From 5643e00cce32def42babc07f7ef9456939b931b3 Mon Sep 17 00:00:00 2001
From: David Runge <dave@sleepmap.de>
Date: Sat, 8 Jul 2017 17:25:40 +0200
Subject: thesis/thesis.tex: Minor fixes below Discussion.

---
 thesis/thesis.tex | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

(limited to 'thesis/thesis.tex')

diff --git a/thesis/thesis.tex b/thesis/thesis.tex
index de8888c..870d6d2 100644
--- a/thesis/thesis.tex
+++ b/thesis/thesis.tex
@@ -1681,8 +1681,8 @@ ssr-aap -N “server” -C “127.0.0.1:50002”
     further in the following section, followed by an outlook on related
     future work.\\
     Due to the versatility of how the \gls{ssr} can be used in a networking
-    context, its likely, that some of its possibilities are not even accounted
-    for.
+    context, it is likely, that some of its possibilities are not even
+    accounted for.
 
     \subsection{Implemented Features}
       \label{subsec:implemented_features}
@@ -1697,9 +1697,9 @@ ssr-aap -N “server” -C “127.0.0.1:50002”
       described in~\ref{subsec:publisher_subscriber_interface} and extends it,
       where appropriate. Additionally an open client-server architecture has
       been created, according to a message level system, further elaborated
-      upon in \gls{subsubsec:message_levels}. An attempt at giving extensive
-      examples on the various setup possibilities, that are now possible, is
-      made in \gls{subsubsec:setups}, some of which are still dependant on
+      upon in~\ref{subsubsec:message_levels}. An attempt at giving extensive
+      examples on the various setup possibilities, that are now available, is
+      made in~\ref{subsubsec:setups}, some of which are still dependant on
       various missing features (see~\ref{subsec:future_work}).\\
       The \gls{osc} messaging system is adhering to the aforementioned
       client-server architecture by distinguishing between client-only,
@@ -1832,7 +1832,7 @@ ssr-aap -N “server” -C “127.0.0.1:50002”
         \gls{osc} interface trying to create a possibly defective address and
         send poll messages out to it.\\
         While only some of the above mentioned scenarios could lead to a crash
-        of the program (under certain circumstances), unhandled all of them
+        of the program under certain circumstances, left unhandled, all of them
         waste ressources, which is undesired.
         To circumvent possibly harmful input using the \gls{osc} interface, a
         set of sanity checks were implemented, that only allow for a received
@@ -1872,10 +1872,10 @@ ssr-aap -N “server” -C “127.0.0.1:50002”
 
     \subsection{Future Work}
       \label{subsec:future_work}
-      Several features, interesting for different use-cases, could not be
-      implemented in the time frame set for this work. They are however
-      complementary to the \gls{osc} networking extension, or can be
-      implemented on top of it.\\
+      Several features, interesting for different use-cases, were out of scope
+      for this work. They are however complementary to the \gls{osc} networking
+      extension, or can be implemented on top of it and will be discussed in
+      the following sections.\\
 
       \subsubsection{Non-renderer}
         \label{subsubsec:non-renderer}
-- 
cgit v1.2.3-54-g00ecf

