add glue chapter

[msc-thesis1617.git] / mtaskext.tasksem.tex

diff --git a/mtaskext.tasksem.tex b/mtaskext.tasksem.tex
index 470a257..040e461 100644 (file)
--- a/mtaskext.tasksem.tex
+++ b/mtaskext.tasksem.tex
@@ -3,16 +3,15 @@ sense that the \gls{C}-view does. \Glspl{Task} used with the \gls{C}-view are a
 main program that executes code and launches \glspl{Task}. It was also possible
 to just have a main program. The current \gls{mTask}-system only supports main
 programs. Sending a \gls{Task} always goes together with choosing a scheduling
-strategy. This strategy can be one of the following three strategies as
-reflected in the \CI{MTTask} message type.
+strategy. This strategy can be one of the following three strategies:
 
 \begin{itemize}
        \item\CI{OneShot}
 
                \CI{OneShot} takes no parameters and means that the \gls{Task} will run
                once and will then be removed automatically. This type of scheduling
-               could be useful, for example, in retrieving sensor information on
-               request of a user.
+               is useful, for example, in retrieving sensor information on request of
+               the user.
        \item\CI{OnInterval}
 
                \CI{OnInterval} has the number of milliseconds to wait in between