diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 77f933d..218a4ff 100644
a
|
b
|
and so on for as many models as you want to join. For example::
|
289 | 289 | Entry.objects.order_by('blog__name', 'headline') |
290 | 290 | |
291 | 291 | If you try to order by a field that is a relation to another model, Django will |
292 | | use the default ordering on the related model (or order by the related model's |
| 292 | use the default ordering on the related model, or order by the related model's |
293 | 293 | primary key if there is no :attr:`Meta.ordering |
294 | | <django.db.models.Options.ordering>` specified. For example:: |
| 294 | <django.db.models.Options.ordering>` specified. For example, since the ``Blog`` |
| 295 | model has no default ordering specified:: |
295 | 296 | |
296 | 297 | Entry.objects.order_by('blog') |
297 | 298 | |
… |
… |
primary key if there is no :attr:`Meta.ordering
|
299 | 300 | |
300 | 301 | Entry.objects.order_by('blog__id') |
301 | 302 | |
302 | | ...since the ``Blog`` model has no default ordering specified. |
| 303 | If ``Blog`` had ``ordering = ['name']``, then the first queryset would be |
| 304 | identical to:: |
| 305 | |
| 306 | Entry.objects.order_by('blog__name') |
303 | 307 | |
304 | 308 | .. versionadded:: 1.7 |
305 | 309 | |