summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2011-09-07 12:45:28 -0400
committerChris McDonough <chrism@plope.com>2011-09-07 12:45:28 -0400
commit1bca77cc705622da6aa1b163917a22f35e8c01d3 (patch)
treef0afc353ec5ca0f960c90b68b30a146b9d61591c /docs
parent31dc8d526dc58bf56179d6a7417a83fefdc7f475 (diff)
downloadpyramid-1bca77cc705622da6aa1b163917a22f35e8c01d3.tar.gz
pyramid-1bca77cc705622da6aa1b163917a22f35e8c01d3.tar.bz2
pyramid-1bca77cc705622da6aa1b163917a22f35e8c01d3.zip
chronology
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/introduction.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index eefac9812..a672c82ad 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -372,7 +372,7 @@ Transaction management
~~~~~~~~~~~~~~~~~~~~~~
Pyramid's :term:`scaffold` system renders projects that include a
-*transaction management* system, also stolen from Zope. When you use this
+*transaction management* system, stolen from Zope. When you use this
transaction management system, you cease being responsible for committing
your data anymore. Instead, Pyramid takes care of committing: it commits at
the end of a request or aborts if there's an exception. Why is that a good