matplotlib · Kojoley · Jan 16, 2020 · Jan 15, 2020
diff --git a/doc/api/prev_api_changes/api_changes_2.0.0.rst b/doc/api/prev_api_changes/api_changes_2.0.0.rst
@@ -32,7 +32,7 @@ The deprecated and not fully functional CocoaAgg backend has been removed.
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The TkAgg backend had its own implementation of the `round` function. This
 was unused internally and has been removed. Instead, use either the
-`round` builtin function or `numpy.round`.
+`round` builtin function or `numpy.around`.
 
 .. _v200_deprecate_hold:
 

diff --git a/doc/api/prev_api_changes/api_changes_3.0.0.rst b/doc/api/prev_api_changes/api_changes_3.0.0.rst
@@ -144,7 +144,7 @@ now raise ``TypeError`` because ``**kwargs`` has been removed.
   unhandled positional arguments.  If two or more arguments are passed
   (ie X, Y, [linefmt], ...) and Y cannot be cast to an array, an error
   will be raised instead of treating X as Y and Y as linefmt.
-- :meth:`mpl_toolkits.axes_grid1.axes_divider.SubPlotDivider` raises
+- `mpl_toolkits.axes_grid1.axes_divider.SubplotDivider` raises
   ``TypeError`` instead of ``Exception`` when passed unknown kwargs.
 
 
@@ -400,10 +400,10 @@ The following classes, methods, functions, and attributes are deprecated:
 - ``patches.Polygon.xy``
 - ``texmanager.dvipng_hack_alpha``
 - ``text.Annotation.arrow``
-- `.Legend.draggable()`, in favor of `.Legend.set_draggable()`
+- ``Legend.draggable()``, in favor of `.Legend.set_draggable()`
    (``Legend.draggable`` may be reintroduced as a property in future releases)
 - ``textpath.TextToPath.tex_font_map``
-- :class:`matplotlib.cbook.deprecation.mplDeprecation` will be removed
+- ``matplotlib.cbook.deprecation.mplDeprecation`` will be removed
   in future versions. It is just an alias for
   :class:`matplotlib.cbook.deprecation.MatplotlibDeprecationWarning`.
   Please use the

diff --git a/doc/api/prev_api_changes/api_changes_3.1.0.rst b/doc/api/prev_api_changes/api_changes_3.1.0.rst
@@ -316,7 +316,7 @@ FreeType or libpng are not in the compiler or linker's default path, set the
 standard environment variables ``CFLAGS``/``LDFLAGS`` on Linux or OSX, or
 ``CL``/``LINK`` on Windows, to indicate the relevant paths.
 
-See details in `Installing`.
+See details in :doc:`/users/installing`.
 
 Setting artist properties twice or more in the same call
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -796,7 +796,7 @@ Changes in parameter names
   as a keyword argument. The common usage pattern as a positional argument
   ``matplotlib.use('Qt5Agg')`` is not affected.
 - The *normed* parameter to `.Axes.hist2d` has been renamed to *density*.
-- The *s* parameter to `.Annotation` (and indirectly `Axes.annotation`) has
+- The *s* parameter to `.Annotation` (and indirectly `.Axes.annotate`) has
   been renamed to *text*.
 - The *tolerence* parameter to
   `bezier.find_bezier_t_intersecting_with_closedpath`,

diff --git a/doc/api/prev_api_changes/api_changes_3.2.0/deprecations.rst b/doc/api/prev_api_changes/api_changes_3.2.0/deprecations.rst
@@ -19,7 +19,7 @@ axes and axis
 Setting ``Axis.major.locator``, ``Axis.minor.locator``, ``Axis.major.formatter``
 or ``Axis.minor.formatter`` to an object that is not a subclass of `.Locator` or
 `.Formatter` (respectively) is deprecated.  Note that these attributes should
