summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCarlos de la Guardia <cguardia@yahoo.com>2010-03-29 22:39:29 +0000
committerCarlos de la Guardia <cguardia@yahoo.com>2010-03-29 22:39:29 +0000
commit7ee36818f975dcbfbef619b7ff310e959c78d3b5 (patch)
treead05bc8c3f45cc76de75d82e8180286d1b166329 /docs
parent219ba8e0b31e5e7eb10c2f6e14964d804e100c2d (diff)
downloadpyramid-7ee36818f975dcbfbef619b7ff310e959c78d3b5.tar.gz
pyramid-7ee36818f975dcbfbef619b7ff310e959c78d3b5.tar.bz2
pyramid-7ee36818f975dcbfbef619b7ff310e959c78d3b5.zip
finished bug fixing for narrative docs
Diffstat (limited to 'docs')
-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 418312caa..11b7eabad 100644
--- a/docs/narr/zca.rst
+++ b/docs/narr/zca.rst
@@ -43,7 +43,7 @@ of the ZCA from application developers. You needn't understand the
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`
+However, developers who are already used to writing :term:`Zope`
applications often still wish to use the ZCA while building a
:mod:`repoze.bfg` application; :mod:`repoze.bfg` makes this possible.
@@ -74,8 +74,8 @@ Most production Zope applications are relatively large, making it
impractical due to memory constraints to run more than one Zope
application per Python process. However, a :mod:`repoze.bfg`
application may be very small and consume very little memory, so it's
-a reasonable goal to be able to want to run more than one BFG
-application per process.
+a reasonable goal to be able to run more than one BFG application per
+process.
In order to make it possible to run more than one :mod:`repoze.bfg`
application in a single process, :mod:`repoze.bfg` defaults to using a
@@ -86,7 +86,7 @@ trying to use patterns which you might use to build a typical
:term:`Zope` application to build a :mod:`repoze.bfg` application.
Without special help, ZCA "global" APIs such as
``zope.component.getUtility`` and ``zope.component.getSiteManager``
-will use the ZCA "global" registry. Therefore, these APIs application
+will use the ZCA "global" registry. Therefore, these APIs
will appear to fail when used in a :mod:`repoze.bfg` application,
because they'll be consulting the ZCA global registry rather than the
component registry associated with your :mod:`repoze.bfg` application.