innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed typos in documentation.

This commit is contained in:
Baptiste Mispelon 2013-11-06 10:47:07 +01:00
parent 3c4832214f
commit 366bdc4566
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ref/class-based-views/generic-date-based.txt
View File

@ -611,7 +611,7 @@ DateDetailView
.. note:: .. note::
All of the generic views listed above have matching ``Base`` views that 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:`~django.views.generic.detail.SingleObjectTemplateResponseMixin`:
.. class:: BaseArchiveIndexView .. class:: BaseArchiveIndexView

2
docs/ref/contrib/gis/commands.txt
View File

@ -66,7 +66,7 @@ of using ``ogrinspect`` :ref:`in the tutorial <ogrinspect-intro>`.
.. django-admin-option:: --name-field <name_field> .. django-admin-option:: --name-field <name_field>
Generates a ``__unicode__`` routine (``__str__`` on Python 3) on the model 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 .. django-admin-option:: --no-imports

2
docs/ref/databases.txt
View File

@ -214,7 +214,7 @@ indexing and searching until MySQL 5.6.4.
Since MySQL 5.5.5, the default storage engine is InnoDB_. This engine is fully 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 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 is lost on a MySQL restart because it does not remember the
``AUTO_INCREMENT`` value, instead recreating it as "max(id)+1". This may ``AUTO_INCREMENT`` value, instead recreating it as "max(id)+1". This may
result in an inadvertent reuse of :class:`~django.db.models.AutoField` values. result in an inadvertent reuse of :class:`~django.db.models.AutoField` values.

2
docs/ref/models/fields.txt
View File

@ -1325,7 +1325,7 @@ related. This works exactly the same as it does for :class:`ForeignKey`,
including all the options regarding :ref:`recursive <recursive-relationships>` including all the options regarding :ref:`recursive <recursive-relationships>`
and :ref:`lazy <lazy-relationships>` 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 the ``OneToOneField``, Django will use the lower-case name of the current model
as default value. as default value.