haalt trailing space weg

diff --git a/1intro.tex b/1intro.tex
index eca8c06..2e402b1 100644 (file)
--- a/1intro.tex
+++ b/1intro.tex
@@ -2,16 +2,16 @@
 %1, 2
 The objective of this document is to provide an approach for testing a
 particular implementation of \textit{Transmission Control Protocol} (TCP). TCP
-is a host-to-host protocol that provides a reliable communication. 
+is a host-to-host protocol that provides a reliable communication.
 
 This testing approach can be used by either an internal test team or an
 independent testing team. The test effort's goal is to become confident about
 the conformance of an existing implementation to the specification created by
 \textit{The Internet Engineering Task Force}
 (IETF)\footnote{\url{http://www.ietf.org}} as document
-\textit{RFC793}~\cite{rfc793}. This document is explicitly \emph{not} intented 
-to serve as guideline for testing during the development phase, but for testing 
-conformatiy to the specification of an \emph{existing} implementation. 
+\textit{RFC793}~\cite{rfc793}. This document is explicitly \emph{not} intended
+to serve as guideline for testing during the development phase, but for testing
+conformity to the specification of an \emph{existing} implementation.
 
 \subsection{SUT}
 %3,4
@@ -19,10 +19,10 @@ The \textit{System under test} (SUT) is a
 Java\footnote{\url{http://www.java.com}} TCP driven echo server that executed
 on a virtualized Ubuntu system\footnote{\url{http://www.ubuntu.com}} running on
 the Linux kernel\footnote{\url{http://www.kernel.org}} version $3.13$. To test
-the error behaviour custom iptables output policies have to be
-set Listing~\ref{listing:iptables}. This is needed because the kernel by default 
-closes all connections from unknown sources and the manually created TCP 
-packets used in testing the implementation are from a source unknown to the 
+the error behaviour custom iptables output policies have to be set
+Listing~\ref{listing:iptables}. This is needed because the kernel by default
+closes all connections from unknown sources and the manually created TCP
+packets used in testing the implementation are from a source unknown to the
 kernel.
 
 \begin{lstlisting}[label={listing:iptables},caption={settings iptables}]
@@ -34,23 +34,20 @@ DROP        tcp     --      anywhere        anywhere        tcp flags:RST/RST
 
 \subsection{Risks} \label{sec:risks}
 %5. Risks
-Risks can be divided into two categories. Project risks and product risks. 
+Risks can be divided into two categories. Project risks and product risks.
 Because an existing implementation is used the project risk are non applicable.
-Product risks even more so, since it is unknown if the product has been 
-tested during development. 
+Product risks even more so, since it is unknown if the product has been tested
+during development.
 
-The product risks for the SUT are significant because misbehaviour of the SUT 
-could have potential large consequences. The key characteristics of TCP are 
-integrity and reliability~\cite{rfc793}, these characteristics cease to exist 
-when the implementation is faulty. 
+The product risks for the SUT are significant because misbehaviour of the SUT
+could have potential large consequences. The key characteristics of TCP are
+integrity and reliability~\cite{rfc793}, these characteristics cease to exist
+when the implementation is faulty.
 
 Because TCP is a core functionality of a networking capable system it is
 crucial that the TCP implementation functions according to the specification.
 Several critical systems could rely on the correct functionality of the TCP
-implementation. A  failure in the SUT could therefore have extensive 
-consequences.
-Even more so since TCP is a computer-to-computer protocol, which leaves no
-room for ambiguity, which could be solved in a computer-to-human protocol. 
-
-
-
+implementation. A failure in the SUT could therefore have extensive
+consequences. Even more so since TCP is a computer-to-computer protocol, which
+leaves no room for ambiguity, which could be solved in a computer-to-human
+protocol.

diff --git a/2approach.tex b/2approach.tex
index 634edf8..567dba6 100644 (file)
--- a/2approach.tex
+++ b/2approach.tex
@@ -25,14 +25,14 @@ several subcategories. Below we will discuss the qualities which are relevant
 to the SUT.
 \begin{itemize}
        \item \textbf{Functional suitability}\\
-       As descibed in Section~\ref{sec:risks} the SUT is core functioanlity of the
-       networking capable system. Because many other systems running on the system
-       could rely on it it is very important that the SUT is functionaly suitable.
-       Therefore all three subcharacteristics of Functional Suitability
-       (\textit{Functional completeness, Functional correctness, Functional
-       appropriateness}) are of vital importance. As was previously mentioned in
-       Section~\ref{sec:risks} extra emphasis should be placed on testing
-       \emph{Functional Correctness} as recovery from Failures in
+       As described in Section~\ref{sec:risks} the SUT is core functionality of
+       the networking capable system. Because many other systems running on the
+       system could rely on it it is very important that the SUT is functionality
+       suitable.  Therefore all three sub characteristics of Functional
+       Suitability (\textit{Functional completeness, Functional correctness,
+       Functional appropriateness}) are of vital importance. As was previously
+       mentioned in Section~\ref{sec:risks} extra emphasis should be placed on
+       testing \emph{Functional Correctness} as recovery from Failures in
        computer-to-computer systems is problematic.
 \end{itemize}