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

3 files changed, 8 insertions, 8 deletions

diff --git a/docs/internals/contributing/bugs-and-features.txt b/docs/internals/contributing/bugs-and-features.txt
index 0a80ea5f28..d117b2e165 100644
--- a/docs/internals/contributing/bugs-and-features.txt
+++ b/docs/internals/contributing/bugs-and-features.txt
@@ -5,7 +5,7 @@ Reporting bugs and requesting features
 .. Important::
 
     Please report security issues **only** to
-    security@djangoproject.com.  This is a private list only open to
+    security@djangoproject.com. This is a private list only open to
     long-time, highly trusted Django developers, and its archives are
     not public. For further details, please see :doc:`our security
     policies </internals/security>`.
diff --git a/docs/internals/deprecation.txt b/docs/internals/deprecation.txt
index 031074c3fa..b5dc17fd6a 100644
--- a/docs/internals/deprecation.txt
+++ b/docs/internals/deprecation.txt
@@ -1295,7 +1295,7 @@ details on these changes.
   </topics/class-based-views/index>`.
 
 * The ``django.core.servers.basehttp.AdminMediaHandler`` will be
-  removed.  In its place use
+  removed. In its place use
   ``django.contrib.staticfiles.handlers.StaticFilesHandler``.
 
 * The template tags library ``adminmedia`` and the template tag ``{%
@@ -1358,7 +1358,7 @@ details on these changes.
 See the :ref:`Django 1.2 release notes<deprecated-features-1.2>` for more
 details on these changes.
 
-* ``CsrfResponseMiddleware`` and ``CsrfMiddleware`` will be removed.  Use
+* ``CsrfResponseMiddleware`` and ``CsrfMiddleware`` will be removed. Use
   the ``{% csrf_token %}`` template tag inside forms to enable CSRF
   protection. ``CsrfViewMiddleware`` remains and is enabled by default.
 
@@ -1386,7 +1386,7 @@ details on these changes.
 * The ``Message`` model (in ``django.contrib.auth``), its related
   manager in the ``User`` model (``user.message_set``), and the
   associated methods (``user.message_set.create()`` and
-  ``user.get_and_delete_messages()``), will be removed.  The
+  ``user.get_and_delete_messages()``), will be removed. The
   :doc:`messages framework </ref/contrib/messages>` should be used
   instead. The related ``messages`` variable returned by the
   auth context processor will also be removed. Note that this
@@ -1398,7 +1398,7 @@ details on these changes.
   will no longer be checked and can be removed from custom backends.
 
 * Authentication backends will need to support the ``AnonymousUser`` class
-  being passed to all methods dealing with permissions.  The
+  being passed to all methods dealing with permissions. The
   ``supports_anonymous_user`` variable will no longer be checked and can be
   removed from custom backends.
 
@@ -1425,7 +1425,7 @@ details on these changes.
   ``django.contrib.syndication`` will be removed. The class-based view
   ``views.Feed`` should be used instead.
 
-* ``django.core.context_processors.auth``.  This release will
+* ``django.core.context_processors.auth``. This release will
   remove the old method in favor of the new method in
   ``django.contrib.auth.context_processors.auth``.
 
@@ -1456,7 +1456,7 @@ details on these changes.
 See the :ref:`Django 1.1 release notes<deprecated-features-1.1>` for more
 details on these changes.
 
-* ``AdminSite.root()``.  This method of hooking up the admin URLs will be
+* ``AdminSite.root()``. This method of hooking up the admin URLs will be
   removed in favor of including ``admin.site.urls``.
 
 * Authentication backends need to define the boolean attributes
diff --git a/docs/internals/mailing-lists.txt b/docs/internals/mailing-lists.txt
index a88a1d3edf..c8e074c2df 100644
--- a/docs/internals/mailing-lists.txt
+++ b/docs/internals/mailing-lists.txt
@@ -5,7 +5,7 @@ Mailing lists and Forum
 .. Important::
 
     Please report security issues **only** to
-    security@djangoproject.com.  This is a private list only open to
+    security@djangoproject.com. This is a private list only open to
     long-time, highly trusted Django developers, and its archives are
     not public. For further details, please see :doc:`our security
     policies </internals/security>`.