summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCasey Duncan <casey.duncan@gmail.com>2010-11-16 00:02:09 -0700
committerCasey Duncan <casey.duncan@gmail.com>2010-11-16 00:02:09 -0700
commit3791faf4c6a01e42bf36b5e413b53038a028e19b (patch)
tree013cb90e7d0ff208aaa7c6c857e4d8b4437c2ef5 /docs
parent8a3aa65783a49cee517e680b5d4a80216a1e3232 (diff)
downloadpyramid-3791faf4c6a01e42bf36b5e413b53038a028e19b.tar.gz
pyramid-3791faf4c6a01e42bf36b5e413b53038a028e19b.tar.bz2
pyramid-3791faf4c6a01e42bf36b5e413b53038a028e19b.zip
Split up long sentence on beginning configuration for clarity
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/firstapp.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/narr/firstapp.rst b/docs/narr/firstapp.rst
index bbd788250..f0978ed28 100644
--- a/docs/narr/firstapp.rst
+++ b/docs/narr/firstapp.rst
@@ -201,12 +201,12 @@ Beginning Configuration
The :meth:`pyramid.configuration.Configurator.begin` method tells
the system that application configuration has begun. In particular,
this causes the :term:`application registry` associated with this
-configurator to become the "current" application registry, meaning
-that code which attempts to use the application registry :term:`thread
-local` will obtain the registry associated with the configurator.
-This is an explicit step because it's sometimes convenient to use a
-configurator without causing the registry associated with the
-configurator to become "current".
+configurator to become the "current" application registry.
+Code that subsequently attempts to use the application registry
+:term:`thread local` will obtain the registry associated with this
+configurator. This is an explicit step because it's sometimes
+convenient to use a configurator without causing the registry
+associated with the configurator to become "current".
.. note::