diff options
| author | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2007-06-13 02:22:26 +0000 |
|---|---|---|
| committer | Malcolm Tredinnick <malcolm.tredinnick@gmail.com> | 2007-06-13 02:22:26 +0000 |
| commit | 1e57d6ccf0c0d005926b8620f34ecf69189eb2e9 (patch) | |
| tree | d9f8e7dbc69cc3010a6c1b2385307c3ccf060466 /docs/newforms.txt | |
| parent | 9bc8941f678ed5619c522e65de91be33bf7534a7 (diff) | |
Fixed #4547 -- Trivial typo fixing time. Thanks, Grant Kelly.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@5468 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/newforms.txt')
| -rw-r--r-- | docs/newforms.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/newforms.txt b/docs/newforms.txt index e37d76643a..5fe6f95899 100644 --- a/docs/newforms.txt +++ b/docs/newforms.txt @@ -1224,7 +1224,7 @@ Form validation happens when the data is cleaned. If you want to customise this process, there are various places you can change, each one serving a different purpose. Thee types of cleaning methods are run during form processing. These are normally executed when you call the ``is_valid()`` -method on a form. There are other things that can kick of cleaning and +method on a form. There are other things that can trigger cleaning and validation (accessing the ``errors`` attribute or calling ``full_clean()`` directly), but normally they won't be needed. @@ -1234,7 +1234,7 @@ the ``ValidationError`` constructor. If no ``ValidationError`` is raised, the method should return the cleaned (normalised) data as a Python object. If you detect multiple errors during a cleaning method and wish to signal all -of them to the form submittor, it is possible to pass a list of errors to the +of them to the form submitter, it is possible to pass a list of errors to the ``ValidationError`` constructor. The three types of cleaning methods are: |