- Most references to ZCML in narrative chapters have been removed or

  redirected to ``pyramid_zcml`` locations.

1 files changed, 0 insertions, 8 deletions

diff --git a/docs/narr/security.rst b/docs/narr/security.rst
index 62a4727bc..ebaeb1526 100644
--- a/docs/narr/security.rst
+++ b/docs/narr/security.rst
@@ -106,9 +106,6 @@ See also the :mod:`pyramid.authorization` and
 :mod:`pyramid.authentication` modules for alternate implementations
 of authorization and authentication policies.  
 
-You can also enable a security policy declaratively via ZCML.  See
-:ref:`zcml_authorization_policy`.
-
 .. index::
    single: permissions
    single: protecting views
@@ -154,9 +151,6 @@ may be performed via the ``@view_config`` decorator:
        """ Add blog entry code goes here """
        pass
 
-Or the same thing can be done using the ``permission`` attribute of the ZCML
-:ref:`view_directive` directive.
-
 As a result of any of these various view configuration statements, if an
 authorization policy is in place when the view callable is found during
 normal application operations, the requesting user will need to possess the
@@ -189,8 +183,6 @@ application:
   :meth:`pyramid.config.Configurator.set_default_permission`
   method.
 
-- The :ref:`default_permission_directive` ZCML directive.
-
 When a default permission is registered:
 
 - if a view configuration names an explicit ``permission``, the default