diff options
| author | eltronix <lt.eltronix@gmail.com> | 2016-04-19 03:25:54 +0300 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-04-18 20:26:13 -0400 |
| commit | f5b8e9b2820177dae2bf392867641d097438f85e (patch) | |
| tree | 6b8c4ee4794d150a0b6669b4f3a69d13b8f1d5b9 /docs | |
| parent | 51400cbce8165d46fdd380e80a95b6248929b38b (diff) | |
[1.9.x] Fixed typo in docs/topics/class-based-views/mixins.txt
Backport of f43da05cc5c76102c04fd2e76b4bada880265dbe from master
Diffstat (limited to 'docs')
| -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 0a8b7d43fd..1364af1ce3 100644 --- a/docs/topics/class-based-views/mixins.txt +++ b/docs/topics/class-based-views/mixins.txt @@ -400,7 +400,7 @@ To show what happens when you try to get more sophisticated, we show an example that sacrifices readability and maintainability when there is a simpler solution. First, let's look at a naive attempt to combine :class:`~django.views.generic.detail.DetailView` with -:class:`~django.views.generic.edit.FormMixin` to enable use to +:class:`~django.views.generic.edit.FormMixin` to enable us to ``POST`` a Django :class:`~django.forms.Form` to the same URL as we're displaying an object using :class:`DetailView`. |