          
  You can also create :ref:`recursive relationships <recursive-relationships>` (an
  object with a many-to-one relationship to itself) and :ref:`relationsips to
  models not yet defined <lazy-relationships>`; see :ref:`the model field
  reference <ref-foreignkey>` for details.`
  
  It's suggested, but not required, that the name of a
  :class:`~django.db.models.ForeignKey` field (``manufacturer`` in the example
  above) be the name of the model, lowercase. You can, of course, call the field
  whatever you want. For example::
 
</s> remove object with a many-to-one relationship to itself) and :ref:`relationsips to
 </s> add object with a many-to-one relationship to itself) and :ref:`relationships to </s> remove <ref-manytomany>` for details.`
 </s> add <ref-manytomany>` for details. </s> remove define a ``OneToOneField`` on your model, instances of that model will have
access to the related object via a simple attribute of the model.
 </s> add define a :class:`~django.db.models.OneToOneField` on your model, instances of
that model will have access to the related object via a simple attribute of the
model. </s> remove and the groups of which they are a member, so you could use a ManyToManyField
to represent this relationship. However, there is a lot of detail about the
membership that you might want to collect, such as the date at which the person
joined the group.
 </s> add and the groups of which they are a member, so you could use a
:class:`~django.db.models.ManyToManyField` to represent this relationship.
However, there is a lot of detail about the membership that you might want to 
collect, such as the date at which the person joined the group. </s> remove       ``symmetrical=False`` (see the documentation for
      ``ManyToManyField`` above).
 </s> add       :attr:`symmetrical=False <ManyToManyFields.symmetrical>` (see 
      :ref:`the model field reference <manytomany-arguments>`).
reference <ref-foreignkey>` for details.
          
  You can also create :ref:`recursive relationships <recursive-relationships>` (an
  object with a many-to-one relationship to itself) and :ref:`relationsips to
  models not yet defined <lazy-relationships>`; see :ref:`the model field
reference <ref-foreignkey>` for details.
  
  It's suggested, but not required, that the name of a
  :class:`~django.db.models.ForeignKey` field (``manufacturer`` in the example
  above) be the name of the model, lowercase. You can, of course, call the field
  whatever you want. For example::
keep keep keep keep replace keep keep keep keep keep
 Fixed a handful of typo/markup problems in the docs. Patch from Daniel Roseman.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@8540 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/topics/db/models.txt