summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSteve Piercy <web@stevepiercy.com>2018-08-25 01:28:31 -0700
committerSteve Piercy <web@stevepiercy.com>2018-08-25 01:28:31 -0700
commit90bd6061e18143e9619bfbe9dc04e10230f268f4 (patch)
tree1a4162cb3950958c0dc1d360b6cff41ae3d9e3ef /docs
parentb5f4e4937ef43acae17c32444706aac758935aac (diff)
downloadpyramid-90bd6061e18143e9619bfbe9dc04e10230f268f4.tar.gz
pyramid-90bd6061e18143e9619bfbe9dc04e10230f268f4.tar.bz2
pyramid-90bd6061e18143e9619bfbe9dc04e10230f268f4.zip
Remove extra "that"
Diffstat (limited to 'docs')
-rw-r--r--docs/tutorials/wiki2/definingviews.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/tutorials/wiki2/definingviews.rst b/docs/tutorials/wiki2/definingviews.rst
index 2eb78cb00..700a105b1 100644
--- a/docs/tutorials/wiki2/definingviews.rst
+++ b/docs/tutorials/wiki2/definingviews.rst
@@ -267,7 +267,7 @@ which will be used as the action of the generated form.
Since our ``request.dbsession`` defined in the previous chapter is
registered with the ``pyramid_tm`` transaction manager, any changes we make
- to objects managed by the that session will be committed automatically. In
+ to objects managed by the session will be committed automatically. In
the event that there was an error (even later, in our template code), the
changes would be aborted. This means the view itself does not need to
concern itself with commit/rollback logic.