- The BFG router now emits an additional event unconditionally at the

  end of request processing:
  ``repoze.bfg.interfaces.IFinishedRequest``.  This event is meant to
  be used when it is necessary to perform unconditional cleanup after
  request processing.  See the ``repoze.bfg.events.FinishedRequest``
  class documentation for more information.

- The ``repoze.bfg.interfaces.IWSGIApplicationCreatedEvent`` event
  interface was renamed to
  ``repoze.bfg.interfaces.IApplicationCreated``.  Likewise, the
  ``repoze.bfg.events.WSGIApplicationCreatedEvent`` class was renamed
  to ``repoze.bfg.events.ApplicationCreated``.  The older aliases will
  continue to work indefinitely.

- The ``repoze.bfg.interfaces.IAfterTraversal`` event interface was
  renamed to ``repoze.bfg.interfaces.IContextFound``.  Likewise, the
  ``repoze.bfg.events.AfterTraveral`` class was renamed to
  ``repoze.bfg.events.ContextFound``.  The older aliases will continue
  to work indefinitely.

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/narr/router.rst b/docs/narr/router.rst
index 025d70157..af8f057b0 100644
--- a/docs/narr/router.rst
+++ b/docs/narr/router.rst
@@ -67,7 +67,7 @@ processing?
    they can be accessed via e.g. ``request.context`` within
    :term:`view` code.
 
-#. A :class:`repoze.bfg.interfaces.IAfterTraversal` :term:`event` is
+#. A :class:`repoze.bfg.interfaces.IContextFound` :term:`event` is
    sent to any subscribers.
 
 #. :mod:`repoze.bfg` looks up a :term:`view` callable using the