More fixes

Author: javiereguiluz

routing.rst

@@ -197,7 +197,8 @@ Use the ``methods`` option to restrict the verbs each route should respond to:
     HTML forms only support ``GET`` and ``POST`` methods. If you're calling a
     route with a different method from an HTML form, add a hidden field called
     ``_method`` with the method to use (e.g. ``<input type="hidden" name="_method" value="PUT" />``).
-    If you use :doc:`Symfony forms </forms>` this is done automatically for you.
+    If you create your forms with :doc:`Symfony Forms </forms>` this is done
+    automatically for you.
 
 Debugging Routes
 ~~~~~~~~~~~~~~~~
@@ -229,15 +230,15 @@ route details:
 
     $ php bin/console debug:router app_lucky_number
 
-      +-------------+---------------------------------------------------------+
-      | Property    | Value                                                   |
-      +-------------+---------------------------------------------------------+
-      | Route Name  | app_lucky_number                                        |
-      | Path        | /lucky/number/{max}                                     |
-      | ...         | ...                                                     |
-      | Options     | compiler_class: Symfony\Component\Routing\RouteCompiler |
-      |             | utf8: true                                              |
-      +-------------+---------------------------------------------------------+
+    +-------------+---------------------------------------------------------+
+    | Property    | Value                                                   |
+    +-------------+---------------------------------------------------------+
+    | Route Name  | app_lucky_number                                        |
+    | Path        | /lucky/number/{max}                                     |
+    | ...         | ...                                                     |
+    | Options     | compiler_class: Symfony\Component\Routing\RouteCompiler |
+    |             | utf8: true                                              |
+    +-------------+---------------------------------------------------------+
 
 The other command is called ``router:match`` and it shows which route will match
 the given URL. It's useful to find out why some URL is not executing the
@@ -594,8 +595,8 @@ Now, when the user visits ``/blog``, the ``blog_list`` route will match and
 
 .. caution::
 
-    You can have more than one optional placeholder (e.g. ``/blog/{slug}/{page}``),
-    but everything after an optional placeholder must be optional. For example,
+    You can have more than one optional parameter (e.g. ``/blog/{slug}/{page}``),
+    but everything after an optional parameter must be optional. For example,
     ``/{page}/blog`` is a valid path, but ``page`` will always be required
     (i.e. ``/blog`` will not match this route).
 
@@ -675,7 +676,7 @@ parameter:
 
 .. tip::
 
-    To give a ``null`` default value to any placeholder, add nothing after the
+    To give a ``null`` default value to any parameter, add nothing after the
     ``?`` character (e.g. ``/blog/{page?}``).
 
 .. _routing-expression_parameters:
@@ -763,6 +764,7 @@ where you can use any of these variables created by Symfony:
 ``context``
     An instance of :class:`Symfony\\Component\\Routing\\RequestContext`,
     which holds the most fundamental information about the route being matched.
+
 ``request``
     The :ref:`Symfony Request <component-http-foundation-request>` object that
     represents the current request.
@@ -1067,7 +1069,7 @@ A possible solution is to change the parameter requirements to be more permissiv
 
 .. note::
 
-    If the route defines several placeholders and you apply this permissive
+    If the route defines several parameter and you apply this permissive
     regular expression to all of them, the results won't be the expected. For
     example, if the route definition is ``/share/{path}/{token}`` and both
     ``path`` and ``token`` accept ``/``, then ``path`` will contain its contents
@@ -2034,7 +2036,7 @@ This information can be configured per command too::
     }
 
 Checking if a Route Exists
---------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 In highly dynamic applications, it may be necessary to check whether a route
 exists before using it to generate a URL. In those cases, don't use the