Update src/roadmaps/software-design-architecture/content/100-clean-code-principles/101-be-consistent.md

src/roadmaps/software-design-architecture/content/100-clean-code-principles/101-be-consistent.md

@@ -1,7 +1,7 @@
 # Be Consistent
 
-Being consistent in system design architecture refers to maintaining a consistent pattern or structure in the design of a system. This can include using consistent naming conventions, data structures, and interfaces throughout the system, as well as adhering to established design principles and best practices. Consistency can help to make the system more maintainable, understandable, and extendable.
+Being consistent refers to maintaining a consistent pattern. This can include using consistent naming conventions, data structures, and interfaces throughout the system, as well as adhering to established design principles and best practices. Consistency can help to make the system more maintainable, understandable, and extendable.
 
 Learn more from the following links:
 
-- [Strongly Consistent vs Eventually Consistent for System Design](https://medium.com/double-pointer/strongly-consistent-vs-eventually-cosistent-for-system-design-interview-f67f9c1882ed)
+- [10 Tips for Writing Clean Code](https://www.pluralsight.com/blog/software-development/10-steps-to-clean-code)