fix docs: pyramid.configuration -> pyramid.config

1 files changed, 18 insertions, 18 deletions

diff --git a/docs/narr/static.rst b/docs/narr/static.rst
index beb12c586..9547e73fc 100644
--- a/docs/narr/static.rst
+++ b/docs/narr/static.rst
@@ -13,17 +13,17 @@ how to configure :app:`Pyramid` to do so.
 Serving Static Resources
 ------------------------
 
-Use the :meth:`pyramid.configuration.Configurator.add_static_view` to
+Use the :meth:`pyramid.config.Configurator.add_static_view` to
 instruct :app:`Pyramid` to serve static resources such as JavaScript and CSS
 files. This mechanism makes static files available at a name relative to the
 application root URL, e.g. ``/static``.
 
 Note that the ``path`` provided to
-:meth:`pyramid.configuration.Configurator.add_static_view` may be a fully
+:meth:`pyramid.config.Configurator.add_static_view` may be a fully
 qualified :term:`resource specification` or an *absolute path*.  
 
 Here's an example of a use of
-:meth:`pyramid.configuration.Configurator.add_static_view` that will serve
+:meth:`pyramid.config.Configurator.add_static_view` that will serve
 files up under the ``/static`` URL from the ``/var/www/static`` directory of
 the computer which runs the :app:`Pyramid` application using an absolute
 path.
@@ -31,11 +31,11 @@ path.
 .. code-block:: python
    :linenos:
 
-   # config is an instance of pyramid.configuration.Configurator
+   # config is an instance of pyramid.config.Configurator
    config.add_static_view(name='static', path='/var/www/static')
 
 Here's an example of
-:meth:`pyramid.configuration.Configurator.add_static_view` that will serve
+:meth:`pyramid.config.Configurator.add_static_view` that will serve
 files up under the ``/static`` URL from the ``a/b/c/static`` directory of the
 Python package named ``some_package`` using a fully qualified :term:`resource
 specification`.
@@ -43,7 +43,7 @@ specification`.
 .. code-block:: python
    :linenos:
 
-   # config is an instance of pyramid.configuration.Configurator
+   # config is an instance of pyramid.config.Configurator
    config.add_static_view(name='static', path='some_package:a/b/c/static')
 
 Whether you use for ``path`` a fully qualified resource specification, or an
@@ -59,7 +59,7 @@ be resolved by the static view as you would expect.
 
 While the ``path`` argument can be a number of different things, the ``name``
 argument of the call to
-:meth:`pyramid.configuration.Configurator.add_static_view` can also be one of
+:meth:`pyramid.config.Configurator.add_static_view` can also be one of
 a number of things: a *view name* or a *URL*.  The above examples have shown
 usage of the ``name`` argument as a view name.  When ``name`` is a *URL* (or
 any string with a slash (``/``) in it), static resources can be served from
@@ -69,13 +69,13 @@ when generating a URL using :func:`pyramid.url.static_url`.
 .. note::
 
    Using :func:`pyramid.url.static_url` in conjunction with a
-   :meth:`pyramid.configuration.Configurator.add_static_view` makes it
+   :meth:`pyramid.config.Configurator.add_static_view` makes it
    possible to put static media on a separate webserver during production (if
    the ``name`` argument to
-   :meth:`pyramid.configuration.Configurator.add_static_view` is a URL),
+   :meth:`pyramid.config.Configurator.add_static_view` is a URL),
    while keeping static media package-internal and served by the development
    webserver during development (if the ``name`` argument to
-   :meth:`pyramid.configuration.Configurator.add_static_view` is a view
+   :meth:`pyramid.config.Configurator.add_static_view` is a view
    name).  To create such a circumstance, we suggest using the
    :attr:`pyramid.registry.Registry.settings` API in conjunction with a
    setting in the application ``.ini`` file named ``media_location``.  Then
@@ -85,28 +85,28 @@ when generating a URL using :func:`pyramid.url.static_url`.
    development).  This is just a suggestion for a pattern; any setting name
    other than ``media_location`` could be used.
 
-For example, :meth:`pyramid.configuration.Configurator.add_static_view` may
+For example, :meth:`pyramid.config.Configurator.add_static_view` may
 be fed a ``name`` argument which is ``http://example.com/images``:
 
 .. code-block:: python
    :linenos:
 
-   # config is an instance of pyramid.configuration.Configurator
+   # config is an instance of pyramid.config.Configurator
    config.add_static_view(name='http://example.com/images', 
                           path='mypackage:images')
 
-Because :meth:`pyramid.configuration.Configurator.add_static_view` is
+Because :meth:`pyramid.config.Configurator.add_static_view` is
 provided with a ``name`` argument that is the URL prefix
 ``http://example.com/images``, subsequent calls to
 :func:`pyramid.url.static_url` with paths that start with the ``path``
-argument passed to :meth:`pyramid.configuration.Configurator.add_static_view`
+argument passed to :meth:`pyramid.config.Configurator.add_static_view`
 will generate a URL something like ``http://example.com/logo.png``.  The
 external webserver listening on ``example.com`` must be itself configured to
 respond properly to such a request.  The :func:`pyramid.url.static_url` API
 is discussed in more detail later in this chapter.
 
 The :ref:`static_directive` ZCML directive offers an declarative equivalent
-to :meth:`pyramid.configuration.Configurator.add_static_view`.  Use of the
+to :meth:`pyramid.config.Configurator.add_static_view`.  Use of the
 :ref:`static_directive` ZCML directive is completely equivalent to using
 imperative configuration for the same purpose.
 
@@ -119,7 +119,7 @@ imperative configuration for the same purpose.
 Generating Static Resource URLs
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-When a :meth:`pyramid.configuration.Configurator.add_static_view` method is
+When a :meth:`pyramid.config.Configurator.add_static_view` method is
 used to register a static resource directory, a special helper API named
 :func:`pyramid.url.static_url` can be used to generate the appropriate URL for a
 package resource that lives in one of the directories named by the static
@@ -169,7 +169,7 @@ properly after the rename.
 
 URLs may also be generated by :func:`pyramid.url.static_url` to static
 resources that live *outside* the :app:`Pyramid` application.  This will
-happen when the :meth:`pyramid.configuration.Configurator.add_static_view`
+happen when the :meth:`pyramid.config.Configurator.add_static_view`
 API associated with the path fed to :func:`pyramid.url.static_url` is a *URL*
 instead of a view name.  For example, the ``name`` argument may be
 ``http://example.com`` while the the ``path`` given may be
@@ -228,7 +228,7 @@ your application root as below.
    which the static view is defined.
  
 Subsequently, you may wire this view up to be accessible as ``/static`` using
-the :mod:`pyramid.configuration.Configurator.add_view` method in your
+the :mod:`pyramid.config.Configurator.add_view` method in your
 application's startup code against either the class or interface that
 represents your root object.