Browse files

Merge pull request #480 from ppaez/typos

  • Loading branch information...
2 parents e47a859 + c946fc7 commit 0d57eb63ff4a495c5b652a708e31888e5f0a49c6 @mcdonc mcdonc committed Mar 14, 2012
Showing with 2 additions and 2 deletions.
  1. +1 −1 docs/narr/advconfig.rst
  2. +1 −1 docs/narr/introduction.rst
@@ -227,7 +227,7 @@ to :meth:`~pyramid.config.Configurator.commit` between them:
In the above example we've issued a call to
:meth:`~pyramid.config.Configurator.commit` between the two ``add_view``
-calls. :meth:`~pyramid.config.Configurator.commit` will cause any pending
+calls. :meth:`~pyramid.config.Configurator.commit` will execute any pending
configuration statements.
Calling :meth:`~pyramid.config.Configurator.commit` is safe at any time. It
@@ -347,7 +347,7 @@ You can do this:
When this view callable is called by Pyramid, the ``{'a':1}`` dictionary will
be rendered to a response on your behalf. The string passed as ``renderer=``
above is an :term:`asset specification`. It is in the form
-``packagename:directoryname/filename.ext``. In this case, it names the
+``packagename:directoryname/filename.ext``. In this case, it refers to the
```` file in the ``templates`` directory within the ``myapp``
Python package. Asset specifications are omnipresent in Pyramid: see
:ref:`intro_asset_specs` for more information.

0 comments on commit 0d57eb6

Please sign in to comment.