diff --git a/README.md b/README.md
index 636e22b..7050503 100644
--- a/README.md
+++ b/README.md
@@ -123,7 +123,7 @@ Here’s how each of the mentioned principle fits into modular programming:
 
 ### 6. Fat-Data over Fat-Function
    - **Why to Use:** This principle encourages the creation of data structures with rich information content, reducing and moving the logical functions to interfaces and middleware
-   - **How to Use:** Design your data models to be comprehensive and include all necessary information. This approach often favors object-oriented designs, where data and related behaviors are combined into objects. Divide objects into data models that do not contain method functions and those that contain them but do not have attributes, i.e. data. Separation of data from functions facilitates expansion and does not create artificial dependencies. For OOP - [Object-oriented programming - Wikipedia](https://en.wikipedia.org/wiki/Object-oriented_programming), [Single-responsibility principle - Wikipedia](https://en.wikipedia.org/wiki/Single-responsibility_principle) and [Dependency injection - Wikipedia](https://en.wikipedia.org/wiki/Dependency_injection) will be helpful
+   - **How to Use:** Design your data models to be comprehensive and include all necessary information. This approach often favors object-oriented designs, where data and related behaviors are combined into objects. Divide objects into data models that do not contain method functions and those that contain them but do not have attributes, i.e. data. Separation of data from functions facilitates expansion and does not create artificial dependencies. For OOP - [Object-oriented programming](https://en.wikipedia.org/wiki/Object-oriented_programming), [Single-responsibility principle](https://en.wikipedia.org/wiki/Single-responsibility_principle) and [Dependency injection](https://en.wikipedia.org/wiki/Dependency_injection) will be helpful