summaryrefslogtreecommitdiff
path: root/docs/topics/class-based-views
diff options
context:
space:
mode:
authorDavid Smith <smithdc@gmail.com>2021-07-23 07:48:16 +0100
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2021-07-29 06:24:12 +0200
commit1024b5e74a7166313ad4e4975a15e90dccd3ec5f (patch)
tree05d75177f183de5e3c58dbf25a3f71ff4a5c820a /docs/topics/class-based-views
parentacde91745656a852a15db7611c08cabf93bb735b (diff)
Fixed 32956 -- Lowercased spelling of "web" and "web framework" where appropriate.
Diffstat (limited to 'docs/topics/class-based-views')
-rw-r--r--docs/topics/class-based-views/generic-display.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/class-based-views/generic-display.txt b/docs/topics/class-based-views/generic-display.txt
index e7ba5c99a2..cb35296149 100644
--- a/docs/topics/class-based-views/generic-display.txt
+++ b/docs/topics/class-based-views/generic-display.txt
@@ -2,9 +2,9 @@
Built-in class-based generic views
==================================
-Writing Web applications can be monotonous, because we repeat certain patterns
+Writing web applications can be monotonous, because we repeat certain patterns
again and again. Django tries to take away some of that monotony at the model
-and template layers, but Web developers also experience this boredom at the view
+and template layers, but web developers also experience this boredom at the view
level.
Django's *generic views* were developed to ease that pain. They take certain