summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarlos de la Guardia <cguardia@yahoo.com>2013-09-14 23:55:12 -0500
committerCarlos de la Guardia <cguardia@yahoo.com>2013-09-14 23:55:12 -0500
commit9d0f887fa913482a2e07df442ed0b02ae7778a89 (patch)
tree807a3743cb4281ed7ccca70d53f431b5b8952e32
parent14e164132e64f4808ff2a41399e2f47bd22bea68 (diff)
downloadpyramid-9d0f887fa913482a2e07df442ed0b02ae7778a89.tar.gz
pyramid-9d0f887fa913482a2e07df442ed0b02ae7778a89.tar.bz2
pyramid-9d0f887fa913482a2e07df442ed0b02ae7778a89.zip
"useful...than" made no sense.
-rw-r--r--docs/designdefense.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index bbc9e2660..e30b847de 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -764,7 +764,7 @@ content management system (CMS) may have basic functionality that needs to be
extended for a particular deployment. That CMS system may be deployed for
many organizations at many places. Some number of deployments of this CMS
may be deployed centrally by a third party and managed as a group. It's
-useful to be able to extend such a system for each deployment via preordained
+easier to be able to extend such a system for each deployment via preordained
plugpoints than it is to continually keep each software branch of the system
in sync with some upstream source: the upstream developers may change code in
such a way that your changes to the same codebase conflict with theirs in