Fixed all broken references

Author: javiereguiluz

components/routing.rst

@@ -22,4 +22,4 @@ Usage
 -----
 
 The documentation about using this component has been moved to the
-main :doc:`Symfony routing` article.
+main :doc:`Symfony routing </routing>` article.

reference/forms/types/options/method.rst.inc

@@ -19,7 +19,7 @@ is used to decide whether to process the form submission in the
     When the method is PUT, PATCH, or DELETE, Symfony will automatically
     render a ``_method`` hidden field in your form. This is used to "fake"
     these HTTP methods, as they're not supported on standard browsers. This can
-    be useful when using :ref:`method routing requirements <routing-method-requirement>`.
+    be useful when :ref:`matching routes by HTTP method <routing-matching-http-methods>`.
 
 .. note::
 

routing.rst

@@ -10,6 +10,8 @@ configuration defines which action to run for each incoming URL. It also
 provides other useful features, like generating SEO-friendly URLs (e.g.
 ``/read/intro-to-symfony`` instead of ``index.php?article_id=57``).
 
+.. _routing-creating-routes:
+
 Creating Routes
 ---------------
 
@@ -110,6 +112,8 @@ The route name (``blog_list``) is not important for now, but it will be essentia
 :ref:`generating URLs <routing-generating-urls>`. You only have to keep in mind
 that each route name must be unique in the application.
 
+.. _routing-matching-http-methods:
+
 Matching HTTP Methods
 ~~~~~~~~~~~~~~~~~~~~~
 
@@ -833,7 +837,7 @@ special parameters created by Symfony:
     This parameter is used to determine which controller and action is executed
     when the route is matched.
 
-.. _routing-format-param:
+.. _routing-format-parameter:
 
 ``_format``
     The matched value is used to set the "request format" of the ``Request`` object.
@@ -844,6 +848,8 @@ special parameters created by Symfony:
     Used to set the fragment identifier, which is the optional last part of a URL that
     starts with a ``#`` character and is used to identify a portion of a document.
 
+.. _routing-locale-parameter:
+
 ``_locale``
     Used to set the :ref:`locale <translation-locale-url>` on the request.
 

templating/formats.rst

@@ -48,7 +48,7 @@ but can return any other format based on the format requested by the user.
 The request format is most often managed by the routing, where a route can
 be configured so that ``/about-us`` sets the request format to ``html`` while
 ``/about-us.xml`` sets the format to ``xml``. This can be achieved by using the
-special ``_format`` placeholder in your route definition::
+:ref:`special _format parameter <routing-format-parameter>` in your route definition::
 
     /**
      * @Route("/{slug}.{_format}", defaults={"_format"="html"}, requirements={"_format"="html|xml"}))
@@ -67,10 +67,6 @@ format:
         View as XML
     </a>
 
-.. seealso::
-
-    For more information, see this :ref:`Advanced Routing Example <advanced-routing-example>`.
-
 .. tip::
 
     When building APIs, using file name extensions often isn't the best

translation/locale.rst

@@ -59,8 +59,8 @@ this violates a fundamental rule of the Web: that a particular URL returns
 the same resource regardless of the user. To further muddy the problem, which
 version of the content would be indexed by search engines?
 
-A better policy is to include the locale in the URL. This is fully-supported
-by the routing system using the special ``_locale`` parameter:
+A better policy is to include the locale in the URL using the
+:ref:`special _locale parameter <routing-locale-parameter>`:
 
 .. configuration-block::
 
@@ -114,8 +114,8 @@ application.
 
 .. tip::
 
-    Read :doc:`/routing/service_container_parameters` to learn how to avoid
-    hardcoding the ``_locale`` requirement in all your routes.
+    Define the locale requirement as a :ref:`container parameter <configuration-parameters>`
+    to avoid hardcoding its value in all your routes.
 
 .. index::
     single: Translations; Fallback and default locale