summaryrefslogtreecommitdiff
path: root/docs/narr/advanced-features.rst
diff options
context:
space:
mode:
authorStephen Martin <lockwood@opperline.com>2018-09-16 15:46:31 -0700
committerStephen Martin <lockwood@opperline.com>2018-09-16 15:46:31 -0700
commitf2520e5910861beac0199aa424ba282f856f79b3 (patch)
tree9b9919cc52da2abd25ad6bd940ffb98ab4ccc488 /docs/narr/advanced-features.rst
parentf1f15e9f4d98de268b65166c88cf1e5bbb8c1e79 (diff)
downloadpyramid-f2520e5910861beac0199aa424ba282f856f79b3.tar.gz
pyramid-f2520e5910861beac0199aa424ba282f856f79b3.tar.bz2
pyramid-f2520e5910861beac0199aa424ba282f856f79b3.zip
doc fixes
Diffstat (limited to 'docs/narr/advanced-features.rst')
-rw-r--r--docs/narr/advanced-features.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/narr/advanced-features.rst b/docs/narr/advanced-features.rst
index 71985e49c..b169aad95 100644
--- a/docs/narr/advanced-features.rst
+++ b/docs/narr/advanced-features.rst
@@ -51,7 +51,7 @@ This approach allows you to develop view code that is simpler, more easily under
Stop Worrying About Transactions
--------------------------------
-:app:`Pyramid`\ 's :term:`cookiecutter`\ renders projects that include a *transaction management* system. When you use this system, you can stop worrying about when to commit your changes, :app:`Pyramid` handles it for you. The system will commit at the end of a request or abort if there was an exception.
+:app:`Pyramid`\ 's :term:`cookiecutter` renders projects that include a *transaction management* system. When you use this system, you can stop worrying about when to commit your changes, :app:`Pyramid` handles it for you. The system will commit at the end of a request or abort if there was an exception.
Why is that a good thing? Imagine a situation where you manually commit a change to your persistence layer. It's very likely that other framework code will run *after* your changes are done. If an error happens in that other code, you can easily wind up with inconsistent data if you're not extremely careful.