@@ -116,15 +116,15 @@ Flow: Firewall, Authentication, Authorization
116
116
Hopefully you can now see a little bit about how the "flow" of the security
117
117
context works:
118
118
119
- #. the Firewall is registered as a listener on thereques ;
119
+ #. the Firewall is registered as a listener on the`` kernel.request `` event ;
120
120
#. at the beginning of the request, the Firewall checks the firewall map
121
121
to see if any firewall should be active for this URL;
122
- #. If a firewall is foundon the map for this URL, its listeners are notified
122
+ #. If a firewall is foundin the map for this URL, its listeners are notified
123
123
#. each listener checks to see if the current request contains any authentication
124
124
information - a listener may (a) authenticate a user, (b) throw an
125
125
``AuthenticationException ``, or (c) do nothing (because there is no
126
126
authentication information on the request);
127
- #. Once a user isauthentication , you'll use:doc: `/components/security/authorization `
127
+ #. Once a user isauthenticated , you'll use:doc: `/components/security/authorization `
128
128
to deny access to certain resources.
129
129
130
130
Read the next sections to find out more about:doc: `/components/security/authentication `