[DOC] fixed lots of typos in mpl_toolkits

svn path=/trunk/matplotlib/; revision=8925

Author: ivanov

doc/mpl_toolkits/axes_grid/index.rst

@@ -18,13 +18,13 @@ multiple axes according to their aspects.
    0.99. Originally, the toolkit had a single namespace of 
    *axes_grid*. In more recent version (since svn r8226), the toolkit 
    has divided into two separate namespace (*axes_grid1* and *axisartist*).
-   While *axes_grid* namespace is maintained for he backward compatibility,
+   While *axes_grid* namespace is maintained for the backward compatibility,
    use of *axes_grid1* and *axisartist* is recommended.
 
 .. warning:: 
    *axes_grid* and *axisartist* (but not *axes_grid1*) uses
-   a custome Axes class (derived from the mpl's original Axes class).
-   As a sideeffect, some commands (mostly tick-related) do not work.
+   a custom Axes class (derived from the mpl's original Axes class).
+   As a side effect, some commands (mostly tick-related) do not work.
    Use *axes_grid1* to avoid this, or see how things are different in
    *axes_grid* and *axisartist* (LINK needed)
 

doc/mpl_toolkits/axes_grid/users/axes_divider.rst

@@ -4,20 +4,21 @@ AxesDivider
 The axes_divider module provide helper classes to adjust the axes
 positions of set of images in the drawing time.
 
-* :mod:`~mpl_toolkits.axes_grid.axes_size` provides a classese of
+* :mod:`~mpl_toolkits.axes_grid.axes_size` provides a classes of
   units that the size of each axes will be determined. For example,
   you can specify a fixed size
 
 * :class:`~mpl_toolkits.axes_grid.axes_size.Divider` this is the class
   that is used calculates the axes position. It divides the given
-  renctangular area into several areas. You intialize the divider by
+  rectangular area into several areas. You initialize the divider by
   setting the horizontal and vertical list of sizes that the division
   will be based on. You then use the new_locator method, whose return
   value is a callable object that can be used to set the axes_locator
   of the axes.
 
 
-You first initialize the divider by specifying its grids, i.e., horiz and vert.
+You first initialize the divider by specifying its grids, i.e.,
+horizontal and vertical.
 
 for example,::
 
@@ -56,8 +57,8 @@ be adjusted accordingly.
 
 
 The :mod:`mpl_toolkits.axes_grid.axes_size` contains several classes
-that can be used to set the horiz and vert. For example, for the
-vertical configuration above will be::
+that can be used to set the horizontal and vertical configurations. For
+example, for the vertical configuration above will be::
 
   from mpl_toolkits.axes_grid.axes_size import Fixed, Scaled
   vert = [Fixed(2), Scaled(2), Scaled(3)]
@@ -84,7 +85,7 @@ See the example,
 .. plot:: mpl_toolkits/axes_grid/figures/simple_axes_divider2.py
    :include-source:
 
-You can adjust the size of the each axes accroding to their x or y
+You can adjust the size of the each axes according to their x or y
 data limits (AxesX and AxesY), similar to the axes aspect parameter.
 
 .. plot:: mpl_toolkits/axes_grid/figures/simple_axes_divider3.py

doc/mpl_toolkits/axes_grid/users/axisartist.rst

@@ -4,11 +4,11 @@
 AXISARTIST namespace
 ====================
 
-The AxisArtist namesapce includes a derived Axes implementation. The
+The AxisArtist namespace includes a derived Axes implementation. The
 biggest difference is that the artists responsible to draw axis line,
 ticks, ticklabel and axis labels are separated out from the mpl's Axis
 class, which are much more than artists in the original mpl. This
-change was strongly motivated to support curvlinear grid. Here are a
+change was strongly motivated to support curvilinear grid. Here are a
 few things that mpl_tootlkits.axisartist.Axes is different from original
 Axes from mpl.
 
@@ -18,15 +18,15 @@ Axes from mpl.
   have different tick location and different tick labels.
 
 * gridlines are drawn by a Gridlines instance. The change was
-  motivated that in curvelinear coordinate, a gridline may not cross
+  motivated that in curvilinear coordinate, a gridline may not cross
   axis-lines (i.e., no associated ticks). In the original Axes class,
   gridlines are tied to ticks.
 
 * ticklines can be rotated if necessary (i.e, along the gridlines)
 
 In summary, all these changes was to support
 
-* a curvelinear grid.
+* a curvilinear grid.
 * a floating axis
 
 .. plot:: mpl_toolkits/axes_grid/examples/demo_floating_axis.py
@@ -111,7 +111,8 @@ Similarly, to make ticklabels invisible ::
 
   ax.axis["bottom"].major_ticklabels.set_visible(False)
 
-AxisAritst provides a helper method to control the visibility of ticks, ticklabels, and label. To make ticklabel invisible, ::
+AxisAritst provides a helper method to control the visibility of ticks,
+ticklabels, and label. To make ticklabel invisible, ::
 
   ax.axis["bottom"].toggle(ticklabels=False)
 
@@ -138,7 +139,7 @@ Note that 'ax.axis["top","right"]' returns a simple proxy object that translate
       for n in ["top","right"]:
         ax.axis[n].toggle(ticklabels=True))
 
-So, any return values in the for loop are ignored. And you shoud not
+So, any return values in the for loop are ignored. And you should not
 use it anything more than a simple method. 
 
 Like the list indexing ":" means all items, i.e., ::
@@ -184,8 +185,8 @@ HowTo
     axis.label.set_pad method.
 
 
-Rotaion and Alignment of TickLabels
-===================================
+Rotation and Alignment of TickLabels
+====================================
 
 This is also quite different from the original mpl and can be
 confusing. When you want to rotate the ticklabels, first consider
@@ -252,7 +253,7 @@ direction can be more clear with curved axis.
 
 .. plot:: mpl_toolkits/axes_grid/figures/demo_axis_direction.py
 
-The axis_drection can be adjusted in the AxisArtist level, or in the
+The axis_direction can be adjusted in the AxisArtist level, or in the
 level of its child arists, i.e., ticks, ticklabels, and axis-label. ::
 
   ax1.axis["left"].set_axis_direction("top")
@@ -264,7 +265,7 @@ axis, while ::
 
 changes the axis_direction of only the major_ticklabels.  Note that
 set_axis_direction in the AxisArtist level changes the
-ticklabel_direction and label_direction, while chainging the
+ticklabel_direction and label_direction, while changing the
 axis_direction of ticks, ticklabels, and axis-label does not affect
 them.
 
@@ -295,11 +296,11 @@ So, in summary,
     * set_ticksize : size in points
  * TickLabels' methods (major_ticklabels and minor_ticklabels)
     * set_axis_direction : "left", "right", "bottom", or "top"
-    * set_rotation : angle with respect to the renference direction
+    * set_rotation : angle with respect to the reference direction
     * set_ha and set_va : see below
  * AxisLabels' methods (label)
     * set_axis_direction : "left", "right", "bottom", or "top"
-    * set_rotation : angle with respect to the renference direction
+    * set_rotation : angle with respect to the reference direction
     * set_ha and set_va
 
 
@@ -329,13 +330,13 @@ Or ticklabels and axis-label ::
 GridHelper
 ==========
 
-To actually define a curvelinear coordinate, you have to use your own
+To actually define a curvilinear coordinate, you have to use your own
 grid helper. A generalised version of grid helper class is supplied
 and this class should suffice in most of cases. A user may provide
 two functions which defines a transformation (and its inverse pair)
-from the curved coordinate to (rectlinear) image coordinate. Note that
+from the curved coordinate to (rectilinear) image coordinate. Note that
 while ticks and grids are drawn for curved coordinate, the data
-transform of the axes itself (ax.transData) is still rectlinear
+transform of the axes itself (ax.transData) is still rectilinear
 (image) coordinate. ::
 
 
@@ -404,7 +405,7 @@ required. ::
                                         )
 
 
