matplotlib · dstansby · Jan 18, 2018 · Jan 16, 2018
diff --git a/doc/api/api_changes.rst b/doc/api/api_changes.rst
@@ -19,7 +19,7 @@ API Changes in 2.1.2
 `matplotlib.Figure.legend` used to check if a line had the
 same label as an existing legend entry. If it also had the same line color
 or marker color legend didn't add a new entry for that line. However, the
-list of conditions was incomplete, didn't handle RGB tupples,
+list of conditions was incomplete, didn't handle RGB tuples,
 didn't handle linewidths or linestyles etc.
 
 This logic did not exist in `Axes.legend`.  It was included (erroneously)
@@ -781,7 +781,7 @@ Default Behavior Changes
 Changed default ``autorange`` behavior in boxplots
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Prior to v1.5.2, the whiskers of boxplots would extend to the mininum
+Prior to v1.5.2, the whiskers of boxplots would extend to the minimum
 and maximum values if the quartiles were all equal (i.e., Q1 = median
 = Q3). This behavior has been disabled by default to restore consistency
 with other plotting packages.
@@ -3452,7 +3452,7 @@ Changes for 0.40
   - Patches
      * Initialized with a transx, transy which are Transform instances
 
-  - FigureBase attributes dpi is a DPI intance rather than scalar and
+  - FigureBase attributes dpi is a DPI instance rather than scalar and
     new attribute bbox is a Bound2D in display coords, and I got rid
     of the left, width, height, etc... attributes.  These are now
     accessible as, for example, bbox.x.min is left, bbox.x.interval()

