diff options
| author | Craig Teegarden | 2013-05-31 18:02:47 -0400 | 
|---|---|---|
| committer | Craig Teegarden | 2013-05-31 18:02:47 -0400 | 
| commit | 9154b09eb98593411605a35e6aa342e3c00d63ce (patch) | |
| tree | 5aa8f83a8d99c970451d801bb717a67b98b687e6 | |
| parent | 363b342548a41bfdcc3358595cd9d1de288c4962 (diff) | |
| download | django-rest-framework-9154b09eb98593411605a35e6aa342e3c00d63ce.tar.bz2 | |
fix typo
| -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()  | 
