diff --git a/src/roadmaps/software-design-architecture/content/100-clean-code-principles/102-meaningful-names.md b/src/roadmaps/software-design-architecture/content/100-clean-code-principles/102-meaningful-names.md
index 0a62fc041..5101b1bf0 100644
--- a/src/roadmaps/software-design-architecture/content/100-clean-code-principles/102-meaningful-names.md
+++ b/src/roadmaps/software-design-architecture/content/100-clean-code-principles/102-meaningful-names.md
@@ -1,7 +1,7 @@
 # Meaningful Names
 
-Meaningful names in system design architecture refer to the practice of giving clear and descriptive names to different components of a system, such as variables, functions, and classes. This can help to make the system more understandable and maintainable by clearly communicating the purpose of each component and its intended usage.
+You should follow the practice of giving clear and descriptive names to different components of a system, such as variables, functions, and classes. This can help to make the system more understandable and maintainable by clearly communicating the purpose of each component and its intended usage.
 
 Learn more from the following links:
 
-- [What’s in a Name? - Architecture](https://www.innoq.com/en/blog/whats-in-a-name-architecture/)
\ No newline at end of file
+- [A Guide for Naming Things in Programming](https://levelup.gitconnected.com/a-guide-for-naming-things-in-programming-2dc2d74879f8)
\ No newline at end of file