summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2011-09-09 03:47:34 -0700
committerChris McDonough <chrism@plope.com>2011-09-09 03:47:34 -0700
commitc214c747b5ba81051ab1e8c8ac1b82fc54e889cf (patch)
treea409dab99045a69a4fcb5f42203f97f9ac32a57d /docs
parent43850d404e77f050930ec32226670c54f78be347 (diff)
parent157d3256acf633bb21cfd09e542c639672c2c579 (diff)
downloadpyramid-c214c747b5ba81051ab1e8c8ac1b82fc54e889cf.tar.gz
pyramid-c214c747b5ba81051ab1e8c8ac1b82fc54e889cf.tar.bz2
pyramid-c214c747b5ba81051ab1e8c8ac1b82fc54e889cf.zip
Merge pull request #272 from stevepiercy/patch-5
Correct spelling of "chages" to "changes".
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 b2fb95c42..ecec846cf 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -503,7 +503,7 @@ data if you're not extremely careful. Some data will have been written to
the database that probably should not have. Having a centralized commit
point saves you from needing to think about this; it's great for lazy people
who also care about data integrity. Either the request completes
-successfully, and all chages are committed, or it does not, and all changes
+successfully, and all changes are committed, or it does not, and all changes
are aborted.
Also, Pyramid's transaction management system allows you to synchronize