Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typos #480

Merged
merged 1 commit into from Mar 14, 2012
Merged

Typos #480

Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/narr/advconfig.rst
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/narr/introduction.rst
Expand Up @@ -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
``mytemplate.pt`` file in the ``templates`` directory within the ``myapp``
Python package. Asset specifications are omnipresent in Pyramid: see
:ref:`intro_asset_specs` for more information.
Expand Down