Fixed #19516 - Fixed remaining broken links.

Added -n to sphinx builds to catch issues going forward.

8 files changed, 16 insertions, 17 deletions

diff --git a/docs/releases/1.2-beta-1.txt b/docs/releases/1.2-beta-1.txt
index 3549767379..abb0f3bbb9 100644
--- a/docs/releases/1.2-beta-1.txt
+++ b/docs/releases/1.2-beta-1.txt
@@ -47,7 +47,7 @@ should be updated to use the new :ref:`class-based runners
 Syndication feeds
 -----------------
 
-The :class:`django.contrib.syndication.feeds.Feed` class is being
+The ``django.contrib.syndication.feeds.Feed`` class is being
 replaced by the :class:`django.contrib.syndication.views.Feed` class.
 The old ``feeds.Feed`` class is deprecated. The new class has an
 almost identical API, but allows instances to be used as views.
diff --git a/docs/releases/1.2.txt b/docs/releases/1.2.txt
index 68cec91587..50c049f5da 100644
--- a/docs/releases/1.2.txt
+++ b/docs/releases/1.2.txt
@@ -345,10 +345,10 @@ in 1.2 is support for multiple spatial databases.  As a result,
 the following :ref:`spatial database backends <spatial-backends>`
 are now included:
 
-* :mod:`django.contrib.gis.db.backends.postgis`
-* :mod:`django.contrib.gis.db.backends.mysql`
-* :mod:`django.contrib.gis.db.backends.oracle`
-* :mod:`django.contrib.gis.db.backends.spatialite`
+* ``django.contrib.gis.db.backends.postgis``
+* ``django.contrib.gis.db.backends.mysql``
+* ``django.contrib.gis.db.backends.oracle``
+* ``django.contrib.gis.db.backends.spatialite``
 
 GeoDjango now supports the rich capabilities added
 in the `PostGIS 1.5 release <http://postgis.refractions.net/documentation/manual-1.5/>`_.
@@ -986,7 +986,7 @@ should be updated to use the new :ref:`class-based runners
 ``Feed`` in ``django.contrib.syndication.feeds``
 ------------------------------------------------
 
-The :class:`django.contrib.syndication.feeds.Feed` class has been
+The ``django.contrib.syndication.feeds.Feed`` class has been
 replaced by the :class:`django.contrib.syndication.views.Feed` class.
 The old ``feeds.Feed`` class is deprecated, and will be removed in
 Django 1.4.
diff --git a/docs/releases/1.3-alpha-1.txt b/docs/releases/1.3-alpha-1.txt
index e2c52a7264..ba8a4fc557 100644
--- a/docs/releases/1.3-alpha-1.txt
+++ b/docs/releases/1.3-alpha-1.txt
@@ -150,7 +150,7 @@ process has been on adding lots of smaller, long standing feature
 requests. These include:
 
 * Improved tools for accessing and manipulating the current Site via
-  :func:`django.contrib.sites.models.get_current_site`.
+  ``django.contrib.sites.models.get_current_site()``.
 
 * A :class:`~django.test.client.RequestFactory` for mocking
   requests in tests.
diff --git a/docs/releases/1.3-beta-1.txt b/docs/releases/1.3-beta-1.txt
index d064063fce..14897ed3b7 100644
--- a/docs/releases/1.3-beta-1.txt
+++ b/docs/releases/1.3-beta-1.txt
@@ -140,7 +140,7 @@ attribute.
 Changes to ``USStateField``
 ===========================
 
-The :mod:`django.contrib.localflavor` application contains collections
+The ``django.contrib.localflavor`` application contains collections
 of code relevant to specific countries or cultures. One such is
 ``USStateField``, which provides a field for storing the two-letter postal
 abbreviation of a U.S. state. This field has consistently caused problems,
@@ -167,13 +167,13 @@ as a pair of changes:
   independent nations -- the Federated States of Micronesia, the
   Republic of the Marshall Islands and the Republic of Palau -- which
   are serviced under treaty by the U.S. postal system. A new form
-  widget, :class:`django.contrib.localflavor.us.forms.USPSSelect`, is
+  widget, ``django.contrib.localflavor.us.forms.USPSSelect``, is
   also available and provides the same set of choices.
 
 Additionally, several finer-grained choice tuples are provided which
 allow mixing and matching of subsets of the U.S. states and
 territories, and other locations serviced by the U.S. postal
-system. Consult the :mod:`django.contrib.localflavor` documentation
+system. Consult the ``django.contrib.localflavor`` documentation
 for more details.
 
 The change to `USStateField` is technically backwards-incompatible for
diff --git a/docs/releases/1.3.txt b/docs/releases/1.3.txt
index 6a056532b9..4c8dd2f81f 100644
--- a/docs/releases/1.3.txt
+++ b/docs/releases/1.3.txt
@@ -367,9 +367,8 @@ In earlier Django versions, when a model instance containing a
 file from the backend storage. This opened the door to several data-loss
 scenarios, including rolled-back transactions and fields on different models
 referencing the same file. In Django 1.3, when a model is deleted the
-:class:`~django.db.models.FileField`'s
-:func:`~django.db.models.FileField.delete` method won't be called.  If you
-need cleanup of orphaned files, you'll need to handle it yourself (for
+:class:`~django.db.models.FileField`'s ``delete()`` method won't be called. If
+you need cleanup of orphaned files, you'll need to handle it yourself (for
 instance, with a custom management command that can be run manually or
 scheduled to run periodically via e.g. cron).
 
diff --git a/docs/releases/1.4-alpha-1.txt b/docs/releases/1.4-alpha-1.txt
index 4086cfdecc..09855400eb 100644
--- a/docs/releases/1.4-alpha-1.txt
+++ b/docs/releases/1.4-alpha-1.txt
@@ -504,7 +504,7 @@ Django 1.4 also includes several smaller improvements worth noting:
   page.
 
 * The ``django.contrib.auth.models.check_password`` function has been moved
-  to the :mod:`django.contrib.auth.utils` module. Importing it from the old
+  to the ``django.contrib.auth.utils`` module. Importing it from the old
   location will still work, but you should update your imports.
 
 * The :djadmin:`collectstatic` management command gained a ``--clear`` option
diff --git a/docs/releases/1.4-beta-1.txt b/docs/releases/1.4-beta-1.txt
index a8732a9e65..8ea63742e3 100644
--- a/docs/releases/1.4-beta-1.txt
+++ b/docs/releases/1.4-beta-1.txt
@@ -564,7 +564,7 @@ Django 1.4 also includes several smaller improvements worth noting:
   page.
 
 * The ``django.contrib.auth.models.check_password`` function has been moved
-  to the :mod:`django.contrib.auth.utils` module. Importing it from the old
+  to the ``django.contrib.auth.utils`` module. Importing it from the old
   location will still work, but you should update your imports.
 
 * The :djadmin:`collectstatic` management command gained a ``--clear`` option
diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt
index cf53b37f17..9459e940b4 100644
--- a/docs/releases/1.4.txt
+++ b/docs/releases/1.4.txt
@@ -888,10 +888,10 @@ object, Django raises an exception.
 ``MySQLdb``-specific exceptions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The MySQL backend historically has raised :class:`MySQLdb.OperationalError`
+The MySQL backend historically has raised ``MySQLdb.OperationalError``
 when a query triggered an exception. We've fixed this bug, and we now raise
 :exc:`django.db.DatabaseError` instead. If you were testing for
-:class:`MySQLdb.OperationalError`, you'll need to update your ``except``
+``MySQLdb.OperationalError``, you'll need to update your ``except``
 clauses.
 
 Database connection's thread-locality