From cfa0a44b1e1f5f0093b8241caeb48ce24969d876 Mon Sep 17 00:00:00 2001
From: Mustafa Haddara <haddarma@mcmaster.ca>
Date: Sun, 20 Nov 2016 13:32:13 -0500
Subject: [PATCH] proofreading tex file for MG

---
 Doc/Design/MG/ModuleGuide.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Doc/Design/MG/ModuleGuide.tex b/Doc/Design/MG/ModuleGuide.tex
index 964fc9b..a4852ac 100644
--- a/Doc/Design/MG/ModuleGuide.tex
+++ b/Doc/Design/MG/ModuleGuide.tex
@@ -205,7 +205,7 @@ The following definitions explain all important terms used to describe the syste
     \end{figure}
 \end{description}
 
-\subsection{Underlaying Architecture}
+\subsection{Underlaying Architecture} %% you mean "Underlying"
 
 Now that the general idea of the system has been explained, this section will take the level of abstraction one step further. This level of abstraction demonstrates the module decomposition of the system. Arrows in the diagram represent sub-modules that help reach the next module in the system. Note that this is not a uses diagram, nor is it intended to be.
 
-- 
GitLab