summaryrefslogtreecommitdiff
path: root/docs/narr/resources.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/narr/resources.rst')
-rw-r--r--docs/narr/resources.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/narr/resources.rst b/docs/narr/resources.rst
index 3ff8af90b..575afd1fe 100644
--- a/docs/narr/resources.rst
+++ b/docs/narr/resources.rst
@@ -157,7 +157,7 @@ The ``override_resource`` API
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
An individual call to
-:meth:`pyramid.configuration.Configurator.override_resource` can
+:meth:`pyramid.config.Configurator.override_resource` can
override a single resource. For example:
.. ignore-next-block
@@ -213,7 +213,7 @@ will need to register two overrides.
The package name in a specification may start with a dot, meaning that
the package is relative to the package in which the configuration
construction file resides (or the ``package`` argument to the
-:class:`pyramid.configuration.Configurator` class construction).
+:class:`pyramid.config.Configurator` class construction).
For example:
.. ignore-next-block
@@ -245,7 +245,7 @@ The ``resource`` ZCML Directive
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Instead of using
-:meth:`pyramid.configuration.Configurator.override_resource` during
+:meth:`pyramid.config.Configurator.override_resource` during
:term:`imperative configuration`, an equivalent can be used to perform
all the tasks described above within :term:`ZCML`. The ZCML
``resource`` tag is a frontend to using ``override_resource``.