Reword

Author: javiereguiluz

src/TwigComponent/doc/index.rst

@@ -455,17 +455,16 @@ The mount() Method
 ~~~~~~~~~~~~~~~~~~
 
 The ``mount()`` method gives you more control over how your "props" are handled.
-It is called only once: immediately after your component is instantiated.
-The ``mount()`` method **cannot access the values of the public properties**
-passed when rendering the component.
+It is called once, immediately after the component is instantiated, **but before**
+the component system assigns the props you passed when rendering.
 
 For example, if you call your component like this:
 
 .. code-block:: html+twig
 
     <twig:Alert type="error" message="..."/>
 
-The following code won't work as expected:
+The following code won't work as expected::
 
     // src/Twig/Components/Alert.php
     // ...
@@ -478,8 +477,8 @@ The following code won't work as expected:
 
         public function mount(): void
         {
-            {# ❌ this won't work: at this point, the $type property still has its
-                   default value. Passed properties are not yet available. #}
+            {# ❌ this won't work: at this point $type still has its default value.
+                   Passed values are not yet available in props. #}
             if ('error' === $this->type) {
                 // ...
             }
@@ -488,7 +487,32 @@ The following code won't work as expected:
         // ...
     }
 
-Instead, define the values you need in the ``mount()`` method as arguments::
+Inside ``mount()``, each prop has only its *default* value (or ``null`` if it is
+untyped and has no default). If you need a prop's value, declare a parameter in
+``mount()`` whose name matches the prop instead of reading the public property::
+
+    public function mount(string $type): void
+    {
+        {# ✅ this works as expected: the $type argument in PHP has the value
+               passed to the 'type' prop in the Twig template #}
+        if ('error' === $type) {
+            // ...
+        }
+    }
+
+If a prop name (e.g. ``type``) matches an argument name in ``mount()``,
+its value will be passed only to the method. The component system **will not**
+set it on a public property or use it in the component's ``attributes``.
+
+``mount()`` can also receive props **even when no matching public property
+exists**. For example, pass an ``isError`` prop instead of ``type``:
+
+.. code-block:: html+twig
+
+    <twig:Alert isError="{{ true }}" message="..."/>
+
+Define a ``$isError`` argument to capture the prop and initialize other
+properties using that value::
 
     #[AsTwigComponent]
     class Alert
@@ -498,26 +522,14 @@ Instead, define the values you need in the ``mount()`` method as arguments::
 
         public function mount(bool $isError = false): void
         {
-            {# ✅ this works as expected #}
             if ($isError) {
-                // ...
+                $this->type = 'danger';
             }
         }
 
         // ...
     }
 
-Now, pass the ``mount()`` argument like any other prop:
-
-.. code-block:: html+twig
-
-    <twig:Alert isError="{{ true }}" message="..."/>
-
-If a prop name (e.g. ``isError``) matches an argument name in ``mount()``,
-its value will be passed to the method. In that case, the component system
-**will not** set it on a public property or use it in the component's
-``attributes``.
-
 PreMount Hook
 ~~~~~~~~~~~~~