diff options
| author | Casey Duncan <casey.duncan@gmail.com> | 2010-11-15 23:25:06 -0700 |
|---|---|---|
| committer | Casey Duncan <casey.duncan@gmail.com> | 2010-11-15 23:25:06 -0700 |
| commit | 9a88d969a92a4ad8a49d797b2564b2afb6689d28 (patch) | |
| tree | dc17510d66c09511c6239239745778f67bf4374b | |
| parent | 7ca6338a8054169d0257e9c698ab54a0bc1094a7 (diff) | |
| download | pyramid-9a88d969a92a4ad8a49d797b2564b2afb6689d28.tar.gz pyramid-9a88d969a92a4ad8a49d797b2564b2afb6689d28.tar.bz2 pyramid-9a88d969a92a4ad8a49d797b2564b2afb6689d28.zip | |
Reword sentence explaining application configuration for clarity
| -rw-r--r-- | docs/narr/configuration.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/narr/configuration.rst b/docs/narr/configuration.rst index 6a91cbf75..66a9df32e 100644 --- a/docs/narr/configuration.rst +++ b/docs/narr/configuration.rst @@ -10,9 +10,9 @@ Each deployment of an application written using :app:`Pyramid` implies a specific *configuration* of the framework itself. For example, an application which serves up MP3s for user consumption might plug code into the framework that manages songs, while an application that manages corporate -data might plug in code that manages accounting information. :app:`Pyramid` -refers to the way in which code is plugged in to it for a specific -application as "configuration". +data might plug in code that manages accounting information. The way in which +code is plugged in to :app:`Pyramid`, for a specific application, is referred +to as "configuration". Most people understand "configuration" as coarse settings that inform the high-level operation of a specific application deployment. For instance, |