summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorKaren Tracey <kmtracey@gmail.com>2008-12-21 04:23:35 +0000
committerKaren Tracey <kmtracey@gmail.com>2008-12-21 04:23:35 +0000
commit26554aa6b2444e1e3b1641bec773229d292c5587 (patch)
treec949b0dbf5de13efe0c38ddaa3f7164c27b1d5a8 /docs
parent3c9aaaef34366431773e1fd1fab65bbee42a9c24 (diff)
[1.0.X] Fixed #9898 -- Added a missing 'e' to 'one'. Thanks gizzywump. Also Americanized specialised while in the area, per contributing's guideline.
r9662 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9663 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/forms/modelforms.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt
index 2f170fe9f1..0166d4d08a 100644
--- a/docs/topics/forms/modelforms.txt
+++ b/docs/topics/forms/modelforms.txt
@@ -196,7 +196,7 @@ accepts either ``True`` or ``False``. If you call ``save()`` with
``commit=False``, then it will return an object that hasn't yet been saved to
the database. In this case, it's up to you to call ``save()`` on the resulting
model instance. This is useful if you want to do custom processing on the
-object before saving it, or if you want to use on of the specialised
+object before saving it, or if you want to use one of the specialized
:ref:`model saving options <ref-models-force-insert>`. ``commit`` is ``True`` by default.
Another side effect of using ``commit=False`` is seen when your model has