-usually be set using `Axis.set_major_locator`, `Axis.set_minor_locator`, etc.
+usually be set using `.Axis.set_major_locator`, `.Axis.set_minor_locator`, etc.
 which already raise an exception when an object of the wrong class is passed.
 
 Passing more than one positional argument or unsupported keyword arguments to
@@ -89,9 +89,9 @@ Axes3D
 axisartist
 ~~~~~~~~~~
 ``mpl_toolkits.axisartist.grid_finder.GridFinderBase`` is deprecated (its
-only use is to be inherited by the `GridFinder` class which just provides
+only use is to be inherited by the `.GridFinder` class which just provides
 more defaults in the constructor and directly sets the transforms, so
-``GridFinderBase``'s methods were just moved to `GridFinder`).
+``GridFinderBase``'s methods were just moved to `.GridFinder`).
 
 ``axisartist.axis_artist.BezierPath`` is deprecated (use `.patches.PathPatch`
 to draw arbitrary Paths).

diff --git a/doc/devel/MEP/MEP10.rst b/doc/devel/MEP/MEP10.rst
@@ -85,7 +85,7 @@ reason, many matplotlib methods include something like::
         """
 
 This can't be parsed by Sphinx, and is rather verbose in raw text.  As
-of Sphinx 1.1, if the `autodoc_docstring_signature` config value is
+of Sphinx 1.1, if the ``autodoc_docstring_signature`` config value is
 set to True, Sphinx will extract a replacement signature from the
 first line of the docstring, allowing this::
 

diff --git a/doc/devel/MEP/MEP12.rst b/doc/devel/MEP/MEP12.rst
@@ -139,7 +139,7 @@ page instead of the gallery examples.
 
 **Note:** When moving an existing example, you should search for
 references to that example.  For example, the API documentation for
-`axes.py` and `pyplot.py` may use these examples to generate
+:file:`axes.py` and :file:`pyplot.py` may use these examples to generate
 plots. Use your favorite search tool (e.g., grep, ack, `grin
 <https://pypi.python.org/pypi/grin>`_, `pss
 <https://pypi.python.org/pypi/pss>`_) to search the matplotlib

diff --git a/doc/devel/MEP/MEP26.rst b/doc/devel/MEP/MEP26.rst
@@ -68,7 +68,7 @@ Implementation
 It will be easiest to allow a '3rd party' to modify/set the style of
 an artist if the 'style' is created as a separate class and store
 against the artist as a property.  The `.GraphicsContext` class already
-provides a the basis of a `Style` class and an artists `draw` method can
+provides a the basis of a `Style` class and an artist's `~.Artist.draw` method can
 be refactored to use the `Style` class rather than setting up it's own
 `.GraphicsContext` and transferring it's style-related properties to
 it.  A minimal example of how this could be implemented is shown here:

diff --git a/doc/devel/contributing.rst b/doc/devel/contributing.rst
@@ -296,7 +296,8 @@ API changes
 Changes to the public API must follow a standard deprecation procedure to
 prevent unexpected breaking of code that uses Matplotlib.
 
-- Deprecations must be announced via an entry in `doc/api/next_api_changes`.
+- Deprecations must be announced via an entry in
+  :file:`doc/api/next_api_changes`.
 - Deprecations are targeted at the next point-release (i.e. 3.x.0).
 - The deprecated API should, to the maximum extent possible, remain fully
   functional during the deprecation period. In cases where this is not

diff --git a/doc/index.rst b/doc/index.rst
@@ -41,7 +41,7 @@ scatterplots, etc., with just a few lines of code.  For examples, see the
 :doc:`sample plots <tutorials/introductory/sample_plots>` and :doc:`thumbnail
 gallery <gallery/index>`.
 
-For simple plotting the `pyplot` module provides a MATLAB-like interface,
+For simple plotting the :mod:`.pyplot` module provides a MATLAB-like interface,
 particularly when combined with IPython.  For the power user, you have full
 control of line styles, font properties, axes properties, etc, via an object
 oriented interface or via a set of functions familiar to MATLAB users.