From 7e322b5908bf5ec255c90c615d1b45b358ecee5f Mon Sep 17 00:00:00 2001 From: Justin Bronn Date: Wed, 2 Jan 2008 16:57:53 +0000 Subject: gis: Merged revisions 6920-6989 via svnmerge from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/gis@6990 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/modelforms.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/modelforms.txt') diff --git a/docs/modelforms.txt b/docs/modelforms.txt index 372abf9811..0136540bed 100644 --- a/docs/modelforms.txt +++ b/docs/modelforms.txt @@ -277,7 +277,7 @@ model fields: any attempt to ``save()`` a ``ModelForm`` with missing fields will fail. To avoid this failure, you must instantiate your model with initial values for the missing, but required fields, or use ``save(commit=False)`` and - manually set anyextra required fields:: + manually set any extra required fields:: instance = Instance(required_field='value') form = InstanceForm(request.POST, instance=instance) @@ -296,7 +296,7 @@ Overriding the default field types ---------------------------------- The default field types, as described in the "Field types" table above, are -sensible defaults; if you have a ``DateField`` in your model, chances are you'd +sensible defaults. If you have a ``DateField`` in your model, chances are you'd want that to be represented as a ``DateField`` in your form. But ``ModelForm`` gives you the flexibility of changing the form field type for a given model field. You do this by declaratively specifying fields like -- cgit v1.3