diff options
| author | Tom Christie | 2013-06-02 19:50:59 +0100 | 
|---|---|---|
| committer | Tom Christie | 2013-06-02 19:50:59 +0100 | 
| commit | bed5bffb73d0de305aeda8b4ba90eb7ae924dcd9 (patch) | |
| tree | 93a9fbc2db54dee3a307e2f694a4fe7fe2a6c565 | |
| parent | 8b73dce51da9f87940a6c18aef31020ba7ee14aa (diff) | |
| parent | 27520b04e1c629235eb5adeaafa27b22cab0a451 (diff) | |
| download | django-rest-framework-bed5bffb73d0de305aeda8b4ba90eb7ae924dcd9.tar.bz2 | |
Merge branch 'master' of https://github.com/tomchristie/django-rest-framework
| -rw-r--r-- | docs/api-guide/filtering.md | 2 | 
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/api-guide/filtering.md b/docs/api-guide/filtering.md index 4242f40d..05c997a3 100644 --- a/docs/api-guide/filtering.md +++ b/docs/api-guide/filtering.md @@ -231,7 +231,7 @@ Multiple orderings may also be specified:  If an `ordering` attribute is set on the view, this will be used as the default ordering. -Typicaly you'd instead control this by setting `order_by` on the initial queryset, but using the `ordering` parameter on the view allows you to specify the ordering in a way that it can then be passed automatically as context to a rendered template.  This makes it possible to automatically render column headers differently if they are being used to order the results. +Typically you'd instead control this by setting `order_by` on the initial queryset, but using the `ordering` parameter on the view allows you to specify the ordering in a way that it can then be passed automatically as context to a rendered template.  This makes it possible to automatically render column headers differently if they are being used to order the results.      class UserListView(generics.ListAPIView):          queryset = User.objects.all()  | 
