X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=report%2Freflection.auditing_process.tex;h=9413548a539460f83585c2e0769c3bec3b5a91be;hb=bf85c6f569c297c733227d532cbaec0dd663e985;hp=3811140db64430be5f64cc6b763a5cd8dc8d5942;hpb=300e85f3c63352c982b683c730531a8ede1a3895;p=ssproject1617.git

diff --git a/report/reflection.auditing_process.tex b/report/reflection.auditing_process.tex
index 3811140..9413548 100644
--- a/report/reflection.auditing_process.tex
+++ b/report/reflection.auditing_process.tex
@@ -2,13 +2,13 @@
 
 % Daan: If you would have to do something like this again? (...)
 We have noticed that, when doing an audit in a team, it is not feasible for
-everybody to have read all source code. Henceforth, trying this is just a bad
+everybody to have read all source code. Trying this is just a bad
 idea. We are happy to have divided the project by ASVS category, instead of
 program component. For each requirement the the ASVS, the
 team had to verify that there were no mistakes in the code. This would have
 taken a lot of time if we had to verify each component for each requirement.
 Furthermore, the ASVS is an easy guide for dividing the work\footnote{The
-categories in the ASVS are all of similar size. We settled on giving each team
+categories in the ASVS are all more or less of similar size. We settled on giving each team
 member two categories to check.}. Dividing by component would have been a lot
 harder to do fairly, especially because when beginning the project we had
 little knowledge of the internals (and component sizes) of the CMS.