Skip to content

Commit 3c69c58

Browse files
committed
Merge pull request #1649 from richardmiller/tidy_filters_article
Tidied up a bit of grammar and added a link to the EventDispatcher docs ...
2 parents 495935b + f875c2a commit 3c69c58

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

cookbook/event_dispatcher/before_after_filters.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ or hooks.
1010

1111
In Symfony1, this was achieved with the preExecute and postExecute methods,
1212
most major frameworks have similar methods but there is no such thing in Symfony2.
13-
The good news is that there is a much better way to interfere the
14-
Request -> Response process using the EventDispatcher component.
13+
The good news is that there is a much better way to interfere with the
14+
Request -> Response process using the :doc:`EventDispatcher component</components/event_dispatcher/introduction>`.
1515

1616
Token validation Example
1717
------------------------
@@ -21,13 +21,13 @@ but some others are restricted to one or some clients. For these private feature
2121
you might provide a token to your clients to identify themselves.
2222

2323
So, before executing your controller action, you need to check if the action
24-
is restricted or not. And if it is restricted, you need to validate the provided
24+
is restricted or not. If it is restricted, you need to validate the provided
2525
token.
2626

2727
.. note::
2828

29-
Please note that for simplicity in the recipe, tokens will be defined
30-
in config and neither database setup nor authentication provider via
29+
Please note that for simplicity in this recipe, tokens will be defined
30+
in config and neither database setup nor authentication via
3131
the Security component will be used.
3232

3333
Creating a before filter with a controller.request event

0 commit comments

Comments
 (0)