summaryrefslogtreecommitdiff
path: root/docs/topics/class-based-views/generic-display.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/topics/class-based-views/generic-display.txt')
-rw-r--r--docs/topics/class-based-views/generic-display.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/topics/class-based-views/generic-display.txt b/docs/topics/class-based-views/generic-display.txt
index b734eb5d2b..8e39ad6c14 100644
--- a/docs/topics/class-based-views/generic-display.txt
+++ b/docs/topics/class-based-views/generic-display.txt
@@ -172,9 +172,9 @@ they're dealing with publishers here.
Well, if you're dealing with a model object, this is already done for you. When
you are dealing with an object or queryset, Django is able to populate the
-context using the lower cased version of the model class' name. This is
-provided in addition to the default ``object_list`` entry, but contains exactly
-the same data, i.e. ``publisher_list``.
+context using the lowercased version of the model class' name. This is provided
+in addition to the default ``object_list`` entry, but contains exactly the same
+data, i.e. ``publisher_list``.
If this still isn't a good match, you can manually set the name of the
context variable. The ``context_object_name`` attribute on a generic view