X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=introduction.tex;h=9243d2ad19e615b5b17a8cf6f3d361f71f7ceaac;hb=62adc41f28fb8baaa8e1a40d8806b06069d641ed;hp=64cdc92294a6ff809f081e2b213e464a1d1e8349;hpb=7d430f47a575566d56625b3e8641fb78171a1f08;p=msc-thesis1617.git

diff --git a/introduction.tex b/introduction.tex
index 64cdc92..9243d2a 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -39,7 +39,7 @@ such as time are available in the current \gls{iTasks} implementation.}.
 However, this requires a very specific adapter to be written for every device
 and function.  This forces a fixed logic in the device that is set at compile
 time. Many small \gls{IoT} devices have limited processing power but are still
-powerfull enough for decision making. Recompiling the code for a small
+powerful enough for decision making. Recompiling the code for a small
 \gls{IoT} device is expensive and therefore it is difficult to use a device
 dynamically for multiple purposes. Oortgiese et al.\ lifted \gls{iTasks} from a
 single server model to a distributed server architecture that is also runnable
@@ -74,8 +74,8 @@ Chapter~\ref{chp:dsl} discusses the pros and cons of different embedding
 methods to create \gls{EDSL}.
 Chapter~\ref{chp:mtask} shows the existing \gls{mTask}-\gls{EDSL} on which is
 extended upon in this dissertation.
-Chapter~\ref{chp:mtaskcont} shows the extension added to the
-\gls{mTask}-\gls{EDSL} that were needed to make the system function.
+Chapter~\ref{chp:mtaskcont} describes the view and functionality for
+the \gls{mTask}-\gls{EDSL} that were added and used in the system.
 Chapter~\ref{chp:arch} shows the architecture used for \gls{IoT}-devices that
 are a part of the new \gls{mTask}-system. It covers the client software running
 on the device and the server written in \gls{iTasks}.
@@ -141,6 +141,6 @@ is deeply embedded but the type system is shallowly embedded. This requires
 several \gls{Haskell} extensions that offer dependent type constructions. The
 process of compiling an \gls{Ivory} program happens in stages. The embedded
 code is transformed into an \gls{AST} that is sent to a backend. In the new
-system, the \gls{mTask} \gls{EDSL} transforms the embedded code during
+system, the \gls{mTask}-\gls{EDSL} transforms the embedded code during
 compile-time directly into the backend which is often a state transformer that
 will execute on runtime.