diff options
| author | Steve Piercy <web@stevepiercy.com> | 2011-09-09 03:30:48 -0700 |
|---|---|---|
| committer | Steve Piercy <web@stevepiercy.com> | 2011-09-09 03:30:48 -0700 |
| commit | 157d3256acf633bb21cfd09e542c639672c2c579 (patch) | |
| tree | 7caf6fb532ef1d7c96ccf8d82cd7a5310551523c /docs | |
| parent | 82dcba5bf8d6d024f42ded1565d30c314b8e8b4b (diff) | |
| download | pyramid-157d3256acf633bb21cfd09e542c639672c2c579.tar.gz pyramid-157d3256acf633bb21cfd09e542c639672c2c579.tar.bz2 pyramid-157d3256acf633bb21cfd09e542c639672c2c579.zip | |
Correct spelling of "chages" to "changes".
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/narr/introduction.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst index 8694556b2..6bf2665ee 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 |