diff --git a/Doc/TestReport/TestReport.pdf b/Doc/TestReport/TestReport.pdf
index e0b2eaa6aafbf8c969fe7d4f2cafbbec663b5cec..24b9fe7ce98337a36c9fc0b507be32e2c1903868 100644
Binary files a/Doc/TestReport/TestReport.pdf and b/Doc/TestReport/TestReport.pdf differ
diff --git a/Doc/TestReport/TestReport.tex b/Doc/TestReport/TestReport.tex
index e78dd56c89d4c3b151294a80230b1dc0aad91ff7..3502c0dcfeeb4b99cb1fce7700c3880f9b09ce66 100644
--- a/Doc/TestReport/TestReport.tex
+++ b/Doc/TestReport/TestReport.tex
@@ -105,6 +105,7 @@ exported GIF image will match what is created by the user of our product.
 The only tool to be utilized to test this product will be the Microsoft Unit
 Test Framework that is native with Visual Studio. Through this unit testing framework, we will have it set up that it automatically does comparisons of the GIF output to the expected output where it can in a quick manner compare the pixel values to ensure complete accuracy. Throughout utilizing this framework, we have always gotten successful results which allowed us to identify other areas wher the majority of the problems occured.		
 \section{Trace to Requirements}
+
 		
 \section{Trace to Modules}
 Refer to Test Plan to see corresponding Tests and Module Guide to see corresponding Modules.
@@ -114,21 +115,21 @@ Refer to Test Plan to see corresponding Tests and Module Guide to see correspond
 \toprule
 \textbf{Test} & \textbf{Modules}\\
 \midrule
-ID1 & MIL\\
-ID2 &  MIL\\
-ID3 & MIL\\
-ID4 &  MIL\\
-ID5 &  MIL\\
-ID6 & MIL\\
-ID7 &  MIL\\
-ID8 &  MIL\\
+ID1 & M5, M9\\
+ID2 &  M5, M9\\
+ID3 & M5,, M9\\
+ID4 &  M5,  M9\\
+ID5 &  M8\\
+ID6 & M8\\
+ID7 &  M8\\
+ID8 &  M8\\
 ID9 & MIL\\
 ID10 &  MIL\\
 ID11 & MIL\\
 ID12 & M6\\
-ID13 &  MIL\\
-ID14 & \ MIL\\
-ID15 &  MIL\\
+ID13 &  M6\\
+ID14 & M6\\
+ID15 &  M6\\
 ID16 &  MIL\\
 ID17 &  MIL\\
 ID18 &  MIL\\