summaryrefslogtreecommitdiffstats
path: root/notFinishedCode/Report/test.tex~
diff options
context:
space:
mode:
Diffstat (limited to 'notFinishedCode/Report/test.tex~')
-rw-r--r--notFinishedCode/Report/test.tex~2
1 files changed, 1 insertions, 1 deletions
diff --git a/notFinishedCode/Report/test.tex~ b/notFinishedCode/Report/test.tex~
index 5e03427..7f8188a 100644
--- a/notFinishedCode/Report/test.tex~
+++ b/notFinishedCode/Report/test.tex~
@@ -312,7 +312,7 @@ When defining these rules, it is important to define a limited state space for e
response from the other side. Our approch to this problem was to build a simple synchronous protocol, where every expected message is
confirmed or otherwise the connection between two sides is immediatelly terminated. Since designing protocols is a demanding and challenging
topic which requires years of experience and verification, we do not expect that we had developed the best possible and an optimum
-protocol\footnote{Design ideas and references for the protocol design have been used from the
+protocol\footnote{Design concepts and paradigms for the protocol design have been used from the
``Network Protocol Design and Evaluation'' course, lectured by Stefan R\"{u}hrup}.
In the following paragraphs we will try to clarify how our protocol works. Before we start to go into detail how the protocol works,
it is important to remember that we differentiate two sides, handler and the controller side. The handler side represent the device