diff options
| author | David Smith <smithdc@gmail.com> | 2021-10-18 17:06:00 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2021-10-18 21:00:28 +0200 |
| commit | 69b0736fad1d1f0197409ca025b7bcdf5666ae62 (patch) | |
| tree | 10186ffaf53d0d472429a0e2a6e0bea60ea709b5 /docs/topics/class-based-views | |
| parent | e2f778d57947d168a875159e6df075255eea4bbc (diff) | |
Refs #32956 -- Changed docs to treat the acronym HTTP phonetically.
Diffstat (limited to 'docs/topics/class-based-views')
| -rw-r--r-- | docs/topics/class-based-views/mixins.txt | 2 |
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 |