Fixed #17063 -- Fixed visibility of a few version-dependant notes in our documentation.

Thanks jifeng.yin AT gmail DOT com for the report.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@17057 bcc190cf-cafb-0310-a4f2-bffc1f526a37

7 files changed, 0 insertions, 8 deletions

diff --git a/docs/ref/contrib/sitemaps.txt b/docs/ref/contrib/sitemaps.txt
index a45312cddb..f3ca8d1031 100644
--- a/docs/ref/contrib/sitemaps.txt
+++ b/docs/ref/contrib/sitemaps.txt
@@ -315,7 +315,6 @@ parameter to the ``sitemap`` and ``index`` views via the URLconf::
 
 
 .. versionchanged:: 1.4
-
     In addition, these views also return
     :class:`~django.template.response.TemplateResponse`
     instances which allow you to easily customize the response data before
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index f3a4ef4f77..a5d66f8dcf 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -353,7 +353,6 @@ If you need to accept :attr:`~Field.null` values then use
 :class:`NullBooleanField` instead.
 
 .. versionchanged:: 1.2
-
     In previous versions of Django when running under MySQL ``BooleanFields``
     would return their data as ``ints``, instead of true ``bools``.  See the
     release notes for a complete description of the change.
@@ -879,7 +878,6 @@ shortcuts.
 A :class:`CharField` for a URL. Has one extra optional argument:
 
 .. deprecated:: 1.4
-
    ``verify_exists`` is deprecated for security reasons as of 1.4 and will be
    removed in Django 1.5. Prior to 1.3.1, the default value was ``True``.
 
diff --git a/docs/topics/auth.txt b/docs/topics/auth.txt
index fdd764eb68..63fe70ff83 100644
--- a/docs/topics/auth.txt
+++ b/docs/topics/auth.txt
@@ -636,7 +636,6 @@ Manually managing a user's password
 .. currentmodule:: django.contrib.auth.utils
 
 .. versionadded:: 1.4
-
     The :mod:`django.contrib.auth.utils` module provides a set of functions
     to create and validate hashed password. You can use them independently
     from the ``User`` model.
diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt
index ee50821ac5..58a7cf1c82 100644
--- a/docs/topics/db/queries.txt
+++ b/docs/topics/db/queries.txt
@@ -375,7 +375,6 @@ translates (roughly) into the following SQL::
    .. _`Keyword Arguments`: http://docs.python.org/tutorial/controlflow.html#keyword-arguments
 
 .. versionchanged:: 1.4
-
     The field specified in a lookup has to be the name of a model field.
     There's one exception though, in case of a
     :class:`~django.db.models.fields.ForeignKey` you can specify the field
diff --git a/docs/topics/http/urls.txt b/docs/topics/http/urls.txt
index 9349762312..f90a835067 100644
--- a/docs/topics/http/urls.txt
+++ b/docs/topics/http/urls.txt
@@ -29,7 +29,6 @@ mappings. And, because it's pure Python code, it can be constructed
 dynamically.
 
 .. versionadded:: 1.4
-
     Django also allows to translate URLs according to the active language.
     This process is described in the
     :ref:`internationalization docs <url-internationalization>`.
diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt
index bef052e52d..8826f6ddeb 100644
--- a/docs/topics/i18n/translation.txt
+++ b/docs/topics/i18n/translation.txt
@@ -1496,7 +1496,6 @@ translations for the same literal:
    is used as a fallback.
 
 .. deprecated:: 1.3
-
     Lookup in the ``locale`` subdirectory of the directory containing your
     settings file (item 3 above) is deprecated since the 1.3 release and will be
     removed in Django 1.5. You can use the :setting:`LOCALE_PATHS` setting
diff --git a/docs/topics/serialization.txt b/docs/topics/serialization.txt
index 1ec76941cc..e6a94cacc6 100644
--- a/docs/topics/serialization.txt
+++ b/docs/topics/serialization.txt
@@ -198,7 +198,6 @@ Natural keys
 ------------
 
 .. versionadded:: 1.2
-
    The ability to use natural keys when serializing/deserializing data was
    added in the 1.2 release.