  As with :class:`~django.db.models.ForeignKey`, you can also create
  :ref:`recursive relationships <recursive-relationships>` (an object with a
  many-to-one relationship to itself) and :ref:`relationships to models not yet
  defined <lazy-relationships>`; see :ref:`the model field reference
  <ref-manytomany>` for details.`
  
  It's suggested, but not required, that the name of a
  :class:`~django.db.models.ManyToManyField` (``toppings`` in the example above)
  be a plural describing the set of related model objects.
  
 
</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 reference <ref-foreignkey>` for details.`
 </s> add reference <ref-foreignkey>` 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 relationship also has access to a ``Manager`` object, but that ``Manager``
represents a single object, rather than a collection of objects::
 </s> add relationship also has access to a :class:`~django.db.models.Manager` object, but
that :class:`~django.db.models.Manager` represents a single object, rather than
a collection of objects:: </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.
<ref-manytomany>` for details.
  As with :class:`~django.db.models.ForeignKey`, you can also create
  :ref:`recursive relationships <recursive-relationships>` (an object with a
  many-to-one relationship to itself) and :ref:`relationships to models not yet
  defined <lazy-relationships>`; see :ref:`the model field reference
<ref-manytomany>` for details.
  
  It's suggested, but not required, that the name of a
  :class:`~django.db.models.ManyToManyField` (``toppings`` in the example above)
  be a plural describing the set of related model objects.
  
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