- The ``pyramid_zodb``, ``pyramid_routesalchemy`` and ``pyramid_alchemy``

  paster templates now use a default "commit veto" hook when configuring the
  ``repoze.tm2`` transaction manager in ``development.ini``.  This prevents a
  transaction from being committed when the response status code is within
  the 400 or 500 ranges.  See also
  http://docs.repoze.org/tm2/#using-a-commit-veto.

1 files changed, 5 insertions, 3 deletions

diff --git a/docs/tutorials/wiki/basiclayout.rst b/docs/tutorials/wiki/basiclayout.rst
index 4017d7af8..884f17840 100644
--- a/docs/tutorials/wiki/basiclayout.rst
+++ b/docs/tutorials/wiki/basiclayout.rst
@@ -187,9 +187,11 @@ The ``egg:repoze.zodbconn#closer`` middleware is in the middle of the
 pipeline.  This is a piece of middleware which closes the ZODB connection
 opened by the ``PersistentApplicationFinder`` at the end of the request.
 
-The ``egg:repoze.tm#tm`` middleware is the last piece of middleware in the
-pipeline.  This commits a transaction near the end of the request unless
-there's an exception raised.
+The ``tm`` middleware is the last piece of middleware in the pipeline.  This
+commits a transaction near the end of the request unless there's an exception
+raised or the HTTP response code is an error code.  The ``tm`` refers to the
+``[filter:tm]`` section beneath the pipeline declaration, which configures
+the transaction manager.
 
 The final line in the ``[pipeline:main]`` section is ``tutorial``, which
 refers to the ``[app:tutorial]`` section above it.  The ``[app:tutorial]``