From 2fbb6d9ca1e38dc49415ee4fc126c1bc531ee82b Mon Sep 17 00:00:00 2001 From: Attila Gulyas <toraritte@gmail.com> Date: Wed, 16 Aug 2017 09:37:40 -0700 Subject: [PATCH] Fix typos --- docs/framework/database/schema-design.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/framework/database/schema-design.md b/docs/framework/database/schema-design.md index bbe21dc1..65477ce2 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 -- GitLab