SF.net SVN: matplotlib:[6883] branches/v0_98_5_maint/doc/users/shell.rst

[<ry...@us...>]

Revision: 6883
          http://matplotlib.svn.sourceforge.net/matplotlib/?rev=6883&view=rev
Author:   ryanmay
Date:     2009-02-05 17:48:37 +0000 (Thu, 05 Feb 2009)

Log Message:
-----------
Backport doc typo fixes from trunk.

Modified Paths:
--------------
    branches/v0_98_5_maint/doc/users/shell.rst

Modified: branches/v0_98_5_maint/doc/users/shell.rst
===================================================================
--- branches/v0_98_5_maint/doc/users/shell.rst	2009-02-05 16:00:51 UTC (rev 6882)
+++ branches/v0_98_5_maint/doc/users/shell.rst	2009-02-05 17:48:37 UTC (rev 6883)
@@ -5,7 +5,7 @@
 **********************************
 
 By default, matplotlib defers drawing until the end of the script
-because drawing can be an expensive opertation, and you may not want
+because drawing can be an expensive operation, and you may not want
 to update the plot every time a single property is changed, only once
 after all the properties have changed.
 
@@ -76,7 +76,7 @@
 With the TkAgg backend, that uses the Tkinter user interface toolkit,
 you can use matplotlib from an arbitrary python shell.  Just set your
 ``backend : TkAgg`` and ``interactive : True`` in your
-:file:matplotlibrc file (see :ref:`customizing-matplotlib`) and fire
+:file:`matplotlibrc` file (see :ref:`customizing-matplotlib`) and fire
 up python.  Then::
 
   >>> from pylab import *
@@ -103,7 +103,7 @@
 
 The *interactive* property of the pyplot interface controls whether a
 figure canvas is drawn on every pyplot command.  If *interactive* is
-*False*, then the figure state is updated on every plot commands, but
+*False*, then the figure state is updated on every plot command, but
 will only be drawn on explicit calls to
 :func:`~matplotlib.pyplot.draw`.  When  *interactive* is
 *True*, then every pyplot command triggers a draw.


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.