summaryrefslogtreecommitdiffstats
path: root/user_guide_src/source
diff options
context:
space:
mode:
authorAndrey Andreev <narf@devilix.net>2015-02-05 15:37:48 +0100
committerAndrey Andreev <narf@devilix.net>2015-02-05 15:37:48 +0100
commitcf2607d9c7f5d0ea6cb79fc75a9f2f3bcb893889 (patch)
tree854a1fd4327b9e6e5d66c2951bf781d19f8c3f4c /user_guide_src/source
parent514896e1b0df12bc82dac785fa7c9ed4f62585e6 (diff)
parentb4b9bd3fc5bed95c19cd394d9fbf29772e94614a (diff)
Merge pull request #3568 from schwemmer/patch-1
[ci skip] Update transactions.rst
Diffstat (limited to 'user_guide_src/source')
-rw-r--r--user_guide_src/source/database/transactions.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/user_guide_src/source/database/transactions.rst b/user_guide_src/source/database/transactions.rst
index e9190e59a..2e6d4b477 100644
--- a/user_guide_src/source/database/transactions.rst
+++ b/user_guide_src/source/database/transactions.rst
@@ -21,7 +21,7 @@ approach because it greatly simplifies the process of running
transactions. In most cases all that is required are two lines of code.
Traditionally, transactions have required a fair amount of work to
-implement since they demand that you to keep track of your queries and
+implement since they demand that you keep track of your queries and
determine whether to commit or rollback based on the success or failure
of your queries. This is particularly cumbersome with nested queries. In
contrast, we've implemented a smart transaction system that does all