-adapter to be written for every device and functionality. Oortgiese et al.\
-lifted \gls{iTasks} from a single server model to a distributed server
-architecture~\cite{oortgiese_distributed_2017} that is also runnable on smaller
-devices like \acrshort{ARM}. However, this is limited to fairly high
-performance devices that are equipped with high speed communication lines.
-Devices in \gls{IoT} often only have \gls{LTN} communication with low bandwidth
-and a very limited amount of processing power. \glspl{mTask} will bridge this
-gap. It can run on devices as small as Arduino microcontrollers and operates
-via the same paradigms as regular \glspl{Task}. The \glspl{mTask} have access
-to \glspl{SDS} and can run small imperative programs.
+adapter to be written for every device and functionality. However, this forces
+a fixed logic in the device that is set at compile time. A lot of the small
+\gls{IoT} devices have limited processing power but can still contain decision
+making. Oortgiese et al.\ lifted \gls{iTasks} from a single server model to a
+distributed server architecture that is also runnable on smaller devices like
+\acrshort{ARM} devices\cite{oortgiese_distributed_2017}. However, this is
+limited to fairly high performance devices that are equipped with high speed
+communication channels. Devices in \gls{IoT} often only have \gls{LTN}
+communication with low bandwidth and a very limited amount of processing power
+and are therefore not suitable to run an entire \gls{iTasks} core.
+
+\glspl{mTask} will bridge this gap by introducing a new communication protocol,
+device application and \glspl{Task} synchronizing the formers.
+The system can run on devices as small as Arduino microcontrollers and
+operates via the same paradigms and patterns as regular \glspl{Task}.
+\glspl{mTask} can run small imperative programs written in a \gls{EDSL} and
+have access to \glspl{SDS}. In this way \glspl{Task} can be sent to the device
+at runtime and information can be exchanged.