summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAdrian Holovaty <adrian@holovaty.com>2008-07-22 02:57:14 +0000
committerAdrian Holovaty <adrian@holovaty.com>2008-07-22 02:57:14 +0000
commitca98003390cd7f0132c7134accf419f957195192 (patch)
tree87aca6e85eca5fd71b3b67cd638f5d814f8234b7 /docs
parent46c7941de36fe82f5797bfee84109d048e2daf90 (diff)
Fixed spaces vs. tabs issue in docs/contenttypes.txt from [7976]
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8042 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/contenttypes.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/contenttypes.txt b/docs/contenttypes.txt
index 96e3b0939c..a4fc045714 100644
--- a/docs/contenttypes.txt
+++ b/docs/contenttypes.txt
@@ -205,10 +205,10 @@ model. There are three parts to setting up a ``GenericForeignKey``:
models you'll be relating to. (For most models, this means an
``IntegerField`` or ``PositiveIntegerField``.)
- This field must be of the same type as the primary key of the models
- that will be involved in the generic relation. For example, if you use
- ``IntegerField``, you won't be able to form a generic relation with a
- model that uses a ``CharField`` as a primary key.
+ This field must be of the same type as the primary key of the models
+ that will be involved in the generic relation. For example, if you use
+ ``IntegerField``, you won't be able to form a generic relation with a
+ model that uses a ``CharField`` as a primary key.
3. Give your model a ``GenericForeignKey``, and pass it the names of
the two fields described above. If these fields are named