[#6143] some tweaks

Author: xabbuh

cookbook/security/form_login_setup.rst

@@ -42,7 +42,7 @@ First, enable form login under your firewall:
             <config>
                 <firewall name="main">
                     <anonymous />
-                    <form-login login-path="/login" check-path="/login" />
+                    <form-login login-path="login" check-path="login" />
                 </firewall>
             </config>
         </srv:container>
@@ -82,8 +82,8 @@ bundle::
     {
     }
 
-Next, create a route for the path you configured earlier
-under your ``form_login`` configuration (``/login``):
+Next, configure the route that you earlier used under your ``form_login``
+configuration (``login``):
 
 .. configuration-block::
 
@@ -247,7 +247,7 @@ Finally, create the template:
 
 The form can look like anything, but has a few requirements:
 
-* The form must POST to ``/login``, since that's what you configured
+* The form must POST to the ``login`` route, since that's what you configured
   under the ``form_login`` key in ``security.yml``.
 
 * The username must have the name ``_username`` and the password must have

reference/configuration/security.rst

@@ -129,10 +129,10 @@ Each part will be explained in the next section.
                         provider: some_key_from_above
                     form_login:
                         # submit the login form here
-                        check_path: login
+                        check_path: /login_check
 
                         # the user is redirected here when they need to log in
-                        login_path: login
+                        login_path: /login
 
                         # if true, forward the user to the login form instead of redirecting
                         use_forward: false
@@ -252,7 +252,7 @@ The Login Form and Process
 login_path
 ..........
 
-**type**: ``string`` **default**: ``login``
+**type**: ``string`` **default**: ``/login``
 
 This is the route or path that the user will be redirected to (unless ``use_forward``
 is set to ``true``) when they try to access a protected resource but isn't
@@ -265,7 +265,7 @@ you may create a redirect loop. For details, see
 check_path
 ..........
 
-**type**: ``string`` **default**: ``login``
+**type**: ``string`` **default**: ``/login_check``
 
 This is the route or path that your login form must submit to. The firewall
 will intercept any requests (``POST`` requests only, by default) to this