- All references to Pyramid-the-application were changed from :mod:`pyramid`

  to :app:`Pyramid`.  A custom role setting was added to ``docs/conf.py`` to
  allow for this.  (internal)

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/tutorials/wiki/basiclayout.rst b/docs/tutorials/wiki/basiclayout.rst
index d129ff7ec..85cfc825b 100644
--- a/docs/tutorials/wiki/basiclayout.rst
+++ b/docs/tutorials/wiki/basiclayout.rst
@@ -4,7 +4,7 @@ Basic Layout
 
 The starter files generated by the ``pyramid_zodb`` template are basic,
 but they provide a good orientation for the high-level patterns common
-to most :term:`traversal` -based :mod:`pyramid` (and :term:`ZODB`
+to most :term:`traversal` -based :app:`Pyramid` (and :term:`ZODB`
 based) projects.
 
 The source code for this tutorial stage can be browsed via
@@ -101,7 +101,7 @@ following:
 Content Models with ``models.py``
 ---------------------------------
 
-:mod:`pyramid` often uses the word :term:`model` when talking about
+:app:`Pyramid` often uses the word :term:`model` when talking about
 content resources arranged in the hierarchical *object graph*
 consulted by :term:`traversal`.  The ``models.py`` file is where the
 ``pyramid_zodb`` Paster template put the classes that implement our
@@ -124,7 +124,7 @@ Here is the source for ``models.py``:
 
 #. *Lines 6-12*.  ``appmaker`` is used to return the *application
    root* object.  It is called on *every request* to the
-   :mod:`pyramid` application.  It also performs bootstrapping by
+   :app:`Pyramid` application.  It also performs bootstrapping by
    *creating* an application root (inside the ZODB root object) if one
    does not already exist.