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

1 files changed, 15 insertions, 15 deletions

diff --git a/docs/ref/contrib/gis/layermapping.txt b/docs/ref/contrib/gis/layermapping.txt
index e7971ca2b4..b1d91119f4 100644
--- a/docs/ref/contrib/gis/layermapping.txt
+++ b/docs/ref/contrib/gis/layermapping.txt
@@ -21,9 +21,9 @@ then inserting into a GeoDjango model.
 
 .. warning ::
 
-    GIS data sources, like shapefiles, may be very large.  If you find
+    GIS data sources, like shapefiles, may be very large. If you find
     that :class:`LayerMapping` is using too much memory, set
-    :setting:`DEBUG` to ``False`` in your settings.  When :setting:`DEBUG`
+    :setting:`DEBUG` to ``False`` in your settings. When :setting:`DEBUG`
     is set to ``True``, Django :ref:`automatically logs <faq-see-raw-sql-queries>`
     *every* SQL query -- and when SQL statements contain geometries, this may
     consume more memory than is typical.
@@ -83,7 +83,7 @@ Example
 
 Here, :class:`LayerMapping` transformed the three geometries from the shapefile
 in their original spatial reference system (WGS84) to the spatial reference
-system of the GeoDjango model (NAD83).  If no spatial reference system is
+system of the GeoDjango model (NAD83). If no spatial reference system is
 defined for the layer, use the ``source_srs`` keyword with a
 :class:`~django.contrib.gis.gdal.SpatialReference` object to specify one.
 
@@ -101,7 +101,7 @@ Argument           Description
 ``model``          The geographic model, *not* an instance.
 
 ``data_source``    The path to the OGR-supported data source file
-                   (e.g., a shapefile).  Also accepts
+                   (e.g., a shapefile). Also accepts
                    :class:`django.contrib.gis.gdal.DataSource` instances.
 
 ``mapping``        A dictionary: keys are strings corresponding to
@@ -120,12 +120,12 @@ Keyword Arguments
 
 ``source_srs``         Use this to specify the source SRS manually (for
                        example, some shapefiles don't come with a ``'.prj'``
-                       file).  An integer SRID, WKT or PROJ strings, and
+                       file). An integer SRID, WKT or PROJ strings, and
                        :class:`django.contrib.gis.gdal.SpatialReference`
                        objects are accepted.
 
 ``encoding``           Specifies the character set encoding of the strings
-                       in the OGR data source.  For example, ``'latin-1'``,
+                       in the OGR data source. For example, ``'latin-1'``,
                        ``'utf-8'``, and ``'cp437'`` are all valid encoding
                        parameters.
 
@@ -133,7 +133,7 @@ Keyword Arguments
                        ``'autocommit'``.
 
 ``transform``          Setting this to False will disable coordinate
-                       transformations.  In other words, geometries will
+                       transformations. In other words, geometries will
                        be inserted into the database unmodified from their
                        original state in the data source.
 
@@ -141,7 +141,7 @@ Keyword Arguments
                        from the given  model will create models unique
                        only to the given name(s). Geometries from
                        each feature will be added into the collection
-                       associated with the unique model.  Forces
+                       associated with the unique model. Forces
                        the transaction mode to be ``'autocommit'``.
 
 ``using``              Sets the database to use when importing spatial data.
@@ -153,7 +153,7 @@ Keyword Arguments
 
 .. method:: LayerMapping.save(verbose=False, fid_range=False, step=False, progress=False, silent=False, stream=sys.stdout, strict=False)
 
-The ``save()`` method also accepts keywords.  These keywords are
+The ``save()`` method also accepts keywords. These keywords are
 used for controlling output logging, error handling, and for importing
 specific feature ranges.
 
@@ -162,14 +162,14 @@ Save Keyword Arguments       Description
 ===========================  =================================================
 ``fid_range``                May be set with a slice or tuple of
                              (begin, end) feature ID's to map from
-                             the data source.  In other words, this
+                             the data source. In other words, this
                              keyword enables the user to selectively
                              import a subset range of features in the
                              geographic data source.
 
 ``progress``                 When this keyword is set, status information
                              will be printed giving the number of features
-                             processed and successfully saved.  By default,
+                             processed and successfully saved. By default,
                              progress information will be printed every 1000
                              features processed, however, this default may
                              be overridden by setting this keyword with an
@@ -186,11 +186,11 @@ Save Keyword Arguments       Description
 
 
 ``stream``                   Status information will be written to this file
-                             handle.  Defaults to using ``sys.stdout``, but
+                             handle. Defaults to using ``sys.stdout``, but
                              any object with a ``write`` method is supported.
 
 ``strict``                   Execution of the model mapping will cease upon
-                             the first error encountered.  The default value
+                             the first error encountered. The default value
                              (``False``)
                              behavior is to attempt to continue.
 
@@ -206,7 +206,7 @@ Running out of memory
 ---------------------
 
 As noted in the warning at the top of this section, Django stores all SQL
-queries when ``DEBUG=True``.  Set ``DEBUG=False`` in your settings, and this
+queries when ``DEBUG=True``. Set ``DEBUG=False`` in your settings, and this
 should stop excessive memory use when running ``LayerMapping`` scripts.
 
 MySQL: ``max_allowed_packet`` error
@@ -219,7 +219,7 @@ If you encounter the following error when using ``LayerMapping`` and MySQL:
     OperationalError: (1153, "Got a packet bigger than 'max_allowed_packet' bytes")
 
 Then the solution is to increase the value of the ``max_allowed_packet``
-setting in your MySQL configuration.  For example, the default value may
+setting in your MySQL configuration. For example, the default value may
 be something low like one megabyte -- the setting may be modified in MySQL's
 configuration file (``my.cnf``) in the ``[mysqld]`` section: