Fixed #15990 - Simplified a sentence regarding form validation for ModelForms;…

Fixed #15990 - Simplified a sentence regarding form validation for ModelForms; thanks jblaine for the suggestion.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16329 bcc190cf-cafb-0310-a4f2-bffc1f526a37

docs/topics/forms/modelforms.txt

@@ -195,14 +195,11 @@ we'll discuss in a moment.)::
 The ``is_valid()`` method and ``errors``
 ----------------------------------------
 
-.. versionchanged:: 1.2
-
 The first time you call ``is_valid()`` or access the ``errors`` attribute of a
-``ModelForm`` has always triggered form validation, but as of Django 1.2, it
-will also trigger :ref:`model validation <validating-objects>`. This has the
-side-effect of cleaning the model you pass to the ``ModelForm`` constructor.
-For instance, calling ``is_valid()`` on your form will convert any date fields
-on your model to actual date objects.
+``ModelForm`` triggers form validation as well as :ref:`model validation
+<validating-objects>`. This has the side-effect of cleaning the model you pass
+to the ``ModelForm`` constructor. For instance, calling ``is_valid()`` on your
+form will convert any date fields on your model to actual date objects.
 
 
 The ``save()`` method
@@ -359,7 +356,7 @@ Overriding the default field types or widgets
 ---------------------------------------------
 
 .. versionadded:: 1.2
- 	The ``widgets`` attribute is new in Django 1.2.
+    The ``widgets`` attribute is new in Django 1.2.
 
 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