matplotlib
diff --git a/‎doc/README.txt
Lines changed: 1 addition & 1 deletion b/‎doc/README.txt
Lines changed: 1 addition & 1 deletion
diff --git a/‎doc/_templates/search.html
Lines changed: 1 addition & 1 deletion b/‎doc/_templates/search.html
Lines changed: 1 addition & 1 deletion
diff --git a/‎doc/api/api_changes.rst
Lines changed: 8 additions & 8 deletions b/‎doc/api/api_changes.rst
Lines changed: 8 additions & 8 deletions
diff --git a/‎doc/devel/coding_guide.rst
Lines changed: 7 additions & 7 deletions b/‎doc/devel/coding_guide.rst
Lines changed: 7 additions & 7 deletions
diff --git a/‎doc/devel/documenting_mpl.rst
Lines changed: 4 additions & 4 deletions b/‎doc/devel/documenting_mpl.rst
Lines changed: 4 additions & 4 deletions
diff --git a/‎doc/devel/outline.rst
Lines changed: 3 additions & 3 deletions b/‎doc/devel/outline.rst
Lines changed: 3 additions & 3 deletions
diff --git a/‎doc/devel/release_guide.rst
Lines changed: 2 additions & 2 deletions b/‎doc/devel/release_guide.rst
Lines changed: 2 additions & 2 deletions
diff --git a/‎doc/faq/howto_faq.rst
Lines changed: 9 additions & 9 deletions b/‎doc/faq/howto_faq.rst
Lines changed: 9 additions & 9 deletions
diff --git a/‎doc/faq/installing_faq.rst
Lines changed: 2 additions & 2 deletions b/‎doc/faq/installing_faq.rst
Lines changed: 2 additions & 2 deletions
diff --git a/‎doc/faq/troubleshooting_faq.rst
Lines changed: 1 addition & 1 deletion b/‎doc/faq/troubleshooting_faq.rst
Lines changed: 1 addition & 1 deletion
@@ -6,7 +6,7 @@ documentation.  All of the documentation is written using sphinx, a
 python documentation system built on top of ReST.  This directory contains
 
 
-* users - the user documentation, eg plotting tutorials, configuration
+* users - the user documentation, e.g. plotting tutorials, configuration
   tips, etc.
 
 * devel - documentation for matplotlib developers
 
@@ -10,7 +10,7 @@ <h1 id="search-documentation">{{ _('Search') }}</h1>
     words. Pages containing less words won't appear in the result
     list.{% endtrans %}  If you want to limit your search to working code examples,
     include the keyword "codex" (mnemonic for <i>code example</i>) in your
-    search, eg "codex ellipse"; 
+    search, e.g. "codex ellipse"; 
     see <a href="{{ pathto('faq/howto_faq.html#search-examples') }}">search&nbsp;examples</a>.
   </p>
   <form action="" method="get">
 
@@ -657,7 +657,7 @@ Changes for 0.91.0
   should be changed to ``${\cal R}$``.  Alternatively, you may use the
   new LaTeX-style font commands (``\mathcal``, ``\mathrm``,
   ``\mathit``, ``\mathtt``) which do affect the following group,
-  eg. ``$\mathcal{R}$``.
+  e.g. ``$\mathcal{R}$``.
 
 * Text creation commands have a new default linespacing and a new
   ``linespacing`` kwarg, which is a multiple of the maximum vertical
@@ -702,7 +702,7 @@ Changes for 0.90.1
     units.ConversionInterface.tickers renamed to
     units.ConversionInterface.axisinfo and it now returns a
     units.AxisInfo object rather than a tuple.  This will make it
