=doc Akka & GitHub appearances in docs (#20968)

* =doc capitalize akka word

* Capitalize GitHub appearances in docs

akka-docs/rst/scala/camel.rst

@@ -415,7 +415,7 @@ Here's an actor endpoint URI example containing an actor path::
    akka://some-system/user/myconsumer?autoAck=false&replyTimeout=100+millis
 
 In the following example, a custom route to an actor is created, using the
-actor's path. the akka camel package contains an implicit ``toActorRouteDefinition`` that allows for a route to
+actor's path. the Akka camel package contains an implicit ``toActorRouteDefinition`` that allows for a route to
 reference an ``ActorRef`` directly as shown in the below example, The route starts from a `Jetty`_ endpoint and
 ends at the target actor.
 

akka-docs/rst/scala/cluster-metrics.rst

@@ -14,7 +14,7 @@ Cluster metrics information is primarily used for load-balancing routers,
 and can also be used to implement advanced metrics-based node life cycles,
 such as "Node Let-it-crash" when CPU steal time becomes excessive.
 
-Cluster Metrics Extension is a separate akka module delivered in ``akka-cluster-metrics`` jar.
+Cluster Metrics Extension is a separate Akka module delivered in ``akka-cluster-metrics`` jar.
 
 To enable usage of the extension you need to add the following dependency to your project:
 ::

akka-docs/rst/scala/fsm.rst

@@ -8,7 +8,7 @@ FSM
 Overview
 ========
 
-The FSM (Finite State Machine) is available as a mixin for the akka Actor and
+The FSM (Finite State Machine) is available as a mixin for the Akka Actor and
 is best described in the `Erlang design principles
 <http://www.erlang.org/documentation/doc-4.8.2/doc/design_principles/fsm.html>`_
 

akka-docs/rst/scala/io-tcp.rst

@@ -190,7 +190,7 @@ For back-pressuring writes there are three modes of operation
 
 These write back-pressure models (with the exception of the second which is rather specialised) are
 demonstrated in complete examples below. The full and contiguous source is
-available `on github <@github@/akka-docs/rst/scala/code/docs/io/EchoServer.scala>`_.
+available `on GitHub <@github@/akka-docs/rst/scala/code/docs/io/EchoServer.scala>`_.
 
 For back-pressuring reads there are two modes of operation
 

akka-docs/rst/scala/remoting.rst

@@ -495,7 +495,7 @@ Akka behind NAT or in a Docker container
 ----------------------------------------
 
 In setups involving Network Address Translation (NAT), Load Balancers or Docker
-containers the hostname and port pair that akka binds to will be different than the "logical"
+containers the hostname and port pair that Akka binds to will be different than the "logical"
 host name and port pair that is used to connect to the system from the outside. This requires
 special configuration that sets both the logical and the bind pairs for remoting.
 

akka-docs/rst/scala/stream/migration-guide-2.0-2.4-scala.rst

@@ -23,7 +23,7 @@ completion but there is no actual value attached to the completion. It is used t
 occurrences of ``Future<BoxedUnit>`` with ``Future<Done>`` in Java and ``Future[Unit]`` with
 ``Future[Done]`` in Scala.
 
-All previous usage of ``Unit`` and ``BoxedUnit`` for these two cases in the akka streams APIs
+All previous usage of ``Unit`` and ``BoxedUnit`` for these two cases in the Akka Streams APIs
 has been updated.
 
 This means that Scala code like this::