diff --git a/docs/framework/database/schema-design.md b/docs/framework/database/schema-design.md
index bbe21dc1ce7d7c9b02e957cfa588d8be84eb3c7e..65477ce29b2c863dd371377dece48805361d80a9 100644
--- a/docs/framework/database/schema-design.md
+++ b/docs/framework/database/schema-design.md
@@ -2,7 +2,7 @@
 
 ## Why a Entity Relationship Diagram may *not* be helpful
 
-As some coders are visual learners, ER Diagrams maybe a waste of time for those coders to understand the CivCRM Database modle and structure. Fundamentally CiviCRM's Schema design is way too complex, with at least 150 tables and loads of Foreign Key Constraints linking tables together any such graphic or design document that tries to map out the CiviCRM database design would most likely bring more confusion than help, especially for visual learners.
+As some coders are visual learners, ER Diagrams maybe a waste of time for those coders to understand the CiviCRM Database module and structure. Fundamentally CiviCRM's Schema design is way too complex, with at least 150 tables and loads of Foreign Key Constraints linking tables together any such graphic or design document that tries to map out the CiviCRM database design would most likely bring more confusion than help, especially for visual learners.
 
 ## Alternate Methods to ERDs to explore CiviCRM's Database Design