X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=introduction.tex;h=8d5de43aa9d43a9a7abbca85f226c5577b0aa32e;hb=66de2590bcb4046b92ea54bcd3e55b38208be17b;hp=62bbb9f716323ee7deaa8167908d0c907028d432;hpb=76254fbf2941fa0b5a02ab3a98104cad56959218;p=msc-thesis1617.git

diff --git a/introduction.tex b/introduction.tex
index 62bbb9f..8d5de43 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -24,7 +24,7 @@ like sequence, parallel and conditional \glspl{Task} can be modelled using
 combinators.
 
 \gls{iTasks} has been proven to be useful in many fields of operation such as
-incident management~~\cite{lijnse_top_2013}. Interfaces are automatically
+incident management~\cite{lijnse_top_2013}. Interfaces are automatically
 generated for the types of data which makes rapid development possible.
 \Glspl{Task} in the \gls{iTasks} system are modelled after real life workflow
 tasks but the modelling is applied on a very high level. Therefore it is
@@ -42,7 +42,7 @@ This forces a fixed logic in the device that is set at compile time. Many
 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 small
-devices such as those powered by \acrshort{ARM}~~\cite{%
+devices such as those powered by \acrshort{ARM}~\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 have only \gls{LTN} communication with low bandwidth