From 8c3e0eb1c16abbcded3503b4ea3473b353520f61 Mon Sep 17 00:00:00 2001 From: Jon Dufresne Date: Tue, 25 Sep 2018 07:30:18 -0700 Subject: Normalized spelling of "lowercase" and "lowercased". --- docs/topics/class-based-views/generic-display.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/topics/class-based-views') 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 -- cgit v1.3