X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=arch.tex;h=1fd4d4fc7afef0dfae53f4b5bc47067520ed5f57;hb=7b82824c3f3af1d6bc2d9824aae2cc2979ca8180;hp=c5e46ee1904fec4e7a2e735dd15d141ab557dcec;hpb=47820995aae3c8666173d17018ba6d09f8a3d9ff;p=msc-thesis1617.git

diff --git a/arch.tex b/arch.tex
index c5e46ee..1fd4d4f 100644
--- a/arch.tex
+++ b/arch.tex
@@ -5,9 +5,9 @@ to bytecode by the \gls{mTask}-view --- to the device. The device runs an
 interpreter which executes the \gls{Task}'s bytecode following the provided
 scheduling strategy. Devices added to the system are stored and get a profile
 for identification. These profiles are persistent during reboots of the
-\gls{iTasks}-system to allow for easy reconnecting with old devices. The
-way of interacting with \gls{mTask}-\gls{Task} is analogous to interacting
-with \gls{iTasks}-\glspl{Task}. This means that programmers can access the
+\gls{iTasks}-system to allow for easy reconnecting with old devices. The way of
+interacting with \gls{mTask}-\glspl{Task} is analogous to interacting with
+\gls{iTasks}-\glspl{Task}. This means that programmers can access the
 \glspl{SDS} made for a device in the same way as regular \glspl{SDS} and they
 can execute, combine and transform \gls{mTask}-\glspl{Task} as if they where
 normal \gls{iTasks}-\glspl{Task}.
@@ -18,12 +18,8 @@ normal \gls{iTasks}-\glspl{Task}.
 \section{iTasks}
 \input{arch.itasks}
 
-\section{Communication}
+\section{Communication}\label{sec:communication}
 \input{arch.communication}
 
-\section[Lifting mTasks to iTasks-Tasks]%
-	{Lifting \gls{mTask}-\glspl{Task} to \gls{iTasks}-\glspl{Task}}
-\input{arch.lift}
-
 \section{Example}
 \input{arch.example}