process comments

[phd-thesis.git] / top / int.tex

diff --git a/top/int.tex b/top/int.tex
index 20df4f8..209c48e 100644 (file)
--- a/top/int.tex
+++ b/top/int.tex
@@ -10,7 +10,7 @@
 \chapter{The integration of mTask and iTask}%
 \label{chp:integration_with_itask}
 \begin{chapterabstract}
-       This chapter shows the integration of \gls{MTASK} and \gls{ITASK} by showing:
+       This chapter shows the integration of \gls{MTASK} and \gls{ITASK} by discussing:
        \begin{itemize}
                \item an architectural overview of \gls{MTASK} applications;
                \item the interface for connecting devices;
@@ -29,7 +29,7 @@ Devices in the \gls{MTASK} system are set up with a domain-specific \gls{OS} and
 
 \Cref{fig:mtask_integration} shows the architectural layout of a typical \gls{IOT} system created with \gls{ITASK} and \gls{MTASK}.
 The entire system is written as a single \gls{CLEAN} specification where multiple tasks are executed at the same time.
-Tasks can access \glspl{SDS} according to many-to-many communication and multiple clients can work on the same task.
+Tasks can access \glspl{SDS} following the many-to-many communication pattern and multiple clients can work on the same task.
 The diagram contains three labelled arrows that denote the integration functions between \gls{ITASK} and \gls{MTASK}.
 Devices are connected to the system using the \cleaninline{withDevice} function (see \cref{sec:withdevice}).
 There can be multiple devices connected to a single \gls{ITASK} host at the same time.