diff --git a/typo3/sysext/core/Documentation/Changelog/9.4/Feature-85829-ImplementSymfonyExpressionLanguageForTypoScriptConditions.rst b/typo3/sysext/core/Documentation/Changelog/9.4/Feature-85829-ImplementSymfonyExpressionLanguageForTypoScriptConditions.rst
index fdde5738a3cbae5cc4bb33b68f886d9d4426b29f..c7c18462e98f9357d45637dad44ad9b9c05bfe00 100644
--- a/typo3/sysext/core/Documentation/Changelog/9.4/Feature-85829-ImplementSymfonyExpressionLanguageForTypoScriptConditions.rst
+++ b/typo3/sysext/core/Documentation/Changelog/9.4/Feature-85829-ImplementSymfonyExpressionLanguageForTypoScriptConditions.rst
@@ -33,10 +33,11 @@ Here are some examples to understand the power of the expression language:
    # This condition does match if "foo" **not** matches the regExp: `/bar/`
    [END]
 
-   [applicationContext == "Production"] && [userId == 15]
-   # This condition match if application context is "Production" AND logged in user has the uid 15
-   # This condition could also be combined in one condition:
-   # [applicationContext == "Production" && userId == 15]
+   [applicationContext == "Production" && userId == 15]
+   # This condition matches if application context is "Production" AND logged in user has the uid 15
+   # Note that the old syntax with two blocks combined with && is deprecated
+   # and will not work in v10:
+   # [applicationContext == "Production"] && [userId == 15]
    [END]
 
    [request.getNormalizedParams().getHttpHost() == 'typo3.org']