summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2010-01-19 07:35:22 +0000
committerChris McDonough <chrism@agendaless.com>2010-01-19 07:35:22 +0000
commit206161c32808838884f0b7154090817d47751c88 (patch)
treea765c1fb54f7c929163e742d8137a9c3ad0bd71c /docs
parent1b8fb64d15d9e7328df153cd4529a4d3a1554ee5 (diff)
downloadpyramid-206161c32808838884f0b7154090817d47751c88.tar.gz
pyramid-206161c32808838884f0b7154090817d47751c88.tar.bz2
pyramid-206161c32808838884f0b7154090817d47751c88.zip
Wording.
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/zca.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/narr/zca.rst b/docs/narr/zca.rst
index 05bb12ec0..0a2fc5808 100644
--- a/docs/narr/zca.rst
+++ b/docs/narr/zca.rst
@@ -40,8 +40,8 @@ such as :mod:`repoze.bfg`, it is not always the best tool with which
to build an *application* due to the opacity of the ``zope.component``
APIs. Accordingly, :mod:`repoze.bfg` tends to hide the the presence
of the ZCA from application developers. You needn't understand the
-ZCA to create a :mod:`repoze.bfg` application; the use of the ZCA is
-effectively only a framework implementation detail.
+ZCA to create a :mod:`repoze.bfg` application; its use is effectively
+only a framework implementation detail.
However, developers whom are already used to writing :term:`Zope`
applications often still wish to use the ZCA while building a