=doc Fix a few typos in docs

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

@@ -385,7 +385,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/scala/io-tcp.rst

@@ -313,7 +313,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

akka-docs/rst/scala/io.rst

@@ -122,13 +122,3 @@ For further details on the design and internal architecture see :ref:`io-layer`.
 
 .. _spray.io: http://spray.io
 
-Link to the old IO documentation
---------------------------------
-
-.. This is only in here to avoid a warning about io-old not being part of any toctree.
-
-.. toctree::
-   :maxdepth: 1
-
-   io-old
-

akka-docs/rst/scala/persistence.rst

@@ -1,4 +1,4 @@
-.. _persistence:
+.. _persistence-scala:
 
 ###########
 Persistence

akka-docs/rst/scala/serialization.rst

@@ -155,7 +155,7 @@ There is also a default remote address which is the one used by cluster support
 Deep serialization of Actors
 ----------------------------
 
-The recommended approach to do deep serialization of internal actor state is to use Akka :ref:`persistence`.
+The recommended approach to do deep serialization of internal actor state is to use Akka :ref:`persistence-scala`.
 
 A Word About Java Serialization
 ===============================