Update README.md

Author: fx-biocoder

3 - Liskov Substition Principle/README.md

@@ -1,12 +1,12 @@
 # Liskov Substitution Principle (LSP)
 
-The Liskov Substitution Principle (LSP) is a design principle from the SOLID principles that suggests that subtypes should be substitutable for their base types. In other words, any object or instance of a subtype should be able to be used in place of an instance of its base type without affecting the correctness of the program.
+The Liskov Substitution Principle (LSP) states that subtypes should be substitutable for their base types. Any object or instance of a subtype should be able to be used in place of an instance of its base type without affecting the correctness of the program.
 
-The LSP is important because it ensures that the behavior of the program remains consistent when working with different types of objects. It allows you to write code that is more flexible and adaptable, and makes it easier to add new types to your codebase without having to modify existing code.
+This principle ensures that the behavior of the program remains consistent when working with different types of objects. Therefore, it is easier to add new types to your codebase without having to modify existing code.
 
-To follow the LSP, it's important to ensure that all subclasses or subtypes of a class or interface adhere to the same behavior as the base class or interface. This means that the subclass should not introduce new behaviors that are not present in the base class, and it should not modify the behavior of any methods or properties that are inherited from the base class.
+You must ensure that all subclasses or subtypes of a class or interface adhere to the same behavior as the base class or interface. This means that the subclass should not introduce new behaviors that are not present in the base class, and it should not modify the behavior of any methods or properties that are inherited from the base class.
 
-In practice, this means that you should carefully consider the contract defined by the base class or interface, and ensure that any subclasses or subtypes adhere to that contract. This allows you to write code that is more generic and reusable, and reduces the amount of code duplication and maintenance required over time.
+In practice, this means that you should carefully consider the contract defined by the base class or interface, and ensure that any subclasses or subtypes adhere to that contract. This method will reduce the amount of code duplication and maintenance required over time.
 
 
 ### Class diagram for the current example