summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2011-08-22 02:22:05 -0400
committerChris McDonough <chrism@plope.com>2011-08-22 02:22:05 -0400
commit9573ac26e7443ca9f7aa9ee17172d65c8e9774b7 (patch)
treeaf0e19a95a340538b9810833d91402ffe8a9a21f /docs
parent3d338ea5737b7c113b17120b40684e2694cf3fa9 (diff)
downloadpyramid-9573ac26e7443ca9f7aa9ee17172d65c8e9774b7.tar.gz
pyramid-9573ac26e7443ca9f7aa9ee17172d65c8e9774b7.tar.bz2
pyramid-9573ac26e7443ca9f7aa9ee17172d65c8e9774b7.zip
cleanups
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/project.rst7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/narr/project.rst b/docs/narr/project.rst
index 9ea5f20dd..3fe0ed6a8 100644
--- a/docs/narr/project.rst
+++ b/docs/narr/project.rst
@@ -5,7 +5,7 @@ Creating a :app:`Pyramid` Project
As we saw in :ref:`firstapp_chapter`, it's possible to create a
:app:`Pyramid` application completely manually. However, it's usually more
-convenient to use a *scaffold* to generate a basic :app:`Pyramid`
+convenient to use a :term:`scaffold` to generate a basic :app:`Pyramid`
:term:`project`.
A project is a directory that contains at least one Python :term:`package`.
@@ -20,7 +20,8 @@ distributed more easily than one which does not live within a package.
a project. Each scaffold makes different configuration assumptions about
what type of application you're trying to construct.
-These scaffolds are rendered using the :term:`PasteDeploy` ``paster`` script.
+These scaffolds are rendered using the :term:`PasteDeploy` ``paster create``
+command.
.. index::
single: scaffolds
@@ -441,7 +442,7 @@ The generated ``development.ini`` file looks like so:
:language: ini
:linenos:
-This file contains several "sections" including ``[app:main]``,
+This file contains several sections including ``[app:main]``,
``[server:main]`` and several other sections related to logging
configuration.