Negligible change to docs/newforms.txt

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

1 files changed, 8 insertions, 4 deletions

diff --git a/docs/newforms.txt b/docs/newforms.txt
index c4986eb45e..ec721effc4 100644
--- a/docs/newforms.txt
+++ b/docs/newforms.txt
@@ -22,7 +22,7 @@ release, our plan is to do the following:
           from django import oldforms as forms # new
 
     * At an undecided future date, we will move the current ``django.newforms``
-      to ``django.forms``. This will be a backwards-incompatible change, and 
+      to ``django.forms``. This will be a backwards-incompatible change, and
       anybody who is still using the old version of ``django.forms`` at that
       time will need to change their import statements, as described in the
       previous bullet.
@@ -282,6 +282,13 @@ example, in the ``ContactForm`` example, the fields are defined in the order
 ``subject``, ``message``, ``sender``, ``cc_myself``. To reorder the HTML
 output, just change the order in which those fields are listed in the class.
 
+Using forms to validate data
+----------------------------
+
+In addition to HTML form display, a ``Form`` class is responsible for
+validating data.
+
+
 More coming soon
 ================
 
@@ -290,9 +297,6 @@ http://code.djangoproject.com/browser/django/trunk/tests/regressiontests/forms/t
 -- the unit tests for ``django.newforms``. This can give you a good idea of
 what's possible.
 
-Using forms to validate data
-----------------------------
-
 Using forms with templates
 ==========================