summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2013-08-30 21:05:36 -0400
committerTim Graham <timograham@gmail.com>2013-08-30 21:07:04 -0400
commit0089a9a8549828d38f6c49aaefb8364c034fa434 (patch)
tree4cea93b63f611be632444f84577861fdc465cea1 /docs
parent21a3efcf48559b3336ca1743d94c741a82feffd6 (diff)
[1.6.x] Fixed typo in docs/ref/models/options.txt
Backport of a89c856a7a from master
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/models/options.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt
index 9c58416e12..6413050cb7 100644
--- a/docs/ref/models/options.txt
+++ b/docs/ref/models/options.txt
@@ -248,7 +248,7 @@ Django quotes column and table names behind the scenes.
Determines if Django will use the pre-1.6
:meth:`django.db.models.Model.save()` algorithm. The old algorithm
uses ``SELECT`` to determine if there is an existing row to be updated.
- The new algorith tries an ``UPDATE`` directly. In some rare cases the
+ The new algorithm tries an ``UPDATE`` directly. In some rare cases the
``UPDATE`` of an existing row isn't visible to Django. An example is the
PostgreSQL ``ON UPDATE`` trigger which returns ``NULL``. In such cases the
new algorithm will end up doing an ``INSERT`` even when a row exists in