typo's

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

diff --git a/report/reflection.tools.tex b/report/reflection.tools.tex
index 4205902..15ee8a7 100644 (file)
--- a/report/reflection.tools.tex
+++ b/report/reflection.tools.tex
@@ -1,16 +1,16 @@
 % How useful were code analysis tools?\r
 The usefulness of the Fortify Static Code Analysis tool turned out to be very limited.\r
-Since we had most verdicts ready before a license was provided we couldn't use\r
+Since we had most verdicts ready before a license was provided we could not use\r
 the tool as an initial guide through the code. This forced us to manually check\r
 the application source which took quite some time. After the tool became available we\r
-didn't get any new insights regarding potential security risks, just more examples\r
+did not get any new insights regarding potential security risks, just more examples\r
 of problems we already detected. An example would be the use of the \code{crypt()} \PHP{}\r
 function which will, on some platforms, use the outdated \code{DES} algorithm in order to encrypt data. The\r
 use of this function would pose a security risk and results in a failed check. Since\r
 we where only interested in providing a verdict for each check a single occurrence of\r
 this function allowed us to back-up our verdict. Fortify provides a full list of all\r
 occurrences which could be used to fix the application, our verdict on the other hand\r
-doesn't provide the developer with any information on how to fix the problem. We just\r
+does not provide the developer with any information on how to fix the problem. We just\r
 state that there is a problem.\r
 \r
 % How could they be improved? (niet echt een antwoord maar we hebben de tool ook niet echt gebruikt?)\r
@@ -24,10 +24,10 @@ focus on determining which parts of a application need to be secure and less on
 out actual security flaws.\r
 \r
 % How did you experience the rates and amounts of false and true positives?\r
-As far we where able to verify the tool didn't produce any false positives.\r
+As far we where able to verify the tool did not produce any false positives.\r
 However, Fortify was not able to detect all problems we found.\r
 Fortify concluded the application passed all checks in the \r
-Error reporting and Logging (V8) section, however we detected a number of severe\r
+Error reporting and Logging (\ref{sec:V8}) section, however we detected a number of severe\r
 problems in this area.\r
 \r
 % How might that be improved?\r