summaryrefslogtreecommitdiff
path: root/docs/tutorials/wiki2/definingviews.rst
diff options
context:
space:
mode:
authorStephen Martin <lockwood@opperline.com>2018-09-16 15:46:31 -0700
committerStephen Martin <lockwood@opperline.com>2018-09-16 15:46:31 -0700
commitf2520e5910861beac0199aa424ba282f856f79b3 (patch)
tree9b9919cc52da2abd25ad6bd940ffb98ab4ccc488 /docs/tutorials/wiki2/definingviews.rst
parentf1f15e9f4d98de268b65166c88cf1e5bbb8c1e79 (diff)
downloadpyramid-f2520e5910861beac0199aa424ba282f856f79b3.tar.gz
pyramid-f2520e5910861beac0199aa424ba282f856f79b3.tar.bz2
pyramid-f2520e5910861beac0199aa424ba282f856f79b3.zip
doc fixes
Diffstat (limited to 'docs/tutorials/wiki2/definingviews.rst')
-rw-r--r--docs/tutorials/wiki2/definingviews.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/tutorials/wiki2/definingviews.rst b/docs/tutorials/wiki2/definingviews.rst
index c75f6d5ba..b73338f52 100644
--- a/docs/tutorials/wiki2/definingviews.rst
+++ b/docs/tutorials/wiki2/definingviews.rst
@@ -133,9 +133,9 @@ The highlighted lines need to be added or edited.
We added some imports, and created a regular expression to find "WikiWords".
We got rid of the ``my_view`` view function and its decorator that was added
-when we originally rendered the ``sqlalchemy`` backend cookiecutter. It was
-only an example and isn't relevant to our application. We also deleted the
-``db_err_msg`` string.
+when originally rendered after we selected the ``sqlalchemy`` backend option in
+the cookiecutter. It was only an example and isn't relevant to our
+application. We also deleted the ``db_err_msg`` string.
Then we added four :term:`view callable` functions to our ``views/default.py``
module, as mentioned in the previous step:
@@ -436,8 +436,8 @@ There are several important things to note about this configuration:
the view.
Finally, we may delete the ``tutorial/templates/mytemplate.jinja2`` template
-that was provided by the ``sqlalchemy`` backend cookiecutter, as we have
-created our own templates for the wiki.
+that was provided by selecting the backend option of ``sqlalchemy``, as we
+have created our own templates for the wiki.
.. note::