summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTshepang Lekhonkhobe <tshepang@gmail.com>2013-04-06 07:56:08 +0200
committerTshepang Lekhonkhobe <tshepang@gmail.com>2013-04-06 07:56:08 +0200
commit660cb06c0e5ef0be664b6a33fad1db0256d5ec18 (patch)
treebebd185e2c20e70e3282b9335a6fc3ca04128766
parentd79e9c071505ef0532021308c96ab0ab144f3786 (diff)
downloadpyramid-660cb06c0e5ef0be664b6a33fad1db0256d5ec18.tar.gz
pyramid-660cb06c0e5ef0be664b6a33fad1db0256d5ec18.tar.bz2
pyramid-660cb06c0e5ef0be664b6a33fad1db0256d5ec18.zip
remove repetition; improve readability
-rw-r--r--docs/designdefense.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 488da6b19..113ac7ac7 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -38,8 +38,8 @@ 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 building them. No other system, save for Zope itself,
-had such features. And Zope itself was beginning to show signs of its age.
+way they were accustomed to. 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
to hire smart people to work on Zope applications, because there was no