Fixed "the the" typos.

.. note::

    The ``Alias`` and ``Directory`` configurations in the the examples

    The ``Alias`` and ``Directory`` configurations in the examples

    below use an example path to a system-wide installation folder of Django.

    Substitute in an appropriate location, if necessary, as it may be

    different than the path on your system.

Spatial Lookups

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

Just like when using the the :ref:`queryset-api`, interaction

Just like when using the :ref:`queryset-api`, interaction

with ``GeoQuerySet`` by :ref:`chaining filters <chaining-filters>`.

Instead of the regular Django :ref:`field-lookups`, the

spatial lookups in this section are available for :class:`GeometryField`.

*Availability*: PostGIS, Oracle, SpatiaLite

Tests if the geometry field is spatially related to the the lookup geometry by

Tests if the geometry field is spatially related to the lookup geometry by

the values given in the given pattern.  This lookup requires a tuple parameter,

``(geom, pattern)``; the form of ``pattern`` will depend on the spatial backend:

The following methods take no arguments, and attach geometry objects

each element of the :class:`GeoQuerySet` that is the result of relationship

function evaluated on the the geometry field.

function evaluated on the geometry field.

``centroid``

~~~~~~~~~~~~

.. versionadded:: 1.2

Attaches a ``geohash`` attribute to every model the the queryset

Attaches a ``geohash`` attribute to every model the queryset

containing the `GeoHash`__ representation of the geometry.

__ http://geohash.org/

Geospatial Libraries

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

GeoDjango uses and/or provides interfaces for the the following open source

GeoDjango uses and/or provides interfaces for the following open source

geospatial libraries:

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

.. note::

    The important thing here is to make sure you comment out the the

    The important thing here is to make sure you comment out the

    ``define=SQLITE_OMIT_LOAD_EXTENSION`` flag and that the ``include_dirs``

    and ``library_dirs`` settings are uncommented and set to the appropriate

    path if the SQLite header files and libraries are not in ``/usr/include``

    Use of these binaries requires Django 1.0.3 and above.  If you are

    using a previous version of Django (like 1.0.2), then you will have

    to add the the following in your settings::

    to add the following in your settings::

        GEOS_LIBRARY_PATH='/Library/Frameworks/GEOS.framework/GEOS'

        GDAL_LIBRARY_PATH='/Library/Frameworks/GDAL.framework/GDAL'

GDAL Interface

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

Earlier we used the the ``ogrinfo`` to explore the contents of the world borders

Earlier we used the ``ogrinfo`` to explore the contents of the world borders

shapefile.  Included within GeoDjango is an interface to GDAL's powerful OGR

library -- in other words, you'll be able explore all the vector data sources

that OGR supports via a Pythonic API.

    * ``reverse``

    * ``conceal``

A color specification follows one of the the following patterns:

A color specification follows one of the following patterns:

    * ``role=fg``

    * ``role=fg/bg``