Removed code terms from docs/spelling_wordlist.

5 files changed, 18 insertions, 18 deletions

diff --git a/docs/releases/1.0-porting-guide.txt b/docs/releases/1.0-porting-guide.txt
index 72f01495a5..03673e1772 100644
--- a/docs/releases/1.0-porting-guide.txt
+++ b/docs/releases/1.0-porting-guide.txt
@@ -401,8 +401,8 @@ Template tags
 :ttag:`spaceless` tag
 ~~~~~~~~~~~~~~~~~~~~~
 
-The spaceless template tag now removes *all* spaces between HTML tags, instead
-of preserving a single space.
+The ``spaceless`` template tag now removes *all* spaces between HTML tags,
+instead of preserving a single space.
 
 Local flavors
 -------------
diff --git a/docs/releases/1.3.txt b/docs/releases/1.3.txt
index 541211509d..ec746418b0 100644
--- a/docs/releases/1.3.txt
+++ b/docs/releases/1.3.txt
@@ -107,20 +107,20 @@ See the :doc:`reference documentation of the app </ref/contrib/staticfiles>`
 for more details or learn how to :doc:`manage static files
 </howto/static-files/index>`.
 
-unittest2 support
------------------
+``unittest2`` support
+----------------------
 
 Python 2.7 introduced some major changes to the ``unittest`` library,
 adding some extremely useful features. To ensure that every Django
 project can benefit from these new features, Django ships with a copy
-of unittest2_, a copy of the Python 2.7 unittest library, backported
+of unittest2_, a copy of the Python 2.7 ``unittest`` library, backported
 for Python 2.4 compatibility.
 
 To access this library, Django provides the ``django.utils.unittest``
 module alias. If you are using Python 2.7, or you have installed
 ``unittest2`` locally, Django will map the alias to the installed
-version of the unittest library. Otherwise, Django will use its own
-bundled version of unittest2.
+version of the ``unittest`` library. Otherwise, Django will use its own
+bundled version of ``unittest2``.
 
 To take advantage of this alias, simply use::
 
@@ -130,8 +130,8 @@ wherever you would have historically used::
 
     import unittest
 
-If you want to continue to use the base unittest library, you can --
-you just won't get any of the nice new unittest2 features.
+If you want to continue to use the base ``unittest`` library, you can --
+you just won't get any of the nice new ``unittest2`` features.
 
 .. _unittest2: https://pypi.org/project/unittest2/
 
@@ -313,7 +313,7 @@ requests. These include:
   :class:`~django.template.RequestContext` by default.
 
 * Support for combining :class:`F expressions <django.db.models.F>`
-  with timedelta values when retrieving or updating database values.
+  with ``timedelta`` values when retrieving or updating database values.
 
 .. _HTTPOnly: https://www.owasp.org/index.php/HTTPOnly
 
@@ -712,7 +712,7 @@ list, even if it has only a single element or no elements.
 ``DjangoTestRunner``
 --------------------
 
-As a result of the introduction of support for unittest2, the features
+As a result of the introduction of support for ``unittest2``, the features
 of ``django.test.simple.DjangoTestRunner`` (including fail-fast
 and Ctrl-C test termination) have been made redundant. In view of this
 redundancy, ``DjangoTestRunner`` has been turned into an empty placeholder
diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt
index 13cff1f0b3..95f1df2e63 100644
--- a/docs/releases/1.4.txt
+++ b/docs/releases/1.4.txt
@@ -213,7 +213,7 @@ can be used for :doc:`deploying with WSGI app
 servers</howto/deployment/wsgi/index>`.
 
 The :djadmin:`built-in development server<runserver>` now supports using an
-externally-defined WSGI callable, which makes it possible to run runserver
+externally-defined WSGI callable, which makes it possible to run ``runserver``
 with the same WSGI configuration that is used for deployment. The new
 :setting:`WSGI_APPLICATION` setting lets you configure which WSGI callable
 :djadmin:`runserver` uses.
diff --git a/docs/releases/1.5.txt b/docs/releases/1.5.txt
index af8de1ea12..57f14d606a 100644
--- a/docs/releases/1.5.txt
+++ b/docs/releases/1.5.txt
@@ -260,8 +260,8 @@ Django 1.5 also includes several smaller improvements worth noting:
   ``self.stderr.write('error')`` (see the note on
   :ref:`management commands output <management-commands-output>`).
 
-* The dumpdata management command outputs one row at a time, preventing
-  out-of-memory errors when dumping large datasets.
+* The :djadmin:`dumpdata` management command outputs one row at a time,
+  preventing out-of-memory errors when dumping large datasets.
 
 * In the localflavor for Canada, "pq" was added to the acceptable codes for
   Quebec. It's an old abbreviation.
@@ -602,7 +602,7 @@ Ordering of tests
 In order to make sure all ``TestCase`` code starts with a clean database,
 tests are now executed in the following order:
 
-* First, all unittests (including :class:`unittest.TestCase`,
+* First, all unit tests (including :class:`unittest.TestCase`,
   :class:`~django.test.SimpleTestCase`, :class:`~django.test.TestCase` and
   :class:`~django.test.TransactionTestCase`) are run with no particular ordering
   guaranteed nor enforced among them.
diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt
index 00d099b025..53bae5b049 100644
--- a/docs/releases/1.6.txt
+++ b/docs/releases/1.6.txt
@@ -415,8 +415,8 @@ be removed.
 New test runner
 ---------------
 
-In order to maintain greater consistency with Python's unittest module, the new
-test runner (``django.test.runner.DiscoverRunner``) does not automatically
+In order to maintain greater consistency with Python's ``unittest`` module, the
+new test runner (``django.test.runner.DiscoverRunner``) does not automatically
 support some types of tests that were supported by the previous runner:
 
 * Tests in ``models.py`` and ``tests/__init__.py`` files will no longer be
@@ -430,7 +430,7 @@ Django bundles a modified version of the :mod:`doctest` module from the Python
 standard library (in ``django.test._doctest``) and includes some additional
 doctest utilities. These utilities are deprecated and will be removed in Django
 1.8; doctest suites should be updated to work with the standard library's
-doctest module (or converted to unittest-compatible tests).
+doctest module (or converted to ``unittest``-compatible tests).
 
 If you wish to delay updates to your test suite, you can set your
 :setting:`TEST_RUNNER` setting to ``django.test.simple.DjangoTestSuiteRunner``