summaryrefslogtreecommitdiff
path: root/docs/topics/class-based-views
diff options
context:
space:
mode:
authorDavid Smith <smithdc@gmail.com>2021-10-18 17:06:00 +0100
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2021-10-19 06:33:00 +0200
commit6aa917383faaa80e70c6a8a8bc0f52f088434a84 (patch)
tree266a920665a19e685cd1809e276b234f444e0b39 /docs/topics/class-based-views
parentc067a2b68fe2701608b34ac4a538e1f9dba0e9f2 (diff)
[4.0.x] Refs #32956 -- Changed docs to treat the acronym HTTP phonetically.
Backport of 69b0736fad1d1f0197409ca025b7bcdf5666ae62 from main
Diffstat (limited to 'docs/topics/class-based-views')
-rw-r--r--docs/topics/class-based-views/mixins.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/class-based-views/mixins.txt b/docs/topics/class-based-views/mixins.txt
index 7b193ea7f0..08a1ec1af9 100644
--- a/docs/topics/class-based-views/mixins.txt
+++ b/docs/topics/class-based-views/mixins.txt
@@ -653,7 +653,7 @@ same behavior -- except for the format of the response.
If you want to be really adventurous, you could even mix a
:class:`~django.views.generic.detail.DetailView` subclass that is able
to return *both* HTML and JSON content, depending on some property of
-the HTTP request, such as a query argument or a HTTP header. Mix in both the
+the HTTP request, such as a query argument or an HTTP header. Mix in both the
``JSONResponseMixin`` and a
:class:`~django.views.generic.detail.SingleObjectTemplateResponseMixin`,
and override the implementation of