diff options
Diffstat (limited to 'docs/topics')
| -rw-r--r-- | docs/topics/class-based-views/mixins.txt | 2 | ||||
| -rw-r--r-- | docs/topics/testing/tools.txt | 2 |
2 files changed, 2 insertions, 2 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 diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index 40789b98fa..3d955503b1 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -717,7 +717,7 @@ A subclass of :class:`unittest.TestCase` that adds this functionality: * Verifying that a template :meth:`has/hasn't been used to generate a given response content <SimpleTestCase.assertTemplateUsed>`. * Verifying that two :meth:`URLs <SimpleTestCase.assertURLEqual>` are equal. - * Verifying a HTTP :meth:`redirect <SimpleTestCase.assertRedirects>` is + * Verifying an HTTP :meth:`redirect <SimpleTestCase.assertRedirects>` is performed by the app. * Robustly testing two :meth:`HTML fragments <SimpleTestCase.assertHTMLEqual>` for equality/inequality or :meth:`containment <SimpleTestCase.assertInHTML>`. |