[symfony#3180] Minor tweaks after proofreading new trailing slash entry

weaverryan · weaverryan · commit 2bfa09e451c2 · 2013-11-16T12:20:56.000-06:00
diff --git a/cookbook/routing/redirect_trailing_slash.rst b/cookbook/routing/redirect_trailing_slash.rst
@@ -4,13 +4,13 @@
 Redirect URLs with a Trailing Slash
 ===================================
 
-The goal of this cookbook is to demonstrate how to redirect URLs with
+The goal of this cookbook is to demonstrate how to redirect URLs with a
 trailing slash to the same URL without a trailing slash
 (for example ``/en/blog/`` to ``/en/blog``).
 
-You have to create a controller that will match any URL with a trailing
-slash, remove the trailing slash (keeping query parameters if any) and
-redirect to the new URL with a 301 response status code::
+Create a controller that will match any URL with a trailing slash, remove
+the trailing slash (keeping query parameters if any) and redirect to the
+new URL with a 301 response status code::
 
     // src/Acme/DemoBundle/Controller/RedirectingController.php
     namespace Acme\DemoBundle\Controller;
@@ -31,8 +31,9 @@ redirect to the new URL with a 301 response status code::
         }
     }
 
-And after that, register this controller to be executed whenever a URL
-with a trailing slash is requested:
+After that, create a route to this controller that's matched whenever a URL
+with a trailing slash is requested. Be sure to put this route last in your
+system, as explained below:
 
 .. configuration-block::
 
@@ -79,12 +80,13 @@ with a trailing slash is requested:
 
 .. note::
 
-    Redirecting a POST request does not work well in old browsers.
-    A 302 on a POST request will send a GET request after the
-    redirection for legacy reasons.
+    Redirecting a POST request does not work well in old browsers. A 302
+    on a POST request would send a GET request after the redirection for legacy
+    reasons. For that reason, the route here only matches GET requests.
 
 .. caution::
 
-    Make sure to include this route in your routing configuration at
-    the very end of your route listing. Otherwise, you risk to redirect
-    Symfony2 core routes that natively do have a trailing slash.
+    Make sure to include this route in your routing configuration at the
+    very end of your route listing. Otherwise, you risk redirecting real
+    routes (including Symfony2 core routes) that actually *do* have a trailing
+    slash in their path.
