[Doc] Improve RST syntax of some contents

Author: javiereguiluz

src/LazyImage/Resources/doc/index.rst

@@ -69,8 +69,9 @@ There is also support for the ``srcset`` attribute by passing an
         }) }}
     />
 
-**Note** The ``stimulus_controller()`` function comes from
-`WebpackEncoreBundle v1.10`_.
+.. note::
+
+    The ``stimulus_controller()`` function comes from `WebpackEncoreBundle v1.10`_.
 
 Instead of using a generated thumbnail that would exist on your
 filesystem, you can use the BlurHash algorithm to create a light,

src/LiveComponent/src/Resources/doc/index.rst

@@ -968,10 +968,12 @@ Now, when the form is submitted, it will execute the ``save()`` method
 via Ajax. If the form fails validation, it will re-render with the
 errors. And if it's successful, it will redirect.
 
-**NOTE**: Make sure that each time the user changes a field, you update
-the component's model. If you don't do this, when you trigger the
-action, it will *not* contain the form's data because the data in the
-fields and the component's data will be out of sync.
+.. note::
+
+    Make sure that each time the user changes a field, you update the
+    component's model. If you don't do this, when you trigger the action, it
+    will *not* contain the form's data because the data in the fields and the
+    component's data will be out of sync.
 
 An easy way to accomplish this (explained more in the :ref:`Forms <forms>`
 section above) is to add:
@@ -1064,8 +1066,10 @@ property.
 Validation (without a Form)
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-**NOTE** If your component :ref:`contains a form <forms>`, then validation
-is built-in automatically. Follow those docs for more details.
+.. note::
+
+    If your component :ref:`contains a form <forms>`, then validation
+    is built-in automatically. Follow those docs for more details.
 
 If you're building some sort of form *without* using Symfony's form
 component, you *can* still validate your data.
@@ -1328,9 +1332,11 @@ Thanks to the ``data-model-map``, whenever the ``markdown_value`` model
 updates in the child component, the ``post.content`` model will be
 updated in the parent component.
 
-**NOTE**: If you *change* a ``LiveProp`` of a child component on the
-server (e.g. during re-rendering or via an action), that change will
-*not* be reflected on any parent components that share that model.
+.. note::
+
+    If you *change* a ``LiveProp`` of a child component on the server
+    (e.g. during re-rendering or via an action), that change will
+    *not* be reflected on any parent components that share that model.
 
 Full Embedded Component Example
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/Swup/Resources/doc/index.rst

@@ -58,8 +58,9 @@ initialize Swup:
         </body>
     </html>
 
-**Note** The ``stimulus_controller()`` function comes from
-`WebpackEncoreBundle v1.10`_.
+.. note::
+
+    The ``stimulus_controller()`` function comes from `WebpackEncoreBundle v1.10`_.
 
 That's it! Swup now reacts to a link click and run the default fade-in
 transition.
@@ -180,11 +181,10 @@ Then in your template, add your controller to the HTML attribute:
         </body>
     </html>
 
-..
+.. note::
 
-   **Note**: be careful to add your controller **before** the Swup
-   controller so that it is executed before and can listen on the
-   ``swup:connect`` event properly.
+   Be careful to add your controller **before** the Swup controller so that it
+   is executed before and can listen on the ``swup:connect`` event properly.
 
 Backward Compatibility promise
 ------------------------------

src/TwigComponent/src/Resources/doc/index.rst

@@ -312,11 +312,12 @@ need to populate, you can render it with:
 
     {{ component('featured_products') }}
 
-**NOTE** Because components are services, normal dependency injection
-can be used. However, each component service is registered with
-``shared: false``. That means that you can safely render the same
-component multiple times with different data because each component will
-be an independent instance.
+.. note::
+
+    Because components are services, normal dependency injection can be used.
+    However, each component service is registered with ``shared: false``. That
+    means that you can safely render the same component multiple times with
+    different data because each component will be an independent instance.
 
 Computed Properties
 ~~~~~~~~~~~~~~~~~~~