symfony
diff --git a/‎reference/constraints/Expression.rst
Copy file name to clipboardExpand all lines: reference/constraints/Expression.rst
+5-10Lines changed: 5 additions & 10 deletions b/‎reference/constraints/Expression.rst
Copy file name to clipboardExpand all lines: reference/constraints/Expression.rst
+5-10Lines changed: 5 additions & 10 deletions
diff --git a/‎routing.rst
Copy file name to clipboardExpand all lines: routing.rst
+3-3Lines changed: 3 additions & 3 deletions b/‎routing.rst
Copy file name to clipboardExpand all lines: routing.rst
+3-3Lines changed: 3 additions & 3 deletions
diff --git a/‎security/expressions.rst
Copy file name to clipboardExpand all lines: security/expressions.rst
+2-4Lines changed: 2 additions & 4 deletions b/‎security/expressions.rst
Copy file name to clipboardExpand all lines: security/expressions.rst
+2-4Lines changed: 2 additions & 4 deletions
diff --git a/‎service_container/expression_language.rst
Copy file name to clipboardExpand all lines: service_container/expression_language.rst
+1-1Lines changed: 1 addition & 1 deletion b/‎service_container/expression_language.rst
Copy file name to clipboardExpand all lines: service_container/expression_language.rst
+1-1Lines changed: 1 addition & 1 deletion
@@ -139,9 +139,8 @@ 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. To learn
-more about the expression language syntax, see
-:ref:`expression-language-syntax`.
+expression that must return true in order for validation to pass. Learn more
+about the :ref:`expression language syntax <expression-language-syntax>`.
 
 .. sidebar:: Mapping the Error to a Specific Field
 
@@ -262,14 +261,10 @@ Options
 **type**: ``string`` [:ref:`default option <validation-default-option>`]
 
 The expression that will be evaluated. If the expression evaluates to a false
-value (using ``==``, not ``===``), validation will fail.
+value (using ``==``, not ``===``), validation will fail. Learn more about the
+:ref:`expression language syntax <expression-language-syntax>`.
 
-To learn more about the expression language syntax, see
-:ref:`expression-language-syntax`.
-
-Inside of the expression, you have access to up to 2 variables:
-
-Depending on how you use the constraint, you have access to 1 or 2 variables
+Depending on how you use the constraint, you have access to different variables
 in your expression:
 
 * ``this``: The object being validated (e.g. an instance of BlogPost);
 
@@ -414,9 +414,9 @@ arbitrary matching logic:
             ;
         };
 
-The value of the ``condition`` option is any valid :ref:`ExpressionLanguage
-expression <expression-language-syntax>` and can use any of these variables
-created by Symfony:
+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:
 
 ``context``
     An instance of :class:`Symfony\\Component\\Routing\\RequestContext`,
 
@@ -36,12 +36,10 @@ user object's ``isSuperAdmin()`` method returns ``true``, then access will
 be granted (note: your User object may not have an ``isSuperAdmin()`` method,
 that method is invented for this example).
 
-This uses an expression and you can learn more about the expression language
-syntax, see :ref:`expression-language-syntax`.
-
 .. _security-expression-variables:
 
-Inside the expression, you have access to a number of variables:
+The security expression must use any valid :ref:`expression language syntax <expression-language-syntax>`
+and can use any of these variables created by Symfony:
 
 ``user``
     The user object (or the string ``anon`` if you're not authenticated).
 
@@ -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()")]);
         };
 
-To learn more about the expression language syntax, see :ref:`expression-language-syntax`.
+Learn more about the :ref:`expression language syntax <expression-language-syntax>`.
 
 In this context, you have access to 2 functions: