From a715baf9264b454ef590b96556c7686f79b0a1cf Mon Sep 17 00:00:00 2001 From: Andrew M Date: Thu, 9 Oct 2014 08:13:18 +0300 Subject: [PATCH] Improve readability --- cookbook/event_dispatcher/before_after_filters.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/cookbook/event_dispatcher/before_after_filters.rst b/cookbook/event_dispatcher/before_after_filters.rst index 569f0c7cce5..7fe93410713 100644 --- a/cookbook/event_dispatcher/before_after_filters.rst +++ b/cookbook/event_dispatcher/before_after_filters.rst @@ -125,7 +125,8 @@ event listeners, you can learn more about them at :doc:`/cookbook/service_contai $controller = $event->getController(); /* - * $controller passed can be either a class or a Closure. This is not usual in Symfony but it may happen. + * $controller passed can be either a class or a Closure. + * This is not usual in Symfony but it may happen. * If it is a class, it comes in array format */ if (!is_array($controller)) { @@ -189,7 +190,7 @@ want. After Filters with the ``kernel.response`` Event ------------------------------------------------ -In addition to having a "hook" that's executed before your controller, you +In addition to having a "hook" that's executed *before* your controller, you can also add a hook that's executed *after* your controller. For this example, imagine that you want to add a sha1 hash (with a salt using that token) to all responses that have passed this token authentication.