Fixed #16863 -- Corrected ReST markup to avoid errors building docs.

card values plus their suits; 104 characters in total.

.. note::

    Many of Django's model fields accept options that they don't do anything

    with. For example, you can pass both

    :attr:`~django.db.models.Field.editable` and

    This behavior simplifies the field classes, because they don't need to

    check for options that aren't necessary. They just pass all the options to

    the parent class and then don't use them later on. It's up to you whether

    you want your fields to be more strict about the options they select, or

    to use the simpler, more permissive behavior of the current fields.

    you want your fields to be more strict about the options they select, or to

    use the simpler, more permissive behavior of the current fields.

.. method:: Field.__init__

a pattern for your new view.

.. note::

    Any view you render that uses the admin templates, or extends the base

    admin template, should provide the ``current_app`` argument to

    :class:`~django.template.RequestContext` or :class:`~django.template.Context`

    when rendering the template.  It should be set to either ``self.name`` if

    your view is on an ``AdminSite`` or ``self.admin_site.name`` if your view

    is on a ``ModelAdmin``.

    :class:`~django.template.RequestContext` or

    :class:`~django.template.Context` when rendering the template.  It should

    be set to either ``self.name`` if your view is on an ``AdminSite`` or

    ``self.admin_site.name`` if your view is on a ``ModelAdmin``.

.. _admin-reverse-urls:

files into this directory. See the howto on :doc:`managing static

files</howto/static-files>` for more details about usage.

.. warning:: This should be an (initially empty) destination directory for

    collecting your static files from their permanent locations into one

    directory for ease of deployment; it is **not** a place to store your

    static files permanently. You should do that in directories that will be

    found by :doc:`staticfiles</ref/contrib/staticfiles>`'s

.. warning::

    This should be an (initially empty) destination directory for collecting

    your static files from their permanent locations into one directory for

    ease of deployment; it is **not** a place to store your static files

    permanently. You should do that in directories that will be found by

    :doc:`staticfiles</ref/contrib/staticfiles>`'s

    :setting:`finders<STATICFILES_FINDERS>`, which by default, are

    ``'static/'`` app sub-directories and any directories you include in

    :setting:`STATICFILES_DIRS`).

See also :setting:`USE_I18N` and :setting:`LANGUAGE_CODE`

.. note::

    The default :file:`settings.py` file created by

    :djadmin:`django-admin.py startproject <startproject>` includes

    ``USE_L10N = True`` for convenience.

    The default :file:`settings.py` file created by :djadmin:`django-admin.py

    startproject <startproject>` includes ``USE_L10N = True`` for convenience.

.. setting:: USE_THOUSAND_SEPARATOR

        return HttpResponse(t.render(c))

.. note::

    If you're using Django's :func:`~django.shortcuts.render_to_response()`

    shortcut to populate a template with the contents of a dictionary, your

    template will be passed a ``Context`` instance by default (not a

    ``RequestContext``). To use a ``RequestContext`` in your template rendering,

    pass an optional third argument to

    ``RequestContext``). To use a ``RequestContext`` in your template

    rendering, pass an optional third argument to

    :func:`~django.shortcuts.render_to_response()`: a ``RequestContext``

    instance. Your code might look like this::

        )

    .. note::

        All of the built-in Django template tags are safe to use with the cached

        loader, but if you're using custom template tags that come from third

        party packages, or that you wrote yourself, you should ensure that the

        ``Node`` implementation for each tag is thread-safe. For more

        information, see

        :ref:`template tag thread safety considerations<template_tag_thread_safety>`.

        All of the built-in Django template tags are safe to use with the

        cached loader, but if you're using custom template tags that come from

        third party packages, or that you wrote yourself, you should ensure

        that the ``Node`` implementation for each tag is thread-safe. For more

        information, see :ref:`template tag thread safety

        considerations<template_tag_thread_safety>`.

    This loader is disabled by default.

middleware is always called on every response.

.. note::

    Accessing :attr:`request.POST <django.http.HttpRequest.POST>` or

    :attr:`request.REQUEST <django.http.HttpRequest.REQUEST>` inside 

    middleware from ``process_request`` or ``process_view`` will prevent any

    view running after the middleware from being able to

    :ref:`modify the upload handlers for the 

    request <modifying_upload_handlers_on_the_fly>`, and should normally be

    avoided.

    :attr:`request.REQUEST <django.http.HttpRequest.REQUEST>` inside middleware

    from ``process_request`` or ``process_view`` will prevent any view running

    after the middleware from being able to :ref:`modify the upload handlers

    for the request <modifying_upload_handlers_on_the_fly>`, and should

    normally be avoided.

    The :class:`~django.middleware.csrf.CsrfViewMiddleware` class can be

    considered an exception, as it provides the