-    easier to add axis info functionality (eg I added a default label
+    easier to add axis info functionality (e.g. I added a default label
     on this iteration) w/o having to change the tuple length and hence
     the API of the client code everytime new functionality is added.
     Also, units.ConversionInterface.convert_to_value is now simply
@@ -1187,7 +1187,7 @@ Changes for 0.71
    pylab still imports most of the symbols from Numerix, MLab, fft,
    etc, but is more cautious.  For names that clash with python names
    (min, max, sum), pylab keeps the builtins and provides the numeric
-   versions with an a* prefix, eg (amin, amax, asum)
+   versions with an a* prefix, e.g. (amin, amax, asum)
 
 Changes for 0.70
 ================
@@ -1207,7 +1207,7 @@ Changes for 0.65.1
   removed add_axes and add_subplot from backend_bases.  Use
   figure.add_axes and add_subplot instead.  The figure now manages the
   current axes with gca and sca for get and set current axe.  If you
-  have code you are porting which called, eg, figmanager.add_axes, you
+  have code you are porting which called, e.g., figmanager.add_axes, you
   can now simply do figmanager.canvas.figure.add_axes.
 
 Changes for 0.65
@@ -1334,7 +1334,7 @@ pcolor_classic and scatter_classic.
 
 The return value from pcolor is a PolyCollection.  Most of the
 propertes that are available on rectangles or other patches are also
-available on PolyCollections, eg you can say::
+available on PolyCollections, e.g. you can say::
 
   c = scatter(blah, blah)
   c.set_linewidth(1.0)
@@ -1352,7 +1352,7 @@ over the return value of scatter or pcolor to set properties for the
 entire list.
 
 If you want the different elements of a collection to vary on a
-property, eg to have different line widths, see matplotlib.collections
+property, e.g. to have different line widths, see matplotlib.collections
 for a discussion on how to set the properties as a sequence.
 
 For scatter, the size argument is now in points^2 (the area of the
@@ -1612,7 +1612,7 @@ Changes for 0.42
     needed with double buffered drawing.  Ditto with state change.
     Text instances have a get_prop_tup method that returns a hashable
     tuple of text properties which you can use to see if text props
-    have changed, eg by caching a font or layout instance in a dict
+    have changed, e.g. by caching a font or layout instance in a dict
     with the prop tup as a key -- see RendererGTK.get_pango_layout in
     backend_gtk for an example.
 
@@ -1633,7 +1633,7 @@ Changes for 0.42
 
   * matplotlib.matlab._get_current_fig_manager renamed to
     matplotlib.matlab.get_current_fig_manager to allow user access to
-    the GUI window attribute, eg figManager.window for GTK and
+    the GUI window attribute, e.g. figManager.window for GTK and
     figManager.frame for wx
 
 Changes for 0.40
 
@@ -66,10 +66,10 @@ We prefer this over the equivalent ``from matplotlib import cbook``
 because the latter is ambiguous as to whether ``cbook`` is a module or a
 function.  The former makes it explicit that you
 are importing a module or package.  There are some modules with names
-that match commonly used local variable names, eg
+that match commonly used local variable names, e.g.
 :mod:`matplotlib.lines` or :mod:`matplotlib.colors`. To avoid the clash,
 use the prefix 'm' with the ``import some.thing as
-mthing`` syntax, eg::
+mthing`` syntax, e.g.::
 
     import matplotlib.lines as mlines
     import matplotlib.transforms as transforms   # OK
@@ -239,7 +239,7 @@ Eg. in :class:`matplotlib.lines.Line2D`::
       ACCEPTS: [ '-' | '--' | '-.' | ':' | 'steps' | 'None' | ' ' | '' ]
       """
 
-Since matplotlib uses a lot of pass-through ``kwargs``, eg. in every
+Since matplotlib uses a lot of pass-through ``kwargs``, e.g. in every
 function that creates a line (:func:`~matplotlib.pyplot.plot`,
 :func:`~matplotlib.pyplot.semilogx`,
 :func:`~matplotlib.pyplot.semilogy`, etc...), it can be difficult for
@@ -265,7 +265,7 @@ docstring of ``kwargs``.  Here is an example from
   artist.kwdocd['Line2D'] = artist.kwdoc(Line2D)
 
 Then in any function accepting :class:`~matplotlib.lines.Line2D`
-pass-through ``kwargs``, eg. :meth:`matplotlib.axes.Axes.plot`::
+pass-through ``kwargs``, e.g. :meth:`matplotlib.axes.Axes.plot`::
 
   # in axes.py
   def plot(self, *args, **kwargs):
@@ -284,7 +284,7 @@ pass-through ``kwargs``, eg. :meth:`matplotlib.axes.Axes.plot`::
   plot.__doc__ = cbook.dedent(plot.__doc__) % artist.kwdocd
 
 Note there is a problem for :class:`~matplotlib.artist.Artist`
-``__init__`` methods, eg. :meth:`matplotlib.patches.Patch.__init__`,
+``__init__`` methods, e.g. :meth:`matplotlib.patches.Patch.__init__`,
 which supports ``Patch`` ``kwargs``, since the artist inspector cannot
 work until the class is fully defined and we can't modify the
 ``Patch.__init__.__doc__`` docstring outside the class definition.
@@ -403,7 +403,7 @@ The script can take any of the usual `nosetest arguments`_, such as
 
 To run a single test from the command line, you can provide a
 dot-separated path to the module followed by the function separated by
-a colon, eg.  (this is assuming the test is installed)::
+a colon, e.g.  (this is assuming the test is installed)::
 
   python tests.py matplotlib.tests.test_simplification:test_clipping
 
@@ -527,7 +527,7 @@ distributing L/GPL code through an separate channel, possibly a
 toolkit.  If you include code, make sure you include a copy of that
 code's license in the license directory if the code's license requires
 you to distribute the license with it.  Non-BSD compatible licenses
-are acceptable in matplotlib toolkits (eg basemap), but make sure you
+are acceptable in matplotlib toolkits (e.g. basemap), but make sure you
 clearly state the licenses you are using.
 
 Why BSD compatible?
 
@@ -275,7 +275,7 @@ Referring to mpl documents
 In the documentation, you may want to include to a document in the
 matplotlib src, e.g. a license file or an image file from `mpl-data`,
 refer to it via a relative path from the document where the rst file
-resides, eg, in :file:`users/navigation_toolbar.rst`, we refer to the
+resides, e.g., in :file:`users/navigation_toolbar.rst`, we refer to the
 image icons with::
 
     .. image:: ../../lib/matplotlib/mpl-data/images/subplots.png
@@ -305,7 +305,7 @@ So we can include plots from the examples dir using the symlink::
 
 
 We used to use a symlink for :file:`mpl-data` too, but the distro
-becomes very large on platforms that do not support links (eg the font
+becomes very large on platforms that do not support links (e.g. the font
 files are duplicated and large)
 
 .. _internal-section-refs:
@@ -314,7 +314,7 @@ Internal section references
 ===========================
 
 To maximize internal consistency in section labeling and references,
-use hypen separated, descriptive labels for section references, eg::
+use hypen separated, descriptive labels for section references, e.g.::
 
     .. _howto-webapp:
 
@@ -342,7 +342,7 @@ Section names, etc
 ==================
 
 For everything but top level chapters, please use ``Upper lower`` for
-section titles, eg ``Possible hangups`` rather than ``Possible
+section titles, e.g. ``Possible hangups`` rather than ``Possible
 Hangups``
 
 Inheritance diagrams
 
@@ -157,7 +157,7 @@ If you agree to author a unit, remove the question mark by your name
 "has author".  Once you have completed draft and checked it in, you
 can change the status to "submitted" and try to find a reviewer if you
 don't have one.  The reviewer should read your chapter, test it for
-correctness (eg try your examples) and change the status to "complete"
+correctness (e.g. try your examples) and change the status to "complete"
 when done.
 
 You are free to lift and convert as much material from the web site or
@@ -166,7 +166,7 @@ the existing latex user's guide as you see fit.  The more the better.
 The UI chapters should give an example or two of using mpl with your
 GUI and any relevant info, such as version, installation, config,
 etc...  The backend chapters should cover backend specific
-configuration (eg PS only options), what features are missing, etc...
+configuration (e.g. PS only options), what features are missing, etc...
 
 Please feel free to add units, volunteer to review or author a
 chapter, etc...
@@ -204,7 +204,7 @@ minor things to close the book on this chapter:
      user's guide out. - MGD
 
 #. This section might also benefit from a little more detail on the
-   customizations that are possible (eg an example fleshing out the rc
+   customizations that are possible (e.g. an example fleshing out the rc
    options a little bit).  Admittedly, this is pretty clear from
    readin ghte rc file, but it might be helpful to a newbie.
 
 
@@ -25,7 +25,7 @@ Testing
 
 * Run :file:`unit/nose_tests.py` and make sure all the unit tests are passing
 
-* try some GUI examples, eg :file:`simple_plot.py` with GTKAgg, TkAgg, etc...
+* try some GUI examples, e.g. :file:`simple_plot.py` with GTKAgg, TkAgg, etc...
 
 * remove font cache and tex cache from :file:`.matplotlib` and test
   with and without cache on some example script
@@ -124,7 +124,7 @@ Uploading
   then the "File Releases" tab.  Go to the bottom and click "add
   release" and enter the package name but not the version number in
   the "Package Name" box.  You will then be prompted for the "New
-  release name" at which point you can add the version number, eg
+  release name" at which point you can add the version number, e.g.
   somepackage-0.1 and click "Create this release".
 
   You will then be taken to a fairly self explanatory page where you
 
@@ -21,7 +21,7 @@ Find all objects in a figure of a certain type
 Every matplotlib artist (see :ref:`artist-tutorial`) has a method
 called :meth:`~matplotlib.artist.Artist.findobj` that can be used to
 recursively search the artist for any artists it may contain that meet
-some criteria (eg match all :class:`~matplotlib.lines.Line2D`
+some criteria (e.g. match all :class:`~matplotlib.lines.Line2D`
 instances or match some arbitrary filter function).  For example, the
 following snippet finds every object in the figure which has a
 `set_color` property and makes the object blue::
@@ -47,7 +47,7 @@ Save transparent figures
 The :meth:`~matplotlib.pyplot.savefig` command has a keyword argument
 *transparent* which, if True, will make the figure and axes
 backgrounds transparent when saving, but will not affect the displayed
-image on the screen.  If you need finer grained control, eg you do not
+image on the screen.  If you need finer grained control, e.g. you do not
 want full transparency or you to affect the screen displayed version
 as well, you can set the alpha properties directly.  The figure has a
 :class:`matplotlib.patches.Rectangle` instance called *patch*
@@ -62,7 +62,7 @@ any property on them directly (*facecolor*, *edgecolor*, *linewidth*,
 
 If you need *all* the figure elements to be transparent, there is
 currently no global alpha setting, but you can set the alpha channel
-on individual elements, eg::
+on individual elements, e.g.::
 
    ax.plot(x, y, alpha=0.5)
    ax.set_xlabel('volts', alpha=0.5)
@@ -170,7 +170,7 @@ this chicken and egg problem is to wait until the figure is draw by
 connecting
 (:meth:`matplotlib.backend_bases.FigureCanvasBase.mpl_connect`) to the
 "on_draw" signal (:class:`~matplotlib.backend_bases.DrawEvent`) and
-get the window extent there, and then do something with it, eg move
+get the window extent there, and then do something with it, e.g. move
 the left of the canvas over; see :ref:`event-handling-tutorial`.
 
 Here is an example that gets a bounding box in relative figure coordinates
@@ -228,10 +228,10 @@ setting in the right subplots.
 Skip dates where there is no data
 -------------------------------------
 
-When plotting time series, eg financial time series, one often wants
-to leave out days on which there is no data, eg weekends.  By passing
+When plotting time series, e.g. financial time series, one often wants
+to leave out days on which there is no data, e.g. weekends.  By passing
 in dates on the x-xaxis, you get large horizontal gaps on periods when
-there is not data. The solution is to pass in some proxy x-data, eg
+there is not data. The solution is to pass in some proxy x-data, e.g.
 evenly sampled indices, and then use a custom formatter to format
 these as dates. The example below shows how to use an 'index formatter'
 to achieve the desired plot::
@@ -355,7 +355,7 @@ Make a movie
 
 
 If you want to take an animated plot and turn it into a movie, the
-best approach is to save a series of image files (eg PNG) and use an
+best approach is to save a series of image files (e.g. PNG) and use an
 external tool to convert them to a movie.  You can use `mencoder
 <http://www.mplayerhq.hu/DOCS/HTML/en/mencoder.html>`_,
 which is part of the `mplayer <http://www.mplayerhq.hu>`_ suite
@@ -623,7 +623,7 @@ at the end of the page in the sidebar (or `here
 The sphinx website is a good resource for learning sphinx, but we have
 put together a cheat-sheet at :ref:`documenting-matplotlib` which
 shows you how to get started, and outlines the matplotlib conventions
-and extensions, eg for including plots directly from external code in
+and extensions, e.g. for including plots directly from external code in
 your documents.
 
 Once your documentation contributions are working (and hopefully
 
@@ -194,7 +194,7 @@ If you get an error like::
       File "<string>", line 1, in <module>
     ImportError: No module named matplotlib
 
-then you will need to set your PYTHONPATH, eg::
+then you will need to set your PYTHONPATH, e.g.::
 
     export PYTHONPATH=/Library/Python/2.5/site-packages:$PYTHONPATH
 
@@ -311,7 +311,7 @@ If you have already installed python, you can use one of the
 matplotlib binary installers for windows -- you can get these from the
 `sourceforge download
 <http://sourceforge.net/project/platformdownload.php?group_id=80706>`_
-site.  Choose the files that match your version of python (eg
+site.  Choose the files that match your version of python (e.g.
 ``py2.5`` if you installed Python 2.5) which have the ``exe``
 extension.  If you haven't already installed python, you can get the
 official version from the `python web site
 
@@ -115,7 +115,7 @@ If you compiled matplotlib yourself, please also provide
     platform that are useful for the matplotlib developers to diagnose
     your problem.
 
-  * your compiler version -- eg, ``gcc --version``
+  * your compiler version -- e.g., ``gcc --version``
 
 Including this information in your first e-mail to the mailing list
 will save a lot of time.