Commit 04ed4234 authored by Karen Tracey's avatar Karen Tracey
Browse files

Fixed #9898 -- Added a missing 'e' to 'one'. Thanks gizzywump. Also...

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
parent dc4c95cd
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -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