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

3 files changed, 7 insertions, 7 deletions

diff --git a/docs/topics/forms/formsets.txt b/docs/topics/forms/formsets.txt
index a452c7640d..585a42469f 100644
--- a/docs/topics/forms/formsets.txt
+++ b/docs/topics/forms/formsets.txt
@@ -139,9 +139,9 @@ A ``max_num`` value of ``None`` (the default) puts a high limit on the number
 of forms displayed (1000). In practice this is equivalent to no limit.
 
 By default, ``max_num`` only affects how many forms are displayed and does not
-affect validation.  If ``validate_max=True`` is passed to the
+affect validation. If ``validate_max=True`` is passed to the
 :func:`~django.forms.formsets.formset_factory`, then ``max_num`` will affect
-validation.  See :ref:`validate_max`.
+validation. See :ref:`validate_max`.
 
 .. _formsets-absolute-max:
 
@@ -695,7 +695,7 @@ model instances for deleted forms will be deleted when you call
 ``formset.save()``.
 
 If you call ``formset.save(commit=False)``, objects will not be deleted
-automatically.  You'll need to call ``delete()`` on each of the
+automatically. You'll need to call ``delete()`` on each of the
 :attr:`formset.deleted_objects
 <django.forms.models.BaseModelFormSet.deleted_objects>` to actually delete
 them:
diff --git a/docs/topics/forms/media.txt b/docs/topics/forms/media.txt
index 17bd385ed0..96408fb4e7 100644
--- a/docs/topics/forms/media.txt
+++ b/docs/topics/forms/media.txt
@@ -211,7 +211,7 @@ complete control over which files are inherited, and which are not.
 If you need to perform some more sophisticated manipulation of asset
 requirements, you can define the ``media`` property directly. This is
 done by defining a widget property that returns an instance of
-``forms.Media``.  The constructor for ``forms.Media`` accepts ``css``
+``forms.Media``. The constructor for ``forms.Media`` accepts ``css``
 and ``js`` keyword arguments in the same format as that used in a
 static media definition.
 
diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt
index c02d4d7809..a5deeb324a 100644
--- a/docs/topics/forms/modelforms.txt
+++ b/docs/topics/forms/modelforms.txt
@@ -410,7 +410,7 @@ you've manually saved the instance produced by the form, you can invoke
 
 Calling ``save_m2m()`` is only required if you use ``save(commit=False)``.
 When you use a ``save()`` on a form, all data -- including many-to-many data --
-is saved without the need for any additional method calls.  For example:
+is saved without the need for any additional method calls. For example:
 
 .. code-block:: pycon
 
@@ -490,7 +490,7 @@ include that field.
     Django will prevent any attempt to save an incomplete model, so if
     the model does not allow the missing fields to be empty, and does
     not provide a default value for the missing fields, any attempt to
-    ``save()`` a ``ModelForm`` with missing fields will fail.  To
+    ``save()`` a ``ModelForm`` with missing fields will fail. To
     avoid this failure, you must instantiate your model with initial
     values for the missing, but required fields::
 
@@ -1107,7 +1107,7 @@ Overriding ``clean()`` on a ``ModelFormSet``
 Just like with a ``ModelForm``, by default the ``clean()`` method of a
 ``ModelFormSet`` will validate that none of the items in the formset violate
 the unique constraints on your model (either ``unique``, ``unique_together`` or
-``unique_for_date|month|year``).  If you want to override the ``clean()`` method
+``unique_for_date|month|year``). If you want to override the ``clean()`` method
 on a ``ModelFormSet`` and maintain this validation, you must call the parent
 class's ``clean`` method::