fix Simon review

Author: WebMamba

ux.symfony.com/cookbook/component_architecture.md

@@ -15,8 +15,8 @@ In Symfony UX exist two packages: [TwigComponents](https://symfony.com/bundles/u
 Those two packages allow you to create reusable components in your Symfony application.
 But the component architecture is not exclusive to Symfony, it's a design pattern that can be applied to any programming language or framework.
 And the Javascript world already implements this architecture for long time, on many different frameworks like React, Vue, or Svelte.
-So, a set of rules and pattern has already be defined to work with components. This is why Symfony UX try to be as close as possible to those rules.
-So let's see what are those rules!
+So, a set of rules and patterns has already be defined to work with components. This is why Symfony UX tries to be as close as possible to those rules.
+So, let's see what those rules are!
 
 ## 4 Rules
 
@@ -50,18 +50,18 @@ Or you can make composition with the following syntax:
 </twig:Card>
 ```
 
-So here we have a Card component, and we give to the content of this component two others components.
+So here we have a Card component, and we give to the content of this component two other components.
 
 ### Independence
 
-This is a really important rule, and not obvious. But your component should leave on his own context,
-it should not be aware of the rest of the page. You should be able to take one component into a page, to another and it should works exactly the same.
-This rule make your component truly reusable.
+This is a really important rule, and not obvious. But your component should live on his own context,
+it should not be aware of the rest of the page. You should be able to take a component into a page, from another and it should work exactly the same.
+This rule makes your component truly reusable.
 
 ***How does it work into Symfony?***
 
 Symfony keeps the context of the page into the context of your component. So this your own responsibility to follow those rules.
-But notice that if there are conflicts between a variable from the context page and your component, your component context override the page context.
+But notice that if there are conflicts between a variable from the context page and your component, your component context overrides the page context.
 
 ### Props