summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMalcolm Tredinnick <malcolm.tredinnick@gmail.com>2009-03-09 03:33:54 +0000
committerMalcolm Tredinnick <malcolm.tredinnick@gmail.com>2009-03-09 03:33:54 +0000
commit98710a5a2853594f5bad161f9a3bedd27171bb89 (patch)
tree4c334610f31bd26ee074b09436263040ac0a5ba8 /docs
parent059765fa6c273af584ad255eb1395dea6f0e2307 (diff)
Made a couple of cross-references in the model fields documentaiton consistent.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@10007 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/models/fields.txt6
-rw-r--r--docs/topics/db/models.txt4
2 files changed, 5 insertions, 5 deletions
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index 4643837841..340dcff227 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -869,14 +869,14 @@ that control how the relationship functions.
Same as :attr:`ForeignKey.related_name`.
-.. attribute:: ManyToManyFields.limit_choices_to
+.. attribute:: ManyToManyField.limit_choices_to
Same as :attr:`ForeignKey.limit_choices_to`.
``limit_choices_to`` has no effect when used on a ``ManyToManyField`` with
an intermediate table.
-.. attribute:: ManyToManyFields.symmetrical
+.. attribute:: ManyToManyField.symmetrical
Only used in the definition of ManyToManyFields on self. Consider the
following model::
@@ -895,7 +895,7 @@ that control how the relationship functions.
add the descriptor for the reverse relationship, allowing
:class:`ManyToManyField` relationships to be non-symmetrical.
-.. attribute:: ManyToManyFields.through
+.. attribute:: ManyToManyField.through
Django will automatically generate a table to manage many-to-many
relationships. However, if you want to manually specify the intermediary
diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt
index 469733a3b6..12b54babf7 100644
--- a/docs/topics/db/models.txt
+++ b/docs/topics/db/models.txt
@@ -381,7 +381,7 @@ For these situations, Django allows you to specify the model that will be used
to govern the many-to-many relationship. You can then put extra fields on the
intermediate model. The intermediate model is associated with the
:class:`~django.db.models.ManyToManyField` using the
-:attr:`through <ManyToManyFields.through>` argument to point to the model
+:attr:`through <ManyToManyField.through>` argument to point to the model
that will act as an intermediary. For our musician example, the code would look
something like this::
@@ -426,7 +426,7 @@ There are a few restrictions on the intermediate model:
* When defining a many-to-many relationship from a model to
itself, using an intermediary model, you *must* use
- :attr:`symmetrical=False <ManyToManyFields.symmetrical>` (see
+ :attr:`symmetrical=False <ManyToManyField.symmetrical>` (see
:ref:`the model field reference <manytomany-arguments>`).
Now that you have set up your :class:`~django.db.models.ManyToManyField` to use