summaryrefslogtreecommitdiff
path: root/docs/whatsnew-1.0.rst
diff options
context:
space:
mode:
authorSteve Piercy <web@stevepiercy.com>2014-02-10 03:22:33 -0600
committerSteve Piercy <web@stevepiercy.com>2014-02-10 22:32:34 -0600
commit2033eeb3602f330930585678aac926749b9c22f7 (patch)
tree8c0b12ea184357772b7c703f8171095dfd5226d5 /docs/whatsnew-1.0.rst
parent5ac519452613b7bd5df22293c2ccb3b9c3597ef4 (diff)
downloadpyramid-2033eeb3602f330930585678aac926749b9c22f7.tar.gz
pyramid-2033eeb3602f330930585678aac926749b9c22f7.tar.bz2
pyramid-2033eeb3602f330930585678aac926749b9c22f7.zip
- Garden PR #1121
Diffstat (limited to 'docs/whatsnew-1.0.rst')
-rw-r--r--docs/whatsnew-1.0.rst7
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/whatsnew-1.0.rst b/docs/whatsnew-1.0.rst
index 8750863e7..9541f0a28 100644
--- a/docs/whatsnew-1.0.rst
+++ b/docs/whatsnew-1.0.rst
@@ -114,8 +114,11 @@ Scaffold Improvements
scaffolds 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.
+ the 400 or 500 ranges.
+
+ .. seealso::
+
+ See also http://docs.repoze.org/tm2/#using-a-commit-veto.
Terminology Changes
~~~~~~~~~~~~~~~~~~~