From 1b8fb64d15d9e7328df153cd4529a4d3a1554ee5 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Tue, 19 Jan 2010 06:00:34 +0000 Subject: Renderings and typo fix. --- docs/narr/project.rst | 4 ---- docs/narr/zca.rst | 2 +- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/narr/project.rst b/docs/narr/project.rst index 56580451c..797930ba6 100644 --- a/docs/narr/project.rst +++ b/docs/narr/project.rst @@ -39,20 +39,16 @@ differ from each other on two axes: The included templates are these: ``bfg_starter`` - URL mapping via :term:`traversal` and no persistence mechanism. ``bfg_zodb`` - URL mapping via :term:`traversal` and persistence via :term:`ZODB` ``bfg_routesalchemy`` - URL mapping via :term:`URL dispatch` and persistence via :term:`SQLAlchemy` ``bfg_alchemy`` - URL mapping via :term:`traversal` and persistence va :term:`SQLAlchemy` diff --git a/docs/narr/zca.rst b/docs/narr/zca.rst index 2fbdcd873..05bb12ec0 100644 --- a/docs/narr/zca.rst +++ b/docs/narr/zca.rst @@ -91,7 +91,7 @@ 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. -There are three ways to fix this: by disusing the ZCA global registry +There are three ways to fix this: by disusing the ZCA global API entirely, by using :meth:`repoze.bfg.configuration.Configurator.hook_zca` or by passing the ZCA global registry to the :term:`Configurator` constructor at -- cgit v1.2.3