-Again, the *transData* of the axes is still a rectlinear coordinate
+Again, the *transData* of the axes is still a rectilinear coordinate
 (image coordinate). You may manually do conversion between two
 coordinates, or you may use Parasite Axes for convenience.::
 
@@ -447,7 +448,7 @@ Current Limitations and TODO's
 The code need more refinement. Here is a incomplete list of issues and TODO's
 
 * No easy way to support a user customized tick location (for
-  curvelinear grid). A new Locator class needs to be created.
+  curvilinear grid). A new Locator class needs to be created.
 
 * FloatingAxis may have coordinate limits, e.g., a floating axis of x
   = 0, but y only spans from 0 to 1.

doc/mpl_toolkits/axes_grid/users/overview.rst

@@ -17,19 +17,19 @@ mainly to ease displaying (multiple) images in matplotlib.
    0.99. Originally, the toolkit had a single namespace of 
    *axes_grid*. In more recent version (since svn r8226), the toolkit 
    has divided into two separate namespace (*axes_grid1* and *axisartist*).
-   While *axes_grid* namespace is maintained for he backward compatibility,
+   While *axes_grid* namespace is maintained for the backward compatibility,
    use of *axes_grid1* and *axisartist* is recommended.
 
 .. warning:: 
    *axes_grid* and *axisartist* (but not *axes_grid1*) uses
