Fixed typos in documentation.

.. note::

    All of the generic views listed above have matching ``Base`` views that

    only differ in that the they do not include the

    only differ in that they do not include the

    :class:`~django.views.generic.detail.SingleObjectTemplateResponseMixin`:

    .. class:: BaseArchiveIndexView

.. django-admin-option:: --name-field <name_field>

   Generates a ``__unicode__`` routine (``__str__`` on Python 3) on the model

   that will return the the given field name.

   that will return the given field name.

.. django-admin-option:: --no-imports

Since MySQL 5.5.5, the default storage engine is InnoDB_. This engine is fully

transactional and supports foreign key references. It's probably the best

choice at this point. However, note that the the InnoDB autoincrement counter

choice at this point. However, note that the InnoDB autoincrement counter

is lost on a MySQL restart because it does not remember the

``AUTO_INCREMENT`` value, instead recreating it as "max(id)+1". This may

result in an inadvertent reuse of :class:`~django.db.models.AutoField` values.

including all the options regarding :ref:`recursive <recursive-relationships>`

and :ref:`lazy <lazy-relationships>` relationships.

If you do not specify the the :attr:`~ForeignKey.related_name` argument for

If you do not specify the :attr:`~ForeignKey.related_name` argument for

the ``OneToOneField``, Django will use the lower-case name of the current model

as default value.