-The system provides a framework of functions with
-which an \gls{iTasks}-system can add, change and remove devices at runtime.
-Moreover, the \gls{iTasks}-system can send \gls{mTask}-\glspl{Task} ---
-compiled at runtime to bytecode by the \gls{mTask}-view --- to the device. The
-device runs an interpreter which executes the \gls{Task}'s bytecode following
-the scheduling strategy given. 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
-methods of interacting with \gls{mTask}-\gls{Task} is analogous to interacting
-with \gls{iTasks}-\glspl{Task}. This means that programmers can access the
+The system provides a framework of functions with which an \gls{iTasks}-system
+can add, change and remove devices at runtime. Moreover, the
+\gls{iTasks}-system can send \gls{mTask}-\glspl{Task} --- compiled at runtime
+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}-\glspl{Task} is analogous to interacting with
+\gls{iTasks}-\glspl{Task}. This means that programmers can access the