diff options
| author | Tim Graham <timograham@gmail.com> | 2012-12-25 09:56:22 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-12-26 19:10:50 -0500 |
| commit | fbc06eef1af1d7ecf91fae5a94a1994f356ffd22 (patch) | |
| tree | 0d45acf4eecae06ddc205ffc8b23b11dcb4896b9 /docs/topics/serialization.txt | |
| parent | e2396bf1220c543ee8d15c7640481889caace61d (diff) | |
[1.5.X] Fixed broken links, round 3. refs #19516
Backport of b3a8c9dab8 from master
Diffstat (limited to 'docs/topics/serialization.txt')
| -rw-r--r-- | docs/topics/serialization.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/serialization.txt b/docs/topics/serialization.txt index 28f600e223..e36c7587d1 100644 --- a/docs/topics/serialization.txt +++ b/docs/topics/serialization.txt @@ -193,7 +193,7 @@ This strategy works well for most objects, but it can cause difficulty in some circumstances. Consider the case of a list of objects that have a foreign key referencing -:class:`~django.contrib.conttenttypes.models.ContentType`. If you're going to +:class:`~django.contrib.contenttypes.models.ContentType`. If you're going to serialize an object that refers to a content type, then you need to have a way to refer to that content type to begin with. Since ``ContentType`` objects are automatically created by Django during the database synchronization process, |