diff --git a/doc/devel/MEP/MEP14.rst b/doc/devel/MEP/MEP14.rst
@@ -324,7 +324,7 @@ can be obtained from the `TextSpan` instance::
 
       def get_path(self):
           """
-          Returns a single Path object of the entire layed out text.
+          Returns a single Path object of the entire laid out text.
 
           [Not strictly necessary, but might be useful for textpath
           functionality]

diff --git a/doc/devel/MEP/MEP19.rst b/doc/devel/MEP/MEP19.rst
@@ -34,7 +34,7 @@ has a number of shortcomings:
 - It often fails for inexplicable reasons.
 
 - build or test products can only be saved from build off of branches
-  on the main repo, not pull requsts, so it is often difficult to
+  on the main repo, not pull requests, so it is often difficult to
   "post mortem" analyse what went wrong.  This is particularly
   frustrating when the failure can not be subsequently reproduced
   locally.
@@ -114,7 +114,7 @@ This section outlines the requirements that we would like to have.
    (This would not replace the static documentation for stable
    releases as a default).
 
-#. The test systems should be managable by multiple developers, so
+#. The test systems should be manageable by multiple developers, so
    that no single person becomes a bottleneck.  (Travis-CI's design
    does this well -- storing build configuration in the git
    repository, rather than elsewhere, is a very good design.)

diff --git a/doc/devel/MEP/MEP22.rst b/doc/devel/MEP/MEP22.rst
@@ -58,7 +58,7 @@ the shortcuts out of the `Canvas`.  This actions and shortcuts will be
 in the form of `Tools`.
 
 A new class `Navigation` will be the bridge between the events from
-the `Canvas` and `Toolbar` and redirect them to the appropiate `Tool`.
+the `Canvas` and `Toolbar` and redirect them to the appropriate `Tool`.
 
 At the end the user interaction will be divided into three classes:
 
@@ -170,7 +170,7 @@ ToolbarBase
 Methods for **Backend implementation**
  * add_toolitem(self, name, group, position, image, description,
    toggle): Add a toolitem to the toolbar. This method is a callback
-   from `tool_added_event` (emited by navigation)
+   from `tool_added_event` (emitted by navigation)
  * set_message(self, s): Display a message on toolbar or in status bar
  * toggle_toolitem(self, name): Toggle the toolitem without firing
    event.

diff --git a/doc/devel/MEP/MEP23.rst b/doc/devel/MEP/MEP23.rst
@@ -109,8 +109,8 @@ implemented the **MultiFigure** magic yet.
 Alternatives
 ============
 
-Insted of modifing the `FigureManagerBase` it could be possible to add
+Insted of modifying the `FigureManagerBase` it could be possible to add
 a parallel class, that handles the cases where
 `rcParams['backend.multifigure'] = True`.  This will warranty that
 there won't be any problems with custom made backends, but also makes
-bigger the code, and more things to mantain.
+bigger the code, and more things to maintain.
diff --git a/doc/devel/MEP/MEP26.rst b/doc/devel/MEP/MEP26.rst
@@ -39,7 +39,7 @@ on the artist object, which is quite laborious, especially if no
 reference to the artist(s) has been stored.  The new style sheets
 introduced in 1.4 allow styling before a plot is created, but do not
 offer any means to dynamically update plots or distinguish between
-artists of the same type (i.e. to specifiy the `line color` and `line
+artists of the same type (i.e. to specify the `line color` and `line
 style` separately for differing `Line2D` objects).
 
 The initial development should concentrate on allowing styling of

diff --git a/doc/devel/MEP/MEP28.rst b/doc/devel/MEP/MEP28.rst
@@ -246,7 +246,7 @@ Variations on the theme
 
 This MEP can be divided into a few loosely coupled components:
 
-#. Allowing pre- and post-computation tranformation function in ``cbook.boxplot_stats``
+#. Allowing pre- and post-computation transformation function in ``cbook.boxplot_stats``
 #. Exposing that transformation in the ``Axes.boxplot`` API
 #. Removing redundant statistical options in ``Axes.boxplot``
 #. Shifting all styling parameter processing from ``Axes.boxplot`` to ``Axes.bxp``.
@@ -334,7 +334,7 @@ Users could also pass their own function to compute the stats:
    ax1.boxplot(data, statfxn=my_box_stats, bootstrap_method='BCA',
                whisker_method='dynamic')
 
-From the examples above, Option Two seems to have only marginal benifit,
+From the examples above, Option Two seems to have only marginal benefit,
 but in the context of downstream libraries like seaborn, its advantage
 is more apparent as the following would be possible without any patches
 to seaborn:

diff --git a/doc/devel/MEP/MEP29.rst b/doc/devel/MEP/MEP29.rst
@@ -58,7 +58,7 @@ Problems
 --------
 
 * One serious problem is how to deal with text having both latex and
-  html-like tags. For example, consider the follwing::
+  html-like tags. For example, consider the following::
 
      $<b>Bold$</b>
 

diff --git a/doc/devel/contributing.rst b/doc/devel/contributing.rst
@@ -67,7 +67,7 @@ development environment, using the something like `virtual environments in pytho
 `conda environment <http://conda.pydata.org/docs/using/envs.html>`_.
 
 If you choose to use an already existing environment, and not a clean virtual or
-conda environment, uninstall the current version of Matplotlib in that enviroment
+conda environment, uninstall the current version of Matplotlib in that environment
 using the same method used to install it.
 
 If working on Matplotlib documentation only, the above steps are *not* absolutely

diff --git a/doc/mpl_toolkits/mplot3d/faq.rst b/doc/mpl_toolkits/mplot3d/faq.rst
@@ -8,7 +8,7 @@ How is mplot3d different from MayaVi?
 =====================================
 `MayaVi2 <http://code.enthought.com/projects/mayavi/documentation.php>`_
 is a very powerful and featureful 3D graphing library. For advanced
-3D scenes and excellent rendering capabilities, it is highly recomended to
+3D scenes and excellent rendering capabilities, it is highly recommended to
 use MayaVi2.
 
 mplot3d was intended to allow users to create simple 3D graphs with the same
@@ -24,7 +24,7 @@ is that -- from some viewing angles -- a 3D object would appear in front
 of another object, even though it is physically behind it. This can result in
 plots that do not look "physically correct."
 
-Unfortunately, while some work is being done to reduce the occurance of this
+Unfortunately, while some work is being done to reduce the occurrence of this
 artifact, it is currently an intractable problem, and can not be fully solved
 until matplotlib supports 3D graphics rendering at its core.
 

diff --git a/examples/api/colorbar_basics.py b/examples/api/colorbar_basics.py
@@ -15,7 +15,7 @@
 x, y = np.mgrid[:N, :N]
 Z = (np.cos(x*0.2) + np.sin(y*0.3))
 
-# mask out the negative and positve values, respectively
+# mask out the negative and positive values, respectively
 Zpos = np.ma.masked_less(Z, 0)
 Zneg = np.ma.masked_greater(Z, 0)
 

diff --git a/examples/axes_grid1/demo_axes_divider.py b/examples/axes_grid1/demo_axes_divider.py
@@ -4,7 +4,7 @@
 =================
 
 Axes divider to calculate location of axes and
-create a divider for them using exisiting axes instances.
+create a divider for them using existing axes instances.
 """
 import matplotlib.pyplot as plt
 

diff --git a/examples/axisartist/simple_axisline.py b/examples/axisartist/simple_axisline.py
@@ -29,7 +29,7 @@
 #ax.axis["bottom"].label.set_text("Label X")
 #ax.axis["left"].label.set_text("Label Y")
 
-# make new (right-side) yaxis, but wth some offset
+# make new (right-side) yaxis, but with some offset
 offset = (20, 0)
 new_axisline = ax.get_grid_helper().new_fixed_axis
 

diff --git a/examples/misc/multiprocess_sgskip.py b/examples/misc/multiprocess_sgskip.py
@@ -31,7 +31,7 @@
 # Processing Class
 # ================
 #
-# This class plots data it recieves from a pipe.
+# This class plots data it receives from a pipe.
 #
 
 