-   a custome Axes class (derived from the mpl's original Axes class).
-   As a sideeffect, some commands (mostly tick-related) do not work.
+   a custom Axes class (derived from the mpl's original Axes class).
+   As a side effect, some commands (mostly tick-related) do not work.
    Use *axes_grid1* to avoid this, or see how things are different in
    *axes_grid* and *axisartist* (LINK needed)
 
 
 AxesGrid toolkit has two namespaces (*axes_grid1* and *axisartist*).
-*axisartist* contains custome Axes class that is meant to support for
+*axisartist* contains custom Axes class that is meant to support for
 curvilinear grids (e.g., the world coordinate system in astronomy).
 Unlike mpl's original Axes class which uses Axes.xaxis and Axes.yaxis
 to draw ticks, ticklines and etc., Axes in axisartist uses special
@@ -46,7 +46,7 @@ Axes.xaxis and Axes.yaxis may not work. See LINK for more detail.
 (multiple) images with matplotlib.  In matplotlib, the axes location
 (and size) is specified in the normalized figure coordinates, which
 may not be ideal for displaying images that needs to have a given
-aspect ratio.  For example, it helps you to have a colobar whose
+aspect ratio.  For example, it helps you to have a colorbar whose
 height always matches that of the image.  `ImageGrid`_, `RGB Axes`_ and
 `AxesDivider`_ are helper classes that deals with adjusting the
 location of (multiple) Axes.  They provides a framework to adjust the
@@ -76,9 +76,9 @@ used in such case.
 .. plot:: mpl_toolkits/axes_grid/examples/simple_axesgrid.py
    :include-source:
 
-* The postion of each axes is determined at the drawing time (see
+* The position of each axes is determined at the drawing time (see
   `AxesDivider`_), so that the size of the entire grid fits in the
-  given rectangle (like the aspec of axes). Note that in this example,
+  given rectangle (like the aspect of axes). Note that in this example,
   the paddings between axes are fixed even if you changes the figure
   size.
 
@@ -141,7 +141,7 @@ AxesGrid takes following arguments,
   means the increasing direction of the axes number.
 
  *aspect*
-  By default (False), widths and heigths of axes in the grid are
+  By default (False), widths and heights of axes in the grid are
   scaled independently. If True, they are scaled according to their
   data limits (similar to aspect parameter in mpl).
 
@@ -165,7 +165,7 @@ AxesGrid takes following arguments,
    | grid[1] | grid[3] |
    +---------+---------+
 
-You can also create a colorbar (or colobars). You can have colorbar
+You can also create a colorbar (or colorbars). You can have colorbar
 for each axes (cbar_mode="each"), or you can have a single colorbar
 for the grid (cbar_mode="single"). The colorbar can be placed on your
 right, or top. The axes for each colorbar is stored as a *cbar_axes*
@@ -187,7 +187,7 @@ at drawing time. While a more about the AxesDivider is (will be)
 explained in (yet to be written) AxesDividerGuide, direct use of the
 AxesDivider class will not be necessary for most users.  The
 axes_divider module provides a helper function make_axes_locatable,
-which can be useful. It takes a exisitng axes instance and create a
+which can be useful. It takes a existing axes instance and create a
 divider for it. ::
 
 	ax = subplot(1,1,1)
@@ -196,7 +196,7 @@ divider for it. ::
 
 
 
-*make_axes_locatable* returns an isntance of the AxesLocator class,
+*make_axes_locatable* returns an instance of the AxesLocator class,
 derived from the Locator. It provides *append_axes* method that
 creates a new axes on the given side of ("top", "right", "bottom" and
 "left") of the original axes.
@@ -255,7 +255,7 @@ if the host change its location (e.g., images).
 In most cases, you first create a host axes, which provides a few
 method that can be used to create parasite axes. They are *twinx*,
 *twiny* (which are similar to twinx and twiny in the matplotlib) and
-*twin*. *twin* takes an arbitraty tranfromation that maps between the
+*twin*. *twin* takes an arbitrary transformation that maps between the
 data coordinates of the host axes and the parasite axes.  *draw*
 method of the parasite axes are never called. Instead, host axes
 collects artists in parasite axes and draw them as if they belong to
@@ -292,7 +292,7 @@ tick-formatter for bottom(or left)-axis. ::
 
 
 
-A more sophiscated example using twin. Note that if you change the
+A more sophisticated example using twin. Note that if you change the
 x-limit in the host axes, the x-limit of the parasite axes will change
 accordingly.
 
@@ -319,7 +319,7 @@ InsetLocator
 
 :mod:`mpl_toolkits.axes_grid.inset_locator` provides helper classes
 and functions to place your (inset) axes at the anchored position of
-the parent axes, similarly to AnchoredArtis.
+the parent axes, similarly to AnchoredArtist.
 
 Using :func:`mpl_toolkits.axes_grid.inset_locator.inset_axes`, you
 can have inset axes whose size is either fixed, or a fixed proportion
@@ -359,7 +359,7 @@ represented by the inset axes.
 RGB Axes
 ~~~~~~~~
 
-RGBAxes is a helper clase to conveniently show RGB composite
+RGBAxes is a helper class to conveniently show RGB composite
 images. Like ImageGrid, the location of axes are adjusted so that the
 area occupied by them fits in a given rectangle.  Also, the xaxis and
 yaxis of each axes are shared. ::
@@ -386,7 +386,7 @@ AxisArtist
 
 AxisArtist module provides a custom (and very experimental) Axes
 class, where each axis (left, right, top and bottom) have a separate
-artist associated which is resposible to draw axis-line, ticks,
+artist associated which is responsible to draw axis-line, ticks,
 ticklabels, label.  Also, you can create your own axis, which can pass
 through a fixed position in the axes coordinate, or a fixed position
 in the data coordinate (i.e., the axis floats around when viewlimit
@@ -407,7 +407,7 @@ To create an axes, ::
   ax = AA.Axes(fig, [0.1, 0.1, 0.8, 0.8])
   fig.add_axes(ax)
 
-or to creat a subplot ::
+or to create a subplot ::
 
   ax = AA.Subplot(fig, 111)
   fig.add_subplot(ax)
@@ -441,7 +441,7 @@ Or a fixed axis with some offset ::
 AxisArtist with ParasiteAxes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Most commands in the axes_grid toolkit1 can take a axes_class keyword
+Most commands in the axes_grid1 toolkit can take a axes_class keyword
 argument, and the commands creates an axes of the given class. For example,
 to create a host subplot with axisartist.Axes, ::
 
@@ -458,10 +458,10 @@ Here is an example that uses  parasiteAxes.
 
 
 
-Curvelinear Grid
+Curvilinear Grid
 ----------------
 
-The motivation behind the AxisArtist module is to support cuvelinear grid
+The motivation behind the AxisArtist module is to support curvilinear grid
 and ticks.
 
 .. plot:: mpl_toolkits/axes_grid/examples/demo_floating_axis.py
@@ -472,7 +472,7 @@ See :ref:`axisartist-manual` for more details.
 Floating Axes
 -------------
 
-This also suppport a Floating Axes whose outer axis are defined as
+This also support a Floating Axes whose outer axis are defined as
 floating axis.
 
 .. plot:: mpl_toolkits/axes_grid/examples/demo_floating_axes.py

examples/axes_grid/demo_axes_divider.py

@@ -27,7 +27,7 @@ def demo_locatable_axes_hard(fig1):
     # axes for image
     ax = LocatableAxes(fig1, divider.get_position())
 
-    # axes for coloarbar
+    # axes for colorbar
     ax_cb = LocatableAxes(fig1, divider.get_position())
 
     h = [Size.AxesX(ax), # main axes
@@ -117,7 +117,7 @@ def demo():
 
 
     ## PLOT 4
-    # two images side by sied with fixed padding.
+    # two images side by side with fixed padding.
 
     ax = fig1.add_subplot(2, 2, 4)
     demo_images_side_by_sied(ax)