summaryrefslogtreecommitdiff
path: root/docs/narr/zca.rst
diff options
context:
space:
mode:
authorCarlos de la Guardia <cguardia@yahoo.com>2011-06-07 01:54:50 -0500
committerCarlos de la Guardia <cguardia@yahoo.com>2011-06-07 01:54:50 -0500
commitfd5203000d4d051b51f804af023aefe59b832029 (patch)
treef92f1f163aed0d2c282fb674069f987fe4dfba47 /docs/narr/zca.rst
parenta5713863a80a493a1485057609578b907d04c770 (diff)
parentdf75cee020e49cc4668448b83e0617b14904bfa2 (diff)
downloadpyramid-fd5203000d4d051b51f804af023aefe59b832029.tar.gz
pyramid-fd5203000d4d051b51f804af023aefe59b832029.tar.bz2
pyramid-fd5203000d4d051b51f804af023aefe59b832029.zip
Merge remote branch 'cito/master'
Diffstat (limited to 'docs/narr/zca.rst')
-rw-r--r--docs/narr/zca.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/narr/zca.rst b/docs/narr/zca.rst
index 19c52d0c9..a99fd8b24 100644
--- a/docs/narr/zca.rst
+++ b/docs/narr/zca.rst
@@ -38,10 +38,10 @@ code is high.
While the ZCA is an excellent tool with which to build a *framework*
such as :app:`Pyramid`, it is not always the best tool with which
to build an *application* due to the opacity of the ``zope.component``
-APIs. Accordingly, :app:`Pyramid` tends to hide the the presence
-of the ZCA from application developers. You needn't understand the
-ZCA to create a :app:`Pyramid` application; its use is effectively
-only a framework implementation detail.
+APIs. Accordingly, :app:`Pyramid` tends to hide the presence of the
+ZCA from application developers. You needn't understand the ZCA to
+create a :app:`Pyramid` application; its use is effectively only a
+framework implementation detail.
However, developers who are already used to writing :term:`Zope`
applications often still wish to use the ZCA while building a