- 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/cmf/content.rst b/docs/tutorials/cmf/content.rst
index a8b2b8124..85e5b5fbc 100644
--- a/docs/tutorials/cmf/content.rst
+++ b/docs/tutorials/cmf/content.rst
@@ -10,7 +10,7 @@ code which generates an instance of that content.  It is possible to
 construct and enumerate content types using APIs defined on the types
 tool.
 
-:mod:`pyramid` itself has no such concept, but an addon package named
+:app:`Pyramid` itself has no such concept, but an addon package named
 :term:`repoze.lemonade` has a barebones replacement.
 
 Factory Type Information
@@ -22,7 +22,7 @@ initial view name, a factory, and a number of security settings with a
 type name.  Each type information object knows how to manufacture
 content objects that match its type.
 
-:mod:`pyramid` certainly enforces none of these concepts in any
+:app:`Pyramid` certainly enforces none of these concepts in any
 particular way, but :term:`repoze.lemonade` does.
 
 ``repoze.lemonade`` Content
@@ -51,7 +51,7 @@ of helper functions which allow you to:
           content-agnostic unit tests or if you need to get an
           enumerated subset of content type information to aid in UI
           generation.  That said, this *is* a tutorial about how to
-          get CMF-like features in :mod:`pyramid`, so we'll assume
+          get CMF-like features in :app:`Pyramid`, so we'll assume
           the pattern is useful to readers.
 
 See the `repoze.lemonade package