fix grammar mistakes

deyantomov · sumn2u · commit 4d5977197103 · 2024-09-09T23:55:02.000-05:00
diff --git a/en/classes/composition.md b/en/classes/composition.md
@@ -1,6 +1,6 @@
 # Composition
 
-Composition is useful for creating "has-a" relationships which ensure loose coupling and flexibility. If we imagine that our class is a wall, the classes that make it up via composition are like bricks - smaller and more manageable components.
+Composition is useful for creating "has-a" relationships that ensure loose coupling and flexibility. If we imagine that our class is a wall, the classes that make it up via composition are like bricks - smaller and more manageable components.
 
 ## Benefits of composition
 
@@ -37,11 +37,11 @@ let myLibrary = new Library();
 console.log(myLibrary.add(myBook)); // The Great Gatsby was added to the library.
 ```
 
-In the example above, instances of the `Book` class are used to create the larger `Library` class. Composition is used to create a "has-a" relationship between the two classes (a library has books inside it) which ensures loose coupling. Changes to the `Book` class won't be reflected on the `Library` class and vice versa.
+In the example above, instances of the `Book` class are used to create the larger `Library` class. Composition is used to create a "has-a" relationship between the two classes (a library has books inside it), which ensures loose coupling. Changes to the `Book` class won't be reflected on the `Library` class,  and vice versa.
 
 ## Composition vs Inheritance
 
-While inheritance creates an "is-a" relationship (e.g. a `Car` is a `Vehicle`), composition creates a "has-a" relationship (e.g. a `Car` has an `Engine`). Here are some pros and cons for using both:
+While inheritance creates an "is-a" relationship (e.g., a `Car` is a `Vehicle`), composition creates a "has-a" relationship (e.g., a `Car` has an `Engine`). Here are some pros and cons for using both:
 
   + Inheritance
     
