From 2e95acb8b64694f0e99f553413cb2ddc123efd6f Mon Sep 17 00:00:00 2001 From: Tshepang Lekhonkhobe Date: Mon, 14 Jan 2013 23:46:21 +0200 Subject: improve flow --- pyramid/config/__init__.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pyramid/config/__init__.py b/pyramid/config/__init__.py index 40c487704..b8fa1d16d 100644 --- a/pyramid/config/__init__.py +++ b/pyramid/config/__init__.py @@ -640,8 +640,8 @@ class Configurator( A configuration callable should be a callable that accepts a single argument named ``config``, which will be an instance of a - :term:`Configurator` (be warned that it will not be the same - configurator instance on which you call this method, however). The + :term:`Configurator`. However, be warned that it will not be the same + configurator instance on which you call this method. The code which runs as the result of calling the callable should invoke methods on the configurator passed to it which add configuration state. The return value of a callable will be ignored. @@ -701,7 +701,7 @@ class Configurator( to :meth:`pyramid.config.Configurator.add_route` within the included callable will have their pattern prefixed with the value of ``route_prefix``. This can be used to help mount a set of routes at a - different location than the included callable's author intended while + different location than the included callable's author intended, while still maintaining the same route names. For example: .. code-block:: python -- cgit v1.2.3