diff --git a/docs/topics/serialization.txt b/docs/topics/serialization.txt
index d5a5282..6bda32d 100644
|
a
|
b
|
Serializing Django objects
|
| 3 | 3 | ========================== |
| 4 | 4 | |
| 5 | 5 | Django's serialization framework provides a mechanism for "translating" Django |
| 6 | | objects into other formats. Usually these other formats will be text-based and |
| 7 | | used for sending Django objects over a wire, but it's possible for a |
| | 6 | models into other formats. Usually these other formats will be text-based and |
| | 7 | used for sending Django data over a wire, but it's possible for a |
| 8 | 8 | serializer to handle any format (text-based or not). |
| 9 | 9 | |
| 10 | 10 | .. seealso:: |
| … |
… |
At the highest level, serializing data is a very simple operation::
|
| 23 | 23 | The arguments to the ``serialize`` function are the format to serialize the data |
| 24 | 24 | to (see `Serialization formats`_) and a |
| 25 | 25 | :class:`~django.db.models.query.QuerySet` to serialize. (Actually, the second |
| 26 | | argument can be any iterator that yields Django objects, but it'll almost |
| 27 | | always be a QuerySet). |
| | 26 | argument can be any iterator that yields Django model instances, but it'll |
| | 27 | almost always be a QuerySet). |
| 28 | 28 | |
| 29 | 29 | You can also use a serializer object directly:: |
| 30 | 30 | |