Apply suggestions from Ryan review

Co-Authored-By: Ryan Weaver <[email protected]>

Author: javiereguiluz

routing.rst

@@ -4,22 +4,22 @@
 Routing
 =======
 
-When your application receives an HTTP request, it executes some
+When your application receives an HTTP request, it executes a
 :doc:`controller action </controller>` to generate the HTTP response. The
 routing configuration defines which action to run for each incoming URL. It also
-provides other useful features, such as generating SEO-friendly URLs
+provides other useful features, like generating SEO-friendly URLs
 (e.g. ``/read/intro-to-symfony`` instead of ``index.php?article_id=57``).
 
 Creating Routes
 ---------------
 
 Routes can be configured in YAML, XML, PHP or using annotations. All formats
-provide the same features and performance, so choose the one you prefer.
-:doc:`Symfony recommends to use annotations </best_practices/controllers>`
-because it's convenient to put the route definition and its controller in the
-same place instead of having to deal with multiple files.
+provide the same features and performance, so choose your favorite.
+:doc:`Symfony recommends annotations </best_practices/controllers>`
+because it's convenient to put the route and controller in the
+same place instead of dealing with multiple files.
 
-If you choose PHP annotations, run this command once in your application to add
+If you choose annotations, run this command once in your application to add
 support for them:
 
 .. code-block:: terminal
@@ -106,14 +106,14 @@ the ``list()`` method of the ``BlogController`` class.
     example, URLs like ``/blog?foo=bar`` and ``/blog?foo=bar&bar=foo`` will
     also match the ``blog_list`` route.
 
-The route name is not important for now, but it will be essential later when
+The route name (``blog_list``) is not important for now, but it will be essential later when
 :ref:`generating URLs <routing-generating-urls>`. You only have to keep in mind
-that names can be chosen freely but they must be unique in the application.
+that each route name must be unique in the application.
 
 Route HTTP Methods
 ~~~~~~~~~~~~~~~~~~
 
-By default, routes respond to any HTTP verb (``GET``, ``POST``, ``PUT``, etc.)
+By default, routes match any HTTP verb (``GET``, ``POST``, ``PUT``, etc.)
 Use the ``methods`` option to restrict the verbs each route should respond to:
 
 .. configuration-block::
@@ -194,7 +194,7 @@ Use the ``methods`` option to restrict the verbs each route should respond to:
 
 .. tip::
 
-    HTML forms only support ``GET`` and ``POST`` methods. If you are calling a
+    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.
@@ -332,13 +332,13 @@ with a locale. This can be done by defining a different prefix for each locale
 Route Groups
 ~~~~~~~~~~~~
 
-It's common for routes to share some features and options (e.g. all routes
+It's common for a group of routes to share some options (e.g. all routes
 related to the blog start with ``/blog``; all routes validate the locale with
 the same regular expression; etc.) That's why Symfony includes a feature to
-share the routes configuration.
+share route configuration.
 
-When defining routes as annotations, add a ``@Route`` annotation to the
-controller class to apply some options to all the routes defined in that class::
+When defining routes as annotations, add an ``@Route`` annotation to the
+controller class to apply options to all the routes defined in that class::
 
     use Symfony\Component\Routing\Annotation\Route;