summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2010-11-15 23:34:37 -0700
committerCasey Duncan <casey.duncan@gmail.com>2010-11-15 23:34:37 -0700
commit5182f12df56f6593a78d688e2472567b1a780416 (patch)
tree2983f0ade3666532f21374aa8f1b19f7259818cf /docs
parent9a88d969a92a4ad8a49d797b2564b2afb6689d28 (diff)
downloadpyramid-5182f12df56f6593a78d688e2472567b1a780416.tar.gz
pyramid-5182f12df56f6593a78d688e2472567b1a780416.tar.bz2
pyramid-5182f12df56f6593a78d688e2472567b1a780416.zip
Reword sentence describing what Pyramid config accomplishes
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/configuration.rst3
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/narr/configuration.rst b/docs/narr/configuration.rst
index 66a9df32e..ef2e9bef1 100644
--- a/docs/narr/configuration.rst
+++ b/docs/narr/configuration.rst
@@ -21,8 +21,7 @@ application startup time as "configuration". :app:`Pyramid` extends this
pattern to application development, using the term "configuration" to express
standardized ways that code gets plugged into a deployment of the framework
itself. When you plug code into the :app:`Pyramid` framework, you are
-"configuring" :app:`Pyramid` for the purpose of creating a particular
-application deployment.
+"configuring" :app:`Pyramid` to create a particular application.
.. index::
single: imperative configuration