Fixed docs typos.

        def my_function():

            ...

    .. admonition:: When using mutiple decorators

    .. admonition:: When using multiple decorators

        If the variable you want to hide is also a function argument (e.g.

        '``user``’ in the following example), and if the decorated function has

        mutiple decorators, then make sure to place ``@sensitive_variables`` at

        the top of the decorator chain. This way it will also hide the function

        argument as it gets passed through the other decorators::

        multiple decorators, then make sure to place ``@sensitive_variables``

        at the top of the decorator chain. This way it will also hide the

        function argument as it gets passed through the other decorators::

            @sensitive_variables('user', 'pw', 'cc')

            @some_decorator

Florian Apolloner

    Florian is currently studying Physics at the `Graz University of Technology`_.

    Soon after he started using Django he joined the `Ubuntuusers webteam`_ to

    work on *Inyoka*, the software powering the whole Ubuntusers site.

    work on *Inyoka*, the software powering the whole Ubuntuusers site.

    For the time beeing he lives in Graz, Austria (not Australia ;)).

    For the time being he lives in Graz, Austria (not Australia ;)).

    .. _Graz University of Technology: http://tugraz.at/

    .. _Ubuntuusers webteam: http://wiki.ubuntuusers.de/ubuntuusers/Webteam

* ``django.db.models.fields.XMLField`` will be removed. This was

  deprecated as part of the 1.3 release. An accelerated deprecation

  schedule has been used because the field hasn't performed any role

  beyond that of a simple ``TextField`` since the removal of oldforms.

  beyond that of a simple ``TextField`` since the removal of ``oldforms``.

  All uses of ``XMLField`` can be replaced with ``TextField``.

* The undocumented ``mixin`` parameter to the ``open()`` method of

   are left for the upcoming release.

#. Check with the other committers to make sure they don't have any

   un-committed changes for the release.

   uncommitted changes for the release.

#. Proofread the release notes, including looking at the online

   version to catch any broken links or reST errors, and make sure the

  trying to learn. Instead, details about individual classes, functions,

  methods, and modules are kept in the :doc:`reference </ref/index>`. This is

  where you'll turn to find the details of a particular function or

  whathaveyou.

  whatever you need.

* If you are interested in deploying a project for public use, our docs have

  :doc:`several guides</howto/deployment/index>` for various deployment