@@ -45,7 +45,7 @@ authentication (i.e. the old-school username/password box):
4545security :
4646firewalls :
4747secured_area :
48- pattern :^/
48+ pattern :^/
4949anonymous :~
5050http_basic :
5151realm :" Secured Demo Area"
@@ -148,8 +148,8 @@ that looks like the following:
148148* All URLs *not * matching ``/admin/* `` are accessible by all users (and the
149149 user is never prompted to log in).
150150
151- Let's look briefly at how security works and how each part of the configuration
152- comes into play.
151+ Read this short summary about how security works and how each part of the
152+ configuration comes into play.
153153
154154How Security Works: Authentication and Authorization
155155----------------------------------------------------
@@ -300,11 +300,11 @@ First, enable form login under your firewall:
300300security :
301301firewalls :
302302secured_area :
303- pattern :^/
303+ pattern :^/
304304anonymous :~
305305form_login :
306- login_path :login
307- check_path :login_check
306+ login_path :login
307+ check_path :login_check
308308
309309 ..code-block ::xml
310310
@@ -373,10 +373,10 @@ submission (i.e. ``/login_check``):
373373
374374# app/config/routing.yml
375375login :
376- path :/login
377- defaults :{ _controller: AcmeSecurityBundle:Security:login }
376+ path :/login
377+ defaults :{ _controller: AcmeSecurityBundle:Security:login }
378378login_check :
379- path :/login_check
379+ path :/login_check
380380
381381 ..code-block ::xml
382382
@@ -537,7 +537,7 @@ And that's it! When you submit the form, the security system will automatically
537537check the user's credentials and either authenticate the user or send the
538538user back to the login form where the error can be displayed.
539539
540- Let's review the whole process:
540+ To review the whole process:
541541
542542#. The user tries to access a resource that is protected;
543543#. The firewall initiates the authentication process by redirecting the
@@ -633,8 +633,8 @@ see :doc:`/cookbook/security/form_login`.
633633
634634firewalls :
635635login_firewall :
636- pattern :^/login$
637- anonymous :~
636+ pattern :^/login$
637+ anonymous :~
638638secured_area :
639639pattern :^/
640640form_login :~
@@ -1211,13 +1211,14 @@ aren't stored anywhere in a database. The actual user object is provided
12111211by Symfony (:class: `Symfony\\ Component\\ Security\\ Core\\ User\\ User `).
12121212
12131213..tip ::
1214+
12141215 Any user provider can load users directly from configuration by specifying
12151216 the ``users `` configuration parameter and listing the users beneath it.
12161217
12171218..caution ::
12181219
12191220 If your username is completely numeric (e.g. ``77 ``) or contains a dash
1220- (e.g. ``user-name ``), you should usethat alternative syntax when specifying
1221+ (e.g. ``user-name ``), you should usean alternative syntax when specifying
12211222 users in YAML:
12221223
12231224 ..code-block ::yaml