Refs #36485 -- Removed double spaces after periods in sentences.

1 files changed, 9 insertions, 9 deletions

diff --git a/docs/releases/1.2.txt b/docs/releases/1.2.txt
index 6666596872..cff793047e 100644
--- a/docs/releases/1.2.txt
+++ b/docs/releases/1.2.txt
@@ -173,7 +173,7 @@ Permissions for anonymous users
 
 If you provide a custom auth backend with ``supports_anonymous_user`` set to
 ``True``, AnonymousUser will check the backend for permissions, just like
-User already did.  This is useful for centralizing permission handling - apps
+User already did. This is useful for centralizing permission handling - apps
 can always delegate the question of whether something is allowed or not to
 the authorization/authentication backend. See the :doc:`authentication
 docs </topics/auth/index>` for more details.
@@ -276,7 +276,7 @@ untouched up to and including the Django 1.3 release.
 If you have developed your own custom template loaders we suggest to consider
 porting them to a class-based implementation because the code for backwards
 compatibility with function-based loaders starts its deprecation process in
-Django 1.2 and will be removed in Django 1.4.  There is a description of the
+Django 1.2 and will be removed in Django 1.4. There is a description of the
 API these loader classes must implement in the template API reference and you
 can also examine the source code of the loaders shipped with Django.
 
@@ -342,7 +342,7 @@ GeoDjango
 ---------
 
 The most significant new feature for :doc:`GeoDjango </ref/contrib/gis/index>`
-in 1.2 is support for multiple spatial databases.  As a result,
+in 1.2 is support for multiple spatial databases. As a result,
 the following :ref:`spatial database backends <spatial-backends>`
 are now included:
 
@@ -680,7 +680,7 @@ Cookie encoding
 To fix bugs with cookies in Internet Explorer, Safari, and possibly
 other browsers, our encoding of cookie values was changed so that the
 comma and semicolon are treated as non-safe characters, and are
-therefore encoded as ``\054`` and ``\073`` respectively.  This could
+therefore encoded as ``\054`` and ``\073`` respectively. This could
 produce backwards incompatibilities, especially if you are storing
 comma or semi-colon in cookies and have JavaScript code that parses
 and manipulates cookie values client-side.
@@ -702,7 +702,7 @@ In previous versions of Django, a model's ``BooleanField`` under MySQL
 would return its value as either ``1`` or ``0``, instead of ``True``
 or ``False``; for most people this wasn't a problem because ``bool``
 is a subclass of ``int`` in Python. In Django 1.2, however,
-``BooleanField`` on MySQL correctly returns a real ``bool``.  The only
+``BooleanField`` on MySQL correctly returns a real ``bool``. The only
 time this should ever be an issue is if you were expecting the
 ``repr`` of a ``BooleanField`` to print ``1`` or ``0``.
 
@@ -1094,10 +1094,10 @@ GeoDjango
 ---------
 
 To allow support for multiple databases, the GeoDjango database internals were
-changed substantially.  The largest backwards-incompatible change is that
+changed substantially. The largest backwards-incompatible change is that
 the module ``django.contrib.gis.db.backend`` was renamed to
 :mod:`django.contrib.gis.db.backends`, where the full-fledged
-:ref:`spatial database backends <spatial-backends>` now exist.  The
+:ref:`spatial database backends <spatial-backends>` now exist. The
 following sections provide information on the most-popular APIs that
 were affected by these changes.
 
@@ -1107,7 +1107,7 @@ were affected by these changes.
 Prior to the creation of the separate spatial backends, the
 ``django.contrib.gis.db.backend.SpatialBackend`` object was
 provided as an abstraction to introspect on the capabilities of
-the spatial database.  All of the attributes and routines provided by
+the spatial database. All of the attributes and routines provided by
 ``SpatialBackend`` are now a part of the ``ops`` attribute of the
 database backend.
 
@@ -1147,7 +1147,7 @@ is using a supported spatial database backend.
     Because the table structure of the OGC spatial metadata tables
     differs across spatial databases, the ``SpatialRefSys`` and
     ``GeometryColumns`` models can no longer be associated with
-    the ``gis`` application name.  Thus, no models will be returned
+    the ``gis`` application name. Thus, no models will be returned
     when using the ``get_models`` method in the following example:
 
     .. code-block:: pycon