symfony
diff --git a/‎cookbook/event_dispatcher/before_after_filters.rst
Copy file name to clipboardExpand all lines: cookbook/event_dispatcher/before_after_filters.rst
+5-5Lines changed: 5 additions & 5 deletions b/‎cookbook/event_dispatcher/before_after_filters.rst
Copy file name to clipboardExpand all lines: cookbook/event_dispatcher/before_after_filters.rst
+5-5Lines changed: 5 additions & 5 deletions
@@ -10,8 +10,8 @@ or hooks.
 
 In Symfony1, this was achieved with the preExecute and postExecute methods,
 most major frameworks have similar methods but there is no such thing in Symfony2.
-The good news is that there is a much better way to interfere the
-Request -> Response process using the EventDispatcher component.
+The good news is that there is a much better way to interfere with the
+Request -> Response process using the :doc:`EventDispatcher component</components/event_dispatcher/introduction>`.
 
 Token validation Example
 ------------------------
@@ -21,13 +21,13 @@ but some others are restricted to one or some clients. For these private feature
 you might provide a token to your clients to identify themselves.
 
 So, before executing your controller action, you need to check if the action
-is restricted or not. And if it is restricted, you need to validate the provided
+is restricted or not. If it is restricted, you need to validate the provided
 token.
 
 .. note::
 
-    Please note that for simplicity in the recipe, tokens will be defined
-    in config and neither database setup nor authentication provider via
+    Please note that for simplicity in this recipe, tokens will be defined
+    in config and neither database setup nor authentication via
     the Security component will be used.
 
 Creating a before filter with a controller.request event