-

Author: fabpot

_build/redirection_map

@@ -538,7 +538,7 @@
 /components/security /security
 /components/var_dumper/advanced /components/var_dumper#advanced-usage
 /components/yaml/yaml_format /reference/formats/yaml
-/components/expression_language/syntax /components/expression_language#expression-language-syntax
+/components/expression_language/syntax /reference/formats/expression_language
 /components/expression_language/extending /components/expression_language#expression-language-extending
 /notifier/chatters /notifier#sending-chat-messages
 /notifier/texters /notifier#sending-sms

reference/constraints/Expression.rst

@@ -140,7 +140,7 @@ One way to accomplish this is with the Expression constraint:
 
 The :ref:`expression <reference-constraint-expression-option>` option is the
 expression that must return true in order for validation to pass. Learn more
-about the :ref:`expression language syntax <expression-language-syntax>`.
+about the :doc:`expression language syntax </reference/formats/expression-language>`.
 
 .. sidebar:: Mapping the Error to a Specific Field
 
@@ -262,7 +262,7 @@ Options
 
 The expression that will be evaluated. If the expression evaluates to a false
 value (using ``==``, not ``===``), validation will fail. Learn more about the
-:ref:`expression language syntax <expression-language-syntax>`.
+:doc:`expression language syntax </reference/formats/expression-language>`.
 
 Depending on how you use the constraint, you have access to different variables
 in your expression:

routing.rst

@@ -415,8 +415,8 @@ arbitrary matching logic:
         };
 
 The value of the ``condition`` option is an expression using any valid
-:ref:`expression language syntax <expression-language-syntax>` and can use any
-of these variables created by Symfony:
+:doc:`expression language syntax </reference/formats/expression-language>` and
+can use any of these variables created by Symfony:
 
 ``context``
     An instance of :class:`Symfony\\Component\\Routing\\RequestContext`,

security/expressions.rst

@@ -38,7 +38,7 @@ that method is invented for this example).
 
 .. _security-expression-variables:
 
-The security expression must use any valid :ref:`expression language syntax <expression-language-syntax>`
+The security expression must use any valid :doc:`expression language syntax </reference/formats/expression-language>`
 and can use any of these variables created by Symfony:
 
 ``user``

service_container/expression_language.rst

@@ -71,7 +71,7 @@ to another service: ``App\Mailer``. One way to do this is with an expression:
                 ->args([expr("service('App\\\\Mail\\\\MailerConfiguration').getMailerMethod()")]);
         };
 
-Learn more about the :ref:`expression language syntax <expression-language-syntax>`.
+Learn more about the :doc:`expression language syntax </reference/formats/expression-language>`.
 
 In this context, you have access to 2 functions: