* A validator, in contrast, is more generic and can do validations in the full action context,
* involving more than one field (or even no field at all) in validation rule.
* Most validations can be defined on per field basis. This should be preferred over
- * non-field validation where
ever possible, as field validator messages are bound to the
+ * non-field validation wherever possible, as field validator messages are bound to the
* related field and will be presented next to the corresponding input element in the
* <!-- END SNIPPET: fieldValidators -->
* <field name="bar2">
* <field-validator type="regex">
- * <param name="
+ * <param name="">[0-9],[0-9]</param>
* <message>The value of bar2 must be in the format "x, y", where x and y are between 0 and 9</message>
* <p><b>NOTE:</b> Since validation rules are in an XML file, you must make sure
* you escape special characters. For example, notice that in the expression
- * validator rule above we use ">" instead of "
>". Consult a resource on XML
+ * validator rule above we use ">" instead of "". Consult a resource on XML
* for the full list of characters that must be escaped. The most commonly used
- * characters that must be escaped are: & (use &
), > (user >), and < (use <).</p>
+ * characters that must be escaped are: & (use & (user >), and (use <).</p>
* <p>Here is an example of a parameterized message:</p>
* <p>This will pull the min and max parameters from the IntRangeFieldValidator and