--- SimpleWidgetForm	2008-03-23 08:25:48.000000000 -0700
+++ SimpleWidgetForm_update	2008-03-23 09:19:23.000000000 -0700
@@ -182,7 +182,7 @@
 
 We'll talk about the ``tg_errors`` argument later. First, let's have a look
 how the form widget is used in the template. Here's the body contents of
-``formstutorial/templates/index.kid``::
+``formstutorial/templates/add.kid``::
 
     <p py:content="form.display(submit_text='Add Comment')">Comment form</p>
 
@@ -296,14 +296,18 @@
 If you look at the definition of ``CommentFields`` repeated above, you'll see
 that there is a validator for each of the first three fields. These validators
 are part of the ``turbogears.validators`` package, which is a thin wrapper
-around Ian Bicking's `FormEncode`_ project. Since all values in a form are
-sent as strings, validators both convert the value to the appropriate Python
-type and check that the value matches a criteria in one step because one
-usually requires the other. For example, if your validator requires a numeric
-input be greater than 5 and you get ``"10"``, you have to convert ``"10"`` to
-the int ``10`` before a meaningful comparison can be made. In this case, we're
-not doing type conversion for any of our fields, but it's a useful thing to
-know.
+around Ian Bicking's `FormEncode`_ project. Since all values in a form are sent
+as strings, validators will both,
+
+#. convert the value to the appropriate Python type, and ...
+#. check that the value matches your designated criteria.
+
+Validators perform the two steps together because the value criteria frequently
+mean little until type conversion has taken place, or vice versa. In our
+tutorial, no type conversions were needed. But if, for example, your validator
+requires a numeric input be greater than 5 but your form input was ``"10"``,
+you have to convert ``"10"`` to the int ``10`` before a meaningful comparison
+can be made. 
 
 .. _FormEncode: http://www.formencode.org