Ticket #20327: 0001-Corrected-it-s-to-its-when-used-possessively.patch

docs/ref/contrib/gis/geos.txt

@@ -845 +845 @@
 .. class:: WKBWriter
 
 ``WKBWriter`` provides the most control over its output.  By default it
-returns OGC-compliant WKB when it's ``write`` method is called.  However,
+returns OGC-compliant WKB when its ``write`` method is called.  However,
 it has properties that allow for the creation of EWKB, a superset of the
 WKB standard that includes additional information.
 

docs/ref/contrib/gis/install/geolibs.txt

@@ -194 +194 @@
 
 .. note::
 
-   Because GeoDjango has it's own Python interface, the preceding instructions
+   Because GeoDjango has its own Python interface, the preceding instructions
    do not build GDAL's own Python bindings.  The bindings may be built by
    adding the ``--with-python`` flag when running ``configure``.  See
    `GDAL/OGR In Python`__ for more information on GDAL's bindings.

docs/ref/templates/builtins.txt

@@ -176 +176 @@
 
 This will output a list of ``<tr>`` elements with ``class``
 alternating between ``row1`` and ``row2``; the subtemplate will have
-access to ``rowcolors`` in it's context that matches the class of the
+access to ``rowcolors`` in its context that matches the class of the
 ``<tr>`` that encloses it. If the ``silent`` keyword were to be
 omitted, ``row1`` would be emitted as normal text, outside the
 ``<tr>`` element.

docs/releases/1.3-alpha-1.txt

@@ -87 +87 @@
 ``django.utils.unittest`` module alias. If you are using Python
 2.7, or you have installed unittest2 locally, Django will map the
 alias to the installed version of the unittest library. Otherwise,
-Django will use it's own bundled version of unittest2.
+Django will use its own bundled version of unittest2.
 
 To use this alias, simply use::
 

docs/topics/forms/media.txt

@@ -146 +146 @@
     <script type="text/javascript" src="http://static.example.com/actions.js"></script>
     <script type="text/javascript" src="http://static.example.com/whizbang.js"></script>
 
-The FancyCalendar widget inherits all the media from it's parent widget. If
+The FancyCalendar widget inherits all the media from its parent widget. If
 you don't want media to be inherited in this way, add an ``extend=False``
 declaration to the media declaration::
 

docs/topics/logging.txt

@@ -169 +169 @@
 ``project.interesting.stuff`` loggers.
 
 This propagation can be controlled on a per-logger basis. If
-you don't want a particular logger to propagate to it's parents, you
+you don't want a particular logger to propagate to its parents, you
 can turn off this behavior.
 
 Making logging calls