diff --git a/docs/source/development/config.rst b/docs/source/development/config.rst
index 3fb45cc..fc3fbb8 100644
--- a/docs/source/development/config.rst
+++ b/docs/source/development/config.rst
@@ -498,7 +498,7 @@ For instance:
     # is equivalent to
     $ ipcontroller --Application.log_level=DEBUG
     # and
-    $ ipython --matploitlib
+    $ ipython --matplotlib
     # is equivalent to
     $ ipython --matplotlib auto
     # or
diff --git a/docs/source/development/messaging.rst b/docs/source/development/messaging.rst
index d224698..595c1cd 100644
--- a/docs/source/development/messaging.rst
+++ b/docs/source/development/messaging.rst
@@ -818,7 +818,7 @@ Message type: ``stream``::
 Display Data
 ------------
 
-This type of message is used to bring back data that should be diplayed (text,
+This type of message is used to bring back data that should be displayed (text,
 html, svg, etc.) in the frontends. This data is published to all frontends.
 Each message can have multiple representations of the data; it is up to the
 frontend to decide which to use and how. A single message should contain all
@@ -829,7 +829,7 @@ Some questions remain about this design:
 
 * Do we use this message type for pyout/displayhook? Probably not, because
   the displayhook also has to handle the Out prompt display. On the other hand
-  we could put that information into the metadata secion.
+  we could put that information into the metadata section.
 
 Message type: ``display_data``::
 
@@ -838,7 +838,7 @@ Message type: ``display_data``::
         # Who create the data
         'source' : str,
 
-        # The data dict contains key/value pairs, where the kids are MIME
+        # The data dict contains key/value pairs, where the keys are MIME
         # types and the values are the raw data of the representation in that
         # format.
         'data' : dict,
diff --git a/docs/source/parallel/magics.rst b/docs/source/parallel/magics.rst
index 3576915..01ccbdf 100644
--- a/docs/source/parallel/magics.rst
+++ b/docs/source/parallel/magics.rst
@@ -7,7 +7,7 @@ Parallel Magic Commands
 We provide a few IPython magic commands
 that make it a bit more pleasant to execute Python commands on the engines interactively.
 These are mainly shortcuts to :meth:`.DirectView.execute`
-and :meth:`.AsyncResult.display_outputs` methods repsectively.
+and :meth:`.AsyncResult.display_outputs` methods respectively.
 
 These magics will automatically become available when you create a Client:
 
@@ -70,7 +70,7 @@ Since engines are IPython as well, you can even run magics remotely:
 
 And once in pylab mode with the inline backend,
 you can make plots and they will be displayed in your frontend
-if it suports the inline figures (e.g. notebook or qtconsole):
+if it supports the inline figures (e.g. notebook or qtconsole):
 
 .. sourcecode:: ipython
 
diff --git a/docs/source/parallel/parallel_details.rst b/docs/source/parallel/parallel_details.rst
index d6cadf8..882d436 100644
--- a/docs/source/parallel/parallel_details.rst
+++ b/docs/source/parallel/parallel_details.rst
@@ -170,7 +170,7 @@ communication API for engines via its low-level :meth:`send_apply_message` metho
 by all higher level methods of its Views.
 
 f : function
-    The fuction to be called remotely
+    The function to be called remotely
 args : tuple/list
     The positional arguments passed to `f`
 kwargs : dict
diff --git a/docs/source/parallel/parallel_process.rst b/docs/source/parallel/parallel_process.rst
index 1a93609..30d80cf 100644
--- a/docs/source/parallel/parallel_process.rst
+++ b/docs/source/parallel/parallel_process.rst
@@ -800,7 +800,7 @@ which is a UUID, and thus different every time.
 
 .. sourcecode:: python
 
-    # To keep persistant task history in MongoDB:
+    # To keep persistent task history in MongoDB:
     c.MongoDB.database = 'tasks'
     
     # and in SQLite:
@@ -853,7 +853,7 @@ mpi4py, add:
     c.MPI.use = 'mpi4py'
 
 In this case, the Engine will use our default mpi4py init script to set up
-the MPI environment prior to exection.  We have default init scripts for
+the MPI environment prior to execution.  We have default init scripts for
 mpi4py and pytrilinos.  If you want to specify your own code to be run
 at the beginning, specify `c.MPI.init_script`.