doc fixes

4 files changed, 11 insertions, 12 deletions

diff --git a/docs/tutorials/wiki/basiclayout.rst b/docs/tutorials/wiki/basiclayout.rst
index d435e0767..0005ba3cb 100644
--- a/docs/tutorials/wiki/basiclayout.rst
+++ b/docs/tutorials/wiki/basiclayout.rst
@@ -4,10 +4,10 @@
 Basic Layout
 ============
 
-The starter files generated by the ``zodb`` backend cookiecutter are very
-basic, but they provide a good orientation for the high-level patterns common
-to most :term:`traversal`-based (and :term:`ZODB`-based) :app:`Pyramid`
-projects.
+The starter files generated by selecting the ``zodb`` backend in the
+cookiecutter are very basic, but they provide a good orientation for the
+high-level patterns common to most :term:`traversal`-based (and
+:term:`ZODB`-based) :app:`Pyramid` projects.
 
 
 Application configuration with ``__init__.py``
diff --git a/docs/tutorials/wiki/definingviews.rst b/docs/tutorials/wiki/definingviews.rst
index 91b90e911..d584a1b41 100644
--- a/docs/tutorials/wiki/definingviews.rst
+++ b/docs/tutorials/wiki/definingviews.rst
@@ -99,8 +99,8 @@ like the following:
 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 ``zodb`` backend cookiecutter.  It was only an example and
-isn't relevant to our application.
+when originally rendered after we selected the ``zodb`` backend option in the
+cookiecutter.  It was only an example and isn't relevant to our application.
 
 Then we added four :term:`view callable` functions to our ``views.py``
 module:
diff --git a/docs/tutorials/wiki/installation.rst b/docs/tutorials/wiki/installation.rst
index c7047664a..bd8ea9e5c 100644
--- a/docs/tutorials/wiki/installation.rst
+++ b/docs/tutorials/wiki/installation.rst
@@ -365,11 +365,10 @@ page.  You can read more about the purpose of the icon at
 application while you develop.
 
 
-Decisions the ``zodb`` backend cookiecutter has made for you
-------------------------------------------------------------
+Decisions the cookiecutter backend option ``zodb`` has made for you
+-------------------------------------------------------------------
 
-Creating a project using the ``zodb`` backend cookiecutter makes the following
-assumptions:
+When creating a project and selecting the backend option of ``zodb``, the cookiecutter makes the following assumptions:
 
 - You are willing to use :term:`ZODB` for persistent storage.
 
diff --git a/docs/tutorials/wiki/tests.rst b/docs/tutorials/wiki/tests.rst
index 81b020594..353813e91 100644
--- a/docs/tutorials/wiki/tests.rst
+++ b/docs/tutorials/wiki/tests.rst
@@ -16,7 +16,7 @@ We write tests for the ``model`` classes and the ``appmaker``.  Changing
 we'll write a test class for the ``appmaker``.
 
 To do so, we'll retain the ``tutorial.tests.ViewTests`` class that was
-generated as part of the ``zodb`` backend cookiecutter.  We'll add three test
+generated from choosing the ``zodb`` backend option.  We'll add three test
 classes: one for the ``Page`` model named ``PageModelTests``, one for the
 ``Wiki`` model named ``WikiModelTests``, and one for the appmaker named
 ``AppmakerTests``.
@@ -26,7 +26,7 @@ Test the views
 
 We'll modify our ``tests.py`` file, adding tests for each view function we
 added previously.  As a result, we'll delete the ``ViewTests`` class that the
-``zodb`` backend cookiecutter provided, and add four other test classes:
+``zodb`` backend option provided, and add four other test classes:
 ``ViewWikiTests``, ``ViewPageTests``, ``AddPageTests``, and ``EditPageTests``.
 These test the ``view_wiki``, ``view_page``, ``add_page``, and ``edit_page``
 views.