[Cookbook] - fix component_architecture

Author: WebMamba

ux.symfony.com/cookbook/component_architecture.md

@@ -13,7 +13,7 @@ published_at: '2024-08-02'
 
 In SymfonyUX exist two packages: [TwigComponents](https://symfony.com/bundles/ux-twig-component/current/index.html) and [LiveComponent](https://symfony.com/bundles/ux-live-component/current/index.html).
 Those two packages allow you to create reusable components in your Symfony application.
-But the component architecture is not exclusive to Symfony, it is a design pattern that can be applied to any programming language or framework.
+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 js world already implement 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 SymfonyUX try to be as close as possible to those rules.
 So let's see what are those rules!
@@ -52,18 +52,18 @@ Or you can make composition with the following syntax:
 </twig:Card>
 ```
 
-So here we Card component, and we give to the content of this component mutliple other components.
+So here we Card component, and we give to the content of this component two others components.
 
 ### Independence
 
 This is a really important rule, and not obvious. But your component should leave on his own context,
-he should not be aware of the rest of the page. You should to talk one component into a page, to another and it should work exactly the same.
-This rule make your component trully reusable.
+he 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 work exactly the same.
+This rule make your component truly reusable.
 
 ***How does it work into Symfony?***
 
-Symfony keep the context of the page into the context of your component. So this your own responsability to follow this rules.
-But notice that if there are conflic between a variable from the context page and your component, your component context override the page context.
+Symfony keep the context of the page into the context of your component. So this your own responsibility to follow this rules.
+But notice that if there are conflict between a variable from the context page and your component, your component context override the page context.
 
 ### Props