summaryrefslogtreecommitdiff
path: root/docs/designdefense.rst
diff options
context:
space:
mode:
authorMichael Merickel <michael@merickel.org>2013-04-06 01:26:05 -0500
committerMichael Merickel <michael@merickel.org>2013-04-06 01:26:05 -0500
commit74a4e377d64e0e44ebea841feed90333c6c7088f (patch)
tree548fca9d74169e7f41dc0a8c163a4210931b0c06 /docs/designdefense.rst
parent2d2d2854b4831c7da7504fad1a1b96a5eff4272f (diff)
downloadpyramid-74a4e377d64e0e44ebea841feed90333c6c7088f.tar.gz
pyramid-74a4e377d64e0e44ebea841feed90333c6c7088f.tar.bz2
pyramid-74a4e377d64e0e44ebea841feed90333c6c7088f.zip
grammar
Diffstat (limited to 'docs/designdefense.rst')
-rw-r--r--docs/designdefense.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 732a0d357..fdc57e0c1 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -38,7 +38,7 @@ forking is also a Zope derivative.
Implementations of these features were *required* to allow the :app:`Pyramid`
authors to build the bread-and-butter CMS-type systems for customers in the
-way they were accustomed to. No other system, save for Zope itself,
+way in which they were accustomed. No other system, save for Zope itself,
had such features, and Zope itself was beginning to show signs of its age.
We were becoming hampered by consequences of its early design mistakes.
Zope's lack of documentation was also difficult to work around: it was hard