summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2011-01-18 18:08:57 -0700
committerCasey Duncan <casey.duncan@gmail.com>2011-01-18 18:08:57 -0700
commit4dc751e613198c1aa87a47c0d5cf5047c9cfe9ba (patch)
tree1ee566d5cbae1976397cfbe6435cbe01aad929e2 /docs
parentbd3c7d796f940f8b7296631b8a3466fd00bc16f7 (diff)
downloadpyramid-4dc751e613198c1aa87a47c0d5cf5047c9cfe9ba.tar.gz
pyramid-4dc751e613198c1aa87a47c0d5cf5047c9cfe9ba.tar.bz2
pyramid-4dc751e613198c1aa87a47c0d5cf5047c9cfe9ba.zip
fix spacing
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/hooks.rst9
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/narr/hooks.rst b/docs/narr/hooks.rst
index 96515c195..61e8aa1bf 100644
--- a/docs/narr/hooks.rst
+++ b/docs/narr/hooks.rst
@@ -365,10 +365,11 @@ parameter: ``request``. For example:
transaction.commit()
request.add_finished_callback(commit_callback)
-Finished callbacks are called in the order they're added ( first- to
-most-recently- added). Finished callbacks (unlike a :term:`response
-callback`) are *always* called, even if an exception happens in application
-code that prevents a response from being generated.
+Finished callbacks are called in the order they're added
+(first-to-most-recently-added). Finished callbacks (unlike a
+:term:`response callback`) are *always* called, even if an exception
+happens in application code that prevents a response from being
+generated.
The set of finished callbacks associated with a request are called *very
late* in the processing of that request; they are essentially the very last