X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=arch.tex;h=1fd4d4fc7afef0dfae53f4b5bc47067520ed5f57;hb=9f46d86ae967438d41ace2e74da7cee6898015b9;hp=e1ae60816296bce5280121a6b679e6b17cbc123a;hpb=b8953a28b8a7db87f446bc74a6e6f854e19cd639;p=msc-thesis1617.git

diff --git a/arch.tex b/arch.tex
index e1ae608..1fd4d4f 100644
--- a/arch.tex
+++ b/arch.tex
@@ -6,7 +6,7 @@ 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
+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
@@ -21,9 +21,5 @@ normal \gls{iTasks}-\glspl{Task}.
 \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}