Report for symfony/ux#1899@ac408cf

[TwigComponent] Add note in doc about composition that component live in their own context

by @WebMamba

Some issues have been detected in this pull request

0
Coding Standard

1
Common Typos

Issues that can be fixed by applying a patch

Review the proposed patch then download it to apply it manually or execute the following command from the repository root directory: 

curl https://fabbot.io/patch/symfony/ux/1899/ac408cf3c025ad1fac1d4e528024647b8294127d/typos.diff | patch -p0
diff -ru src/TwigComponent/doc/index.rst src/TwigComponent/doc/index.rst
--- src/TwigComponent/doc/index.rst	2024-06-10 08:58:01.529822596 +0000
+++ src/TwigComponent/doc/index.rst	2024-06-10 08:58:02.158844820 +0000
@@ -340,9 +340,9 @@
 Composition vs Inheritance
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Symfony tend to follow the best pratice of the component architecture, so it's highly recommended to use Composition instead of Inheritance to reuse code betwen component (see: https://legacy.reactjs.org/docs/composition-vs-inheritance.html).
+Symfony tend to follow the best practice of the component architecture, so it's highly recommended to use Composition instead of Inheritance to reuse code between component (see: https://legacy.reactjs.org/docs/composition-vs-inheritance.html).
 
-Let's take an exemple. Some component don't know their children ahead of time. This is common for components like Alert or Dialog that represent generic “boxes”. We recommend you
+Let's take an example. Some component don't know their children ahead of time. This is common for components like Alert or Dialog that represent generic “boxes”. We recommend you
 to use the block content to pass children directly into their output :
 
 .. code-block:: html+twig

0
File Permissions

0
Merge Commits

0
Exception Messages Formatting

0
Usage of void in test files

0
Use ::class whenever possible

0
Deprecation Messages