Minor fixes (mainly textual) for v{2,3,4,5,7,8,11}

[ssproject1617.git] / report / v5_input.tex

diff --git a/report/v5_input.tex b/report/v5_input.tex
index 27ee206..e29538d 100644 (file)
--- a/report/v5_input.tex
+++ b/report/v5_input.tex
@@ -11,7 +11,7 @@
 
        % They skip 5.2
        \addtocounter{enumi}{1}
-       \item\fail{} Verify that server side input validation failures result in 
+       \item\fail{} Verify that server side input validation failures result in
                request rejection and are logged.
 
                \begin{result}
@@ -78,7 +78,7 @@
 
        \item\pass{} Verify that the application is not susceptible to common
                \XML{} attacks, such as XPath query tampering, \XML{} External Entity
-               attacks, and \XML{} injection attacks. 
+               attacks, and \XML{} injection attacks.
 
                \begin{result}
                No \XML{} or related techniques are used and thus the application is
@@ -148,7 +148,7 @@
                against a defined schema including allowed characters, length and
                pattern (e.g.\  credit card numbers or telephone, or validating that two
                related fields are reasonable, such as validating suburbs and zip or
-               post codes match). 
+               post codes match).
 
                \begin{result}
                Email addresses are validated against \PHP's stander functionality.
@@ -164,13 +164,13 @@
                \begin{CJK}{UTF8}{min}ねこ\end{CJK} or O'Hara)
 
                \begin{result}
-               Emailaddresses with non-ASCII characters are rejected. Unicode
+               Email addresses with non-ASCII characters are rejected. Unicode
                characters are displayed correctly.
                \end{result}
 
        \item\fail{} Make sure untrusted \HTML{} from WYSIWYG editors or similar are
                properly sanitized with an \HTML{} sanitizer and handle it
-               appropriately according to the input validation task and encoding task. 
+               appropriately according to the input validation task and encoding task.
 
                \begin{result}
                This is not the case, any \HTML{} is allowed.
@@ -180,7 +180,7 @@
                ensure that \HTML{} sanitization is enabled instead.
 
                \begin{result}
-               See previous item.
+               Just as with the previous item, any \HTML{} is allowed.
                \end{result}
 
        \item\pass{} Verify that data transferred from one DOM context to another,