spelling

[ssproject1617.git] / report / reflection.tools.tex

diff --git a/report/reflection.tools.tex b/report/reflection.tools.tex
index 49c7654..4205902 100644 (file)
--- a/report/reflection.tools.tex
+++ b/report/reflection.tools.tex
@@ -36,9 +36,9 @@ generate a clear overview of which components of the application contain detecte
 problems. This could be very useful in combination with the information about\r
 components and functions which do pass the given security check. This would allow\r
 developers to determine if they suffer from chronically malformed code \r
-(e.g. all relevant code fails the check, indicating a very serious problem throughout the entire codebase) \r
+(e.g. all relevant code fails the check, indicating a very serious problem throughout the entire code base) \r
 or a single error (e.g. most relevant code passes the check except for a few isolated cases).\r
-In the tested codebase there is a clean distinction between an installer component and the\r
+In the tested code base there is a clean distinction between an installer component and the\r
 actual web application. If the installer suffers from problems not present in\r
 the web application and Fortify would be able to point out the specific check is\r
 relevant to both components the company would know which team or developer needs some major\r