From 9a88d969a92a4ad8a49d797b2564b2afb6689d28 Mon Sep 17 00:00:00 2001 From: Casey Duncan Date: Mon, 15 Nov 2010 23:25:06 -0700 Subject: Reword sentence explaining application configuration for clarity --- docs/narr/configuration.rst | 6 +++--- 1 file 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, -- cgit v1.2.3