A lot of minor (mostly textual) changes

[ssproject1617.git] / report / v8_error.tex

diff --git a/report/v8_error.tex b/report/v8_error.tex
index dd7d93b..e667af8 100644 (file)
--- a/report/v8_error.tex
+++ b/report/v8_error.tex
@@ -8,7 +8,7 @@
 
                \begin{result}
                Disabled by default but there is no way to enable error logging
-               without outputting detailed error information. \emph{PDOException::getMessage}
+               without outputting detailed error information. \code{PDOException::getMessage}
                is directly logged to the specified logging target (user or logfile).
                \end{result}
 
@@ -54,7 +54,7 @@
                unauthorized access and modification.
 
                \begin{result}
-               There is a htaccess which is supposed to block access to the log files.
+               There is an \code{.htaccess} which is supposed to block access to the log files.
                Blocking access to the logs depends on the server configuration
                because the log files are part of the main program directory.
                Clear documentation which warns users about this behavior is missing.
@@ -70,8 +70,8 @@
                hashes, or API tokens.
 
                \begin{result}
-               The application itself does not log any usernames/passwords.
-               \emph{PDOException}'s end up in the log files however, the database driver implementation
+               The application itself does not log any usernames or passwords.
+               \code{PDOException}s end up in the log files however, the database driver implementation
                could append sensitive data to the exception message.
                Documentation suggesting users should verify that the database driver they end up using doesn't include sensitive data in exception messages is absent.
                \end{result}