=doc Fix a few typos in docs

akka-docs/rst/java/cluster-usage.rst

@@ -388,7 +388,7 @@ There are two distinct types of routers.
 * **Pool - router that creates routees as child actors and deploys them on remote nodes.** 
   Each router will have its own routee instances. For example, if you start a router
   on 3 nodes in a 10 nodes cluster you will have 30 routee actors in total if the router is
-  configured to use one inctance per node. The routees created by the the different routers
+  configured to use one inctance per node. The routees created by the different routers
   will not be shared between the routers. One example of a use case for this type of router
   is a single master that coordinate jobs and delegates the actual work to routees running 
   on other nodes in the cluster.

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

@@ -319,7 +319,7 @@ encrypt them and send them off to the connection actor while buffering writes.
 This pipeline is driven by a :class:`TcpPipelineHandler` actor which is also
 included in ``akka-actor``. In order to capture the generic command and event
 types consumed and emitted by that actor we need to create a wrapper—the nested
-:class:`Init` class—which also provides the the pipeline context needed by the
+:class:`Init` class—which also provides the pipeline context needed by the
 supplied pipeline; in this case we use the :meth:`withLogger` convenience
 method which supplies a context that implements :class:`HasLogger` and
 :class:`HasActorContext` and should be sufficient for typical pipelines. With