Fixed issues, thanks to @weaverryan

Author: wouterj

book/security.rst

@@ -313,7 +313,7 @@ First, enable form login under your firewall:
             <config>
                 <firewall name="secured_area" pattern="^/">
                     <anonymous />
-                    <form-login login_path="/login" check_path="/login_check" />
+                    <form-login login_path="login" check_path="login_check" />
                 </firewall>
             </config>
         </srv:container>
@@ -327,8 +327,8 @@ First, enable form login under your firewall:
                     'pattern' => '^/',
                     'anonymous' => array(),
                     'form_login' => array(
-                        'login_path' => '/login',
-                        'check_path' => '/login_check',
+                        'login_path' => 'login',
+                        'check_path' => 'login_check',
                     ),
                 ),
             ),
@@ -558,7 +558,7 @@ see :doc:`/cookbook/security/form_login`.
 
     **1. Create the correct routes**
 
-    First, be sure that you've defined the ``/login`` and ``/login_check``
+    First, be sure that you've defined the ``login`` and ``login_check``
     routes correctly and that they correspond to the ``login_path`` and
     ``check_path`` config values. A misconfiguration here can mean that you're
     redirected to a 404 page instead of the login page, or that submitting

reference/configuration/security.rst

@@ -218,18 +218,18 @@ The Login Form and Process
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 *   ``login_path`` (type: ``string``, default: ``/login``)
-    This is the path that the user will be redirected to (unless ``use_forward``
-    is set to ``true``) when he/she tries to access a protected resource
-    but isn't fully authenticated.
+    This is the route or path that the user will be redirected to (unless
+    ``use_forward`` is set to ``true``) when he/she tries to access a
+    protected resource but isn't fully authenticated.
 
     This path **must** be accessible by a normal, un-authenticated user, else
     you may create a redirect loop. For details, see
     ":ref:`Avoid Common Pitfalls<book-security-common-pitfalls>`".
 
 *   ``check_path`` (type: ``string``, default: ``/login_check``)
-    This is the path that your login form must submit to. The firewall will
-    intercept any requests (``POST`` requests only, by default) to this URL
-    and process the submitted login credentials.
+    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 URL and process the submitted login credentials.
 
     Be sure that this URL is covered by your main firewall (i.e. don't create
     a separate firewall just for ``check_path`` URL).