[1.7.x] Fixed doc typos.

        In the usual initialization process, the ``ready`` method is only called

        once by Django. But in some corner cases, particularly in tests which

        are fiddling with installed applications, ``ready`` might be called more

        than once. In that case, either write idempotents methods, or put a flag

        than once. In that case, either write idempotent methods, or put a flag

        on your ``AppConfig`` classes to prevent re-running code which should

        be executed exactly one time.

------------------------

First, we'll need to write a function that gets called when the action is

trigged from the admin. Action functions are just regular functions that take

triggered from the admin. Action functions are just regular functions that take

three arguments:

* The current :class:`ModelAdmin`

   :synopsis: GeoDjango's high-level interface to the GDAL library.

`GDAL`__ stands for **Geospatial Data Abstraction Library**,

and is a veritable "swiss army knife" of GIS data functionality.  A subset

and is a veritable "Swiss army knife" of GIS data functionality.  A subset

of GDAL is the `OGR`__ Simple Features Library, which specializes

in reading and writing vector geographic data in a variety of standard

formats.

    A file uploaded into memory (i.e. stream-to-memory). This class is used

    by the :class:`~django.core.files.uploadhandler.MemoryFileUploadHandler`.

Built-in upload handers

=======================

Built-in upload handlers

========================

.. module:: django.core.files.uploadhandler

   :synopsis: Django's handlers for file uploads.

.. admonition:: Model table names

    Where'd the name of the ``Person`` table come from in that example?

    Where did the name of the ``Person`` table come from in that example?

    By default, Django figures out a database table name by joining the

    model's "app label" -- the name you used in ``manage.py startapp`` -- to