Merge pull request matplotlib#15704 from anntzer/morebrokenrefs

Fix more broken refs.

Author: dstansby

doc/api/prev_api_changes/api_changes_3.1.0.rst

@@ -1153,7 +1153,7 @@ will throw an exception in a future version.
 *verticalalignment* kwargs, and used to ignore them with a warning.  This
 behavior is deprecated and will throw an exception in a future version.
 
-Passing steps less than 1 or greater than 10 to `~ticker..MaxNLocator` used to
+Passing steps less than 1 or greater than 10 to `~.ticker.MaxNLocator` used to
 result in undefined behavior.  It now throws a `ValueError`.
 
 The signature of the (private) ``Axis._update_ticks`` has been changed to not

doc/api/prev_api_changes/api_changes_3.1.1.rst

@@ -11,6 +11,6 @@ Behavior changes
 Locator.nonsingular return order
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-`Locator.nonsingular` (introduced in mpl 3.1) now returns a range ``v0, v1``
+`.Locator.nonsingular` (introduced in mpl 3.1) now returns a range ``v0, v1``
 with ``v0 <= v1``.  This behavior is consistent with the implementation of
-``nonsingular`` by the `LogLocator` and `LogitLocator` subclasses.
+``nonsingular`` by the `.LogLocator` and `.LogitLocator` subclasses.

doc/api/prev_api_changes/api_changes_3.2.0/behavior.rst

@@ -213,7 +213,7 @@ interpolation, leading to aliasing effects for downscaling and non-integer
 upscaling.
 
 New default for :rc:`image.interpolation` is the new option "antialiased".
-`imshow(A, interpolation='antialiased')` will apply a Hanning filter when
+``imshow(A, interpolation='antialiased')`` will apply a Hanning filter when
 resampling the data in A for display (or saving to file) *if* the upsample
 rate is less than a factor of three, and not an integer; downsampled data is
 always smoothed at resampling.
@@ -291,9 +291,9 @@ is now automatically detected.
 Exception changes
 ~~~~~~~~~~~~~~~~~
 Various APIs that raised a `ValueError` for incorrectly typed inputs now raise
-`TypeError` instead: `backend_bases.GraphicsContextBase.set_clip_path`,
-`blocking_input.BlockingInput.__call__`, `cm.register_cmap`, `dviread.DviFont`,
-`rcsetup.validate_hatch`, `rcsetup.validate_animation_writer_path`, `spines.Spine`,
+`TypeError` instead: `.backend_bases.GraphicsContextBase.set_clip_path`,
+`.blocking_input.BlockingInput.__call__`, `.cm.register_cmap`, `.dviread.DviFont`,
+`.rcsetup.validate_hatch`, `.rcsetup.validate_animation_writer_path`, `.spines.Spine`,
 many classes in the :mod:`matplotlib.transforms` module and :mod:`matplotlib.tri`
 package, and Axes methods that take a ``norm`` parameter.
 

doc/devel/MEP/MEP11.rst

@@ -64,7 +64,7 @@ When installing from source, a :program:`git` checkout or pip_:
   - :file:`setup.py` attempts to ``import numpy``.  If this fails, the
     installation fails.
 
-  - For each of dateutil_, pytz_ and six_, `setup.py` attempts to
+  - For each of dateutil_, pytz_ and six_, :file:`setup.py` attempts to
     import them (from the top-level namespace).  If that fails,
     matplotlib installs its local copy of the library into the
     top-level namespace.

doc/devel/contributing.rst

@@ -367,7 +367,7 @@ New modules and files: installation
 
 * If you have added new files or directories, or reorganized existing
   ones, make sure the new files are included in the match patterns in
-  :file:`MANIFEST.in`, and/or in `package_data` in `setup.py`.
+  :file:`MANIFEST.in`, and/or in `package_data` in :file:`setup.py`.
 
 C/C++ extensions
 ----------------
@@ -378,8 +378,8 @@ C/C++ extensions
   address C++, but most of its admonitions still apply).
 
 * Python/C interface code should be kept separate from the core C/C++
-  code.  The interface code should be named `FOO_wrap.cpp` or
-  `FOO_wrapper.cpp`.
+  code.  The interface code should be named :file:`FOO_wrap.cpp` or
+  :file:`FOO_wrapper.cpp`.
 
 * Header file documentation (aka docstrings) should be in Numpydoc
   format.  We don't plan on using automated tools for these
@@ -572,7 +572,7 @@ when the website is built to show up in the `examples
 
 Any sample data that the example uses should be kept small and
 distributed with Matplotlib in the
-`lib/matplotlib/mpl-data/sample_data/` directory.  Then in your
+:file:`lib/matplotlib/mpl-data/sample_data/` directory.  Then in your
 example code you can load it into a file handle with::
 
     import matplotlib.cbook as cbook