diff --git a/setup_external_compile.py b/setup_external_compile.py
@@ -1,4 +1,4 @@
-# This file is coppied from https://github.com/jbmohler/matplotlib-winbuild
+# This file is copied from https://github.com/jbmohler/matplotlib-winbuild
 # Only the needed functions were kept.
 """
 This file extracts and builds library dependencies libpng, zlib, & freetype2 on

diff --git a/setupext.py b/setupext.py
@@ -1547,7 +1547,7 @@ def getoutput(s):
                 # If Gtk+ is installed, pkg-config is required to be installed
                 os.environ['PKG_CONFIG_PATH'] = 'C:\\GTK\\lib\\pkgconfig'
 
-                # popen broken on my win32 plaform so I can't use pkgconfig
+                # popen broken on my win32 platform so I can't use pkgconfig
                 ext.library_dirs.extend(
                     ['C:/GTK/bin', 'C:/GTK/lib'])
 
@@ -1660,7 +1660,7 @@ def check_requirements(self):
             success, msg = res.get(timeout=10)[0]
         except multiprocessing.TimeoutError:
             p.terminate()
-            # No result returned. Probaly hanging, terminate the process.
+            # No result returned. Probably hanging, terminate the process.
             success = False
             raise CheckFailed("Check timed out")
         except:
@@ -1734,7 +1734,7 @@ def check_requirements(self):
             success, msg = res.get(timeout=10)[0]
         except multiprocessing.TimeoutError:
             p.terminate()
-            # No result returned. Probaly hanging, terminate the process.
+            # No result returned. Probably hanging, terminate the process.
             success = False
             raise CheckFailed("Check timed out")
         except:
@@ -1869,7 +1869,7 @@ def check_requirements(self):
                 msg = res.get(timeout=10)[0]
             except multiprocessing.TimeoutError:
                 p.terminate()
-                # No result returned. Probaly hanging, terminate the process.
+                # No result returned. Probably hanging, terminate the process.
                 raise CheckFailed("Check timed out")
             except:
                 # Some other error.

diff --git a/tools/subset.py b/tools/subset.py
@@ -195,7 +195,7 @@ def getsubset(subset, font_in):
     latin += [0x02da] # ring
     latin += [0x02dc] # tilde
     latin += [0x2074] # foursuperior
-    latin += [0x2215] # divison slash
+    latin += [0x2215] # division slash
     latin += [0x2044] # fraction slash
     latin += [0xe0ff] # PUA: Font logo
     latin += [0xeffd] # PUA: Font version number

diff --git a/tutorials/colors/colormaps.py b/tutorials/colors/colormaps.py
@@ -311,7 +311,7 @@ def plot_color_gradients(cmap_category, cmap_list, nrows):
 # have very little grayscale change. If a colormap like this was used in a plot
 # and then the plot was printed to grayscale, a lot of the information may map to
 # the same gray values. The Diverging colormaps mostly vary from darker gray on
-# the outer edges to white in the middle. Some (PuOr and seismic) have noticably
+# the outer edges to white in the middle. Some (PuOr and seismic) have noticeably
 # darker gray on one side than the other and therefore are not very symmetric.
 # coolwarm has little range of gray scale and would print to a more uniform plot,
 # losing a lot of detail. Note that overlaid, labeled contours could help

diff --git a/tutorials/introductory/usage.py b/tutorials/introductory/usage.py
@@ -490,7 +490,7 @@ def my_plotter(ax, data1, data2, param_dict):
 # -------------
 #
 # Both `GTK2` and `GTK3` have implicit dependencies on PyCairo regardless of the
-# specific Matplotlib backend used. Unfortunatly the latest release of PyCairo
+# specific Matplotlib backend used. Unfortunately the latest release of PyCairo
 # for Python3 does not implement the Python wrappers needed for the `GTK3Agg`
 # backend. `Cairocffi` can be used as a replacement which implements the correct
 # wrapper.
@@ -653,7 +653,7 @@ def my_plotter(ax, data1, data2, param_dict):
 # Performance
 # ===========
 #
-# Whether exploring data in interactive mode or programatically
+# Whether exploring data in interactive mode or programmatically
 # saving lots of plots, rendering performance can be a painful
 # bottleneck in your pipeline. Matplotlib provides a couple
 # ways to greatly reduce rendering time at the cost of a slight

diff --git a/tutorials/text/mathtext.py b/tutorials/text/mathtext.py
@@ -186,7 +186,7 @@
 #
 # Here "s" and "t" are variable in italics font (default), "sin" is in
 # Roman font, and the amplitude "A" is in calligraphy font.  Note in the
-# example above the caligraphy ``A`` is squished into the ``sin``.  You
+# example above the calligraphy ``A`` is squished into the ``sin``.  You
 # can use a spacing command to add a little whitespace between them::
 #
 #     s(t) = \mathcal{A}\/\sin(2 \omega t)

diff --git a/tutorials/toolkits/axisartist.py b/tutorials/toolkits/axisartist.py
@@ -86,7 +86,7 @@
 
 Or a fixed axis with some offset ::
 
-    # make new (right-side) yaxis, but wth some offset
+    # make new (right-side) yaxis, but with some offset
     ax.axis["right2"] = ax.new_fixed_axis(loc="right",
                   offset=(20, 0))