summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCorey Farwell <coreyf@rwell.org>2014-09-02 23:27:36 -0400
committerTim Graham <timograham@gmail.com>2014-09-03 11:49:33 -0400
commitde18a687ada58c5296f3f41b432aa2d26de8e3d9 (patch)
tree26e45c309b770083f90d0e4f0618dceb9a646b53 /docs
parent0d70bc63d02e973de932ec4a144b4158cdd35b41 (diff)
[1.7.x] Fixed typo in docs/topics/db/transactions.txt.
Backport of 4db75925be from master
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/db/transactions.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt
index 4ccca8ef55..288ecc4ef6 100644
--- a/docs/topics/db/transactions.txt
+++ b/docs/topics/db/transactions.txt
@@ -602,7 +602,7 @@ the block of code it controls; when exiting the block, it commits or
rollbacks, and switches back to auto mode.
So :func:`commit_on_success` really has two effects: it changes the
-transaction state and it defines an transaction block. Nesting will give the
+transaction state and it defines a transaction block. Nesting will give the
expected results in terms of transaction state, but not in terms of
transaction semantics. Most often, the inner block will commit, breaking the
atomicity of the outer block.