summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2010-12-27 01:37:27 -0500
committerChris McDonough <chrism@plope.com>2010-12-27 01:37:27 -0500
commite8db031e8cd22affb65254539ae210f64d37f36e (patch)
treeaadcfe22cd853f5f51dcdf04f4331459d86fc5c2 /docs
parentd30a83540d98bb803caca74b94ae75f88dd3154b (diff)
downloadpyramid-e8db031e8cd22affb65254539ae210f64d37f36e.tar.gz
pyramid-e8db031e8cd22affb65254539ae210f64d37f36e.tar.bz2
pyramid-e8db031e8cd22affb65254539ae210f64d37f36e.zip
wording
Diffstat (limited to 'docs')
-rw-r--r--docs/designdefense.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index db399fffa..53b95b9d0 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -1002,7 +1002,7 @@ understand the ZCA or he will need to develop his own similar extensibility
system.
Ultimately, any argument about whether the extensibility features lent to
-applications by :app:`Pyramid` are "good" or "bad" is somewhat pointless. You
+applications by :app:`Pyramid` are "good" or "bad" is mostly pointless. You
needn't take advantage of the extensibility features provided by a particular
:app:`Pyramid` application in order to affect a modification for a particular
set of its deployments. You can ignore the application's extensibility