diff --git a/src/TwigComponent/doc/index.rst b/src/TwigComponent/doc/index.rst
index 9fb4df3a0bd..d745cd76f2f 100644
--- a/src/TwigComponent/doc/index.rst
+++ b/src/TwigComponent/doc/index.rst
@@ -951,33 +951,39 @@ When overriding the ``alert_message`` block, you have access to the ``message``
         {% endblock %}
     {% endcomponent %}
 
-Sometimes, you may want to override a block of a deeply nested component and you need access to
-some properties or functions from higher components. That can be done via the ``this.parent...`` hierarchy:
+As mentioned before, variables from lower components are merged with those from upper components. When you need
+access to some properties or functions from higher components, that can be done via the ``outerScope...`` variable:
 
 .. code-block:: twig
 
     {# templates/SuccessAlert.html.twig #}
-    {% component Alert with { type: 'success' } %}
-        {{ this.parent.someFunction }} {# this refers to SuccessAlert #}
+    {% set name = 'Fabien' %}
+    {% set message = 'Hello' %}
+    {% component Alert with { type: 'success', name: 'Bart' } %}
+        Hello {{ name }} {# name = Bart #}
+
+        {{ message }} {{ outerScope.name }} {# message = 'Hello', name = Fabien #}
+
+        {{ outerScope.this.someFunction }} {# this refers to SuccessAlert #}
 
-        {{ this.parent.someProp }} {# references a "someProp" prop from SuccessAlert #}
+        {{ outerScope.this.someProp }} {# references a "someProp" prop from SuccessAlert #}
     {% endcomponent %}
 
-To keep the generic Alert component unaware of the ``someProp`` prop it is better to use ``this.parent``
+To keep the generic Alert component unaware of the ``someProp`` prop it is better to use ``outerScope.this``
 instead of passing that info along via Alert's attributes.
 
-You can keep referring to 'grand parents' as well. Just add another ``parent``.
-Remember though that the parent reference only starts once you're INSIDE the (embedded) component.
+You can keep referring to components higher up as well. Just add another ``outerScope``.
+Remember though that the ``outerScope`` reference only starts once you're INSIDE the (embedded) component.
 
 .. code-block:: twig
 
     {# templates/FancyProfileCard.html.twig #}
     {% component Card %}
         {% block header %}
-            {% component Alert with { message: this.parent.someProp } %} {# not yet INSIDE the Alert template #}
+            {% component Alert with { message: outerScope.this.someProp } %} {# not yet INSIDE the Alert template #}
                 {% block content %}
                     {{ message }} {# same value as below, indirectly refers to FancyProfileCard::someProp #}
-                    {{ this.parent.parent.someProp }} {# directly refers to FancyProfileCard::someProp #}
+                    {{ outerScope.outerScope.this.someProp }} {# directly refers to FancyProfileCard::someProp #}
                 {% endblock %}
             {% endcomponent %}
         {% endblock %}
@@ -985,7 +991,7 @@ Remember though that the parent reference only starts once you're INSIDE the (em
 
 .. versionadded:: 2.12
 
-    The ability to refer to higher components via the ``this.parent`` syntax was added in 2.12.
+    The ability to refer to the scope of higher components via the ``outerScope`` variable was added in 2.12.
 
 Component HTML Syntax
 ---------------------