Fix spelling errors.

akka-docs/scala/fsm.rst

@@ -58,7 +58,7 @@ Now let’s take a look at the skeleton for our FSM actor:
    :exclude: transition-elided,unhandled-elided
 
 The basic strategy is to declare the actor, mixing in the :class:`FSM` trait
-and specifying the possible states and data values as type paramters. Within
+and specifying the possible states and data values as type parameters. Within
 the body of the actor a DSL is used for declaring the state machine:
 
  * :meth:`startsWith` defines the initial state and initial data

akka-docs/scala/io.rst

@@ -32,7 +32,7 @@ IO.Handle
 IOManager
 ^^^^^^^^^
 
-The ``IOManager`` takes care of the low level IO details. Each ``ActorSystem`` has it's own ``IOManager``, which can be accessed calling ``IOManager(system: ActorSystem)``. ``Actor``\s communicate with the ``IOManager`` with specific messages. The messages sent from an ``Actor`` to the ``IOManager`` are handled automatically when using certain methods and the messagegs sent from an ``IOManager`` are handled within an ``Actor``\'s ``receive`` method.
+The ``IOManager`` takes care of the low level IO details. Each ``ActorSystem`` has it's own ``IOManager``, which can be accessed calling ``IOManager(system: ActorSystem)``. ``Actor``\s communicate with the ``IOManager`` with specific messages. The messages sent from an ``Actor`` to the ``IOManager`` are handled automatically when using certain methods and the messages sent from an ``IOManager`` are handled within an ``Actor``\'s ``receive`` method.
 
 Connecting to a remote host:
 

akka-docs/scala/logging.rst

@@ -173,7 +173,7 @@ purposes as it contains exactly the default behavior.
 
   The SLF4J event listener treats this case specially (using the actual string
   to look up the logger instance to use instead of the class’ name), and you
-  might want to do this also in case you implement your own loggin adapter.
+  might want to do this also in case you implement your own logging adapter.
 
 Event Handler
 =============

akka-docs/scala/routing.rst

@@ -29,7 +29,7 @@ This is an example of how to create a router that is defined in configuration:
 
 .. includecode:: code/akka/docs/routing/RouterViaConfigExample.scala#configurableRouting
 
-This is an example of how to programatically create a router and set the number of routees it should create:
+This is an example of how to programmatically create a router and set the number of routees it should create:
 
 .. includecode:: code/akka/docs/routing/RouterViaProgramExample.scala#programmaticRoutingNrOfInstances
 
@@ -37,7 +37,7 @@ You can also give the router already created routees as in:
 
 .. includecode:: code/akka/docs/routing/RouterViaProgramExample.scala#programmaticRoutingRoutees
 
-When you create a router programatically you define the number of routees *or* you pass already created routees to it.
+When you create a router programmatically you define the number of routees *or* you pass already created routees to it.
 If you send both parameters to the router *only* the latter will be used, i.e. ``nrOfInstances`` is disregarded.
 
 *It is also worth pointing out that if you define the ``router`` in the
@@ -235,10 +235,10 @@ This is an example of how to create a resizable router that is defined in config
 
 .. includecode:: code/akka/docs/routing/RouterViaConfigExample.scala#configurableRoutingWithResizer
 
-Several more configuration options are availble and described in ``akka.actor.deployment.default.resizer``
+Several more configuration options are available and described in ``akka.actor.deployment.default.resizer``
 section of the reference :ref:`configuration`.
 
-This is an example of how to programatically create a resizable router:
+This is an example of how to programmatically create a resizable router:
 
 .. includecode:: code/akka/docs/routing/RouterViaProgramExample.scala#programmaticRoutingWithResizer
 
@@ -326,7 +326,7 @@ routing is not so important (i.e. no consistent hashing or round-robin is
 required); this enables newly created routees to pick up work immediately by
 stealing it from their siblings.
 
-The “head” router, of couse, cannot run on the same balancing dispatcher,
+The “head” router, of course, cannot run on the same balancing dispatcher,
 because it does not process the same messages, hence this special actor does
 not use the dispatcher configured in :class:`Props`, but takes the
 ``routerDispatcher`` from the :class:`RouterConfig` instead, which defaults to

akka-docs/scala/testing.rst

@@ -204,7 +204,7 @@ of failure) so that all actors—including the test actor—are stopped.
 Built-In Assertions
 -------------------
 
-The abovementioned :meth:`expectMsg` is not the only method for formulating
+The above mentioned :meth:`expectMsg` is not the only method for formulating
 assertions concerning received messages. Here is the full list:
 
   * :meth:`expectMsg[T](d: Duration, msg: T): T`