TCP inherently is a state based system and thus we have considered the
following models.
-\paragraph{Labeled Transition System (LTS)}. A LTS would
+\paragraph{Labeled Transition System (LTS)} A LTS would
be a fitting technique to model the SUT in since the
behaviour of TCP is that both the server and the client have internal states to
which they transition based upon input coming from the other.
erroneous clients or servers since LTS is purely input output and by default
there is no data involved.
-\paragraph{Properties}. Describing TCP in terms of properties would in theory
+\paragraph{Properties} Describing TCP in terms of properties would in theory
be possible but it would require a very different adapter. The adapter should
be handed a trace and it should run the entire trace and return the sequence of
flags sent and received. Because of the high adapter complexity and the
\subsection{\GAST}
\GAST is an open source model based test tool developed by Koopman et
-al.\cite{koopman2003gast} and is a design specific language written in the
+al.\cite{koopman2003gast} and is a domain specific language written in the
functional programming language Clean. Models in \GAST must be expressed as
functions. \GAST supports two different types of testing. Standard model
checking and property based testing. As discussed earlier we are not using