From 1e57d6ccf0c0d005926b8620f34ecf69189eb2e9 Mon Sep 17 00:00:00 2001
From: Malcolm Tredinnick <malcolm.tredinnick@gmail.com>
Date: Wed, 13 Jun 2007 02:22:26 +0000
Subject: [PATCH] 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
---
 docs/newforms.txt | 4 ++--
 1 file 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: