From 04ed4234690c43f6cd294f1cfb8a978e13378903 Mon Sep 17 00:00:00 2001 From: Karen Tracey Date: Sun, 21 Dec 2008 04:17:46 +0000 Subject: [PATCH] Fixed #9898 -- Added a missing 'e' to 'one'. Thanks gizzywump. Also Americanized specialised while in the area, per contributing's guideline. git-svn-id: http://code.djangoproject.com/svn/django/trunk@9662 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/forms/modelforms.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index 2f170fe9f1a..0166d4d08a9 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 `. ``commit`` is ``True`` by default. Another side effect of using ``commit=False`` is seen when your model has