Features

--------

- The ``Configurator.add_view`` method now accepts an argument named
  ``context``.  This is an alias for the older argument named
  ``for_``; it is preferred over ``for_``, but ``for_`` will continue
  to be supported "forever".

- The ``view`` ZCML directive now accepts an attribute named
  ``context``.  This is an alias for the older attribute named
  ``for``; it is preferred over ``for``, but ``for`` will continue to
  be supported "forever".

- The ``Configurator.add_route`` method now accepts an argument named
  ``view_context``.  This is an alias for the older argument named
  ``view_for``; it is preferred over ``view_for``, but ``view_for``
  will continue to be supported "forever".

- The ``route`` ZCML directive now accepts an attribute named
  ``view_context``.  This is an alias for the older attribute named
  ``view_for``; it is preferred over ``view_for``, but ``view_for``
  will continue to be supported "forever".

Documentation and Paster Templates
----------------------------------

- All uses of the ``Configurator.add_view`` method that used its
  ``for_`` argument now use the ``context``argument instead.

- All uses of the ``Configurator.add_route`` method that used its
  ``view_for`` argument now use the ``view_context``argument instead.

- All uses of the ``view`` ZCML directive that used its ``for``
  attribute now use the ``context`` attribute instead.

- All uses of the ``route`` ZCML directive that used its ``view_for``
  attribute now use the ``view_context`` attribute instead.

1 files changed, 5 insertions, 5 deletions

diff --git a/docs/narr/hooks.rst b/docs/narr/hooks.rst
index 990290744..47495b68c 100644
--- a/docs/narr/hooks.rst
+++ b/docs/narr/hooks.rst
@@ -225,11 +225,11 @@ a class that implements the following interface:
 
 More than one traversal algorithm can be active at the same time.  For
 instance, if your :term:`root factory` returns more than one type of
-object conditionally, you could claim that an alternate traverser is
-``for`` only one particular class or interface.  When the root factory
-returned an object that implemented that class or interface, a custom
-traverser would be used.  Otherwise, the default traverser would be
-used.  For example:
+object conditionally, you could claim that an alternate traverser
+adapter is ``for`` only one particular class or interface.  When the
+root factory returned an object that implemented that class or
+interface, a custom traverser would be used.  Otherwise, the default
+traverser would be used.  For example:
 
 .. code-block:: xml
    :linenos: