summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authoraruseni <aruseni.magiku@gmail.com>2014-11-09 22:31:53 +0100
committerTim Graham <timograham@gmail.com>2014-11-10 15:36:42 +0100
commit006451f8943af2974a9a2c105dbc8470a33624c1 (patch)
treebec74542e70ee1a991d10c535f33db50a2758a86 /docs
parent091f5b5a4e83759cf9d96fe2b9f56183b49765f6 (diff)
Fixed a typo in 1.6 release notes.
Diffstat (limited to 'docs')
-rw-r--r--docs/releases/1.6.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt
index 94021adc4a..1a49cdf2a6 100644
--- a/docs/releases/1.6.txt
+++ b/docs/releases/1.6.txt
@@ -1183,7 +1183,7 @@ create a ``ModelForm`` that uses all fields for a model.
For this reason, if you use these views for editing models, you must also supply
the ``fields`` attribute (new in Django 1.6), which is a list of model fields
and works in the same way as the :class:`~django.forms.ModelForm`
-``Meta.fields`` attribute. Alternatively, you can set set the ``form_class``
+``Meta.fields`` attribute. Alternatively, you can set the ``form_class``
attribute to a ``ModelForm`` that explicitly defines the fields to be used.
Defining an ``UpdateView`` or ``CreateView`` subclass to be used with a model
but without an explicit list of fields is deprecated.