summaryrefslogtreecommitdiff
path: root/docs/narr/advconfig.rst
diff options
context:
space:
mode:
authorKarl O. Pinc <kop@meme.com>2018-11-18 23:14:49 -0600
committerKarl O. Pinc <kop@meme.com>2018-11-18 23:48:49 -0600
commit3f01e1f615041aa0e6787e1c6ba2f9c54d139100 (patch)
tree738f59e902d2ca81fe1e67daf2f0425327e1e62b /docs/narr/advconfig.rst
parent33a1ec755a5e128224f31550ae04462d225ca9fc (diff)
downloadpyramid-3f01e1f615041aa0e6787e1c6ba2f9c54d139100.tar.gz
pyramid-3f01e1f615041aa0e6787e1c6ba2f9c54d139100.tar.bz2
pyramid-3f01e1f615041aa0e6787e1c6ba2f9c54d139100.zip
Fix so sentence has the right meaning
Diffstat (limited to 'docs/narr/advconfig.rst')
-rw-r--r--docs/narr/advconfig.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/narr/advconfig.rst b/docs/narr/advconfig.rst
index 322741648..f6a6c5b42 100644
--- a/docs/narr/advconfig.rst
+++ b/docs/narr/advconfig.rst
@@ -169,8 +169,8 @@ Using ``config.commit()``
You can manually commit a configuration by using the
:meth:`~pyramid.config.Configurator.commit` method between configuration calls.
For example, we prevent conflicts from occurring in the application we examined
-previously as the result of adding a ``commit``. Here's the application that
-generates conflicts:
+previously by adding a ``commit``.
+Here's the application that generates conflicts:
.. code-block:: python
:linenos: