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

docs/topics/testing/advanced.txt

@@ -560,7 +560,7 @@ and tear down the test suite.
     ``debug_mode`` specifies what the :setting:`DEBUG` setting should be
     set to prior to running tests.
 
-    ``parallel`` specifies the number of processes.  If ``parallel`` is greater
+    ``parallel`` specifies the number of processes. If ``parallel`` is greater
     than ``1``, the test suite will run in ``parallel`` processes. If there are
     fewer test case classes than configured processes, Django will reduce the
     number of processes accordingly. Each process gets its own database. This

docs/topics/testing/overview.txt

@@ -84,7 +84,7 @@ your project's ``manage.py`` utility:
     $ ./manage.py test
 
 Test discovery is based on the unittest module's :py:ref:`built-in test
-discovery <unittest-test-discovery>`.  By default, this will discover tests in
+discovery <unittest-test-discovery>`. By default, this will discover tests in
 any file named ``test*.py`` under the current working directory.
 
 You can specify particular tests to run by supplying any number of "test

docs/topics/testing/tools.txt

@@ -2057,7 +2057,7 @@ Django, such as your machine's mail server, if you're running one.)
 
 During test running, each outgoing email is saved in
 ``django.core.mail.outbox``. This is a list of all
-:class:`~django.core.mail.EmailMessage` instances that have been sent.  The
+:class:`~django.core.mail.EmailMessage` instances that have been sent. The
 ``outbox`` attribute is a special attribute that is created *only* when the
 ``locmem`` email backend is used. It doesn't normally exist as part of the
 :mod:`django.core.mail` module and you can't import it directly. The code below