X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=conclusion.tex;h=94b75ff57c87dcd9a57accc8340b9fe51a4b251d;hb=7694dfaa240c6dd9af2f1ac8880f0fb1d7f38324;hp=de3da6ce210e7047e0616ad992731731c1dfe517;hpb=d11a7941da4024ec8ff9ef6afaebb6eb9d2c6ed4;p=msc-thesis1617.git

diff --git a/conclusion.tex b/conclusion.tex
index de3da6c..94b75ff 100644
--- a/conclusion.tex
+++ b/conclusion.tex
@@ -25,7 +25,7 @@ broken device without needing to recompile the code.
 
 \section{Discussion}
 \todo{class based shallow doesn't have multiple backend support}
-\todo{slow client software because of intepretation}
+\todo{slow client software because of interpretation}
 \todo{What happens if a device dies? Task resending, add to handshake}
 
 
@@ -56,6 +56,8 @@ of the client software. However, it could be implemented as a compile-time
 option and exchanged during the handshake so that the server knows the
 multithreading capabilities of the client.
 
+\todo{Parametric lenses on devices share?}
+
 \subsection{Resources}
 Resource analysis during compilation can be useful to determine if an
 \gls{mTask}-\gls{Task} is suitable for a specific device. If the device does
@@ -65,7 +67,7 @@ given.
 
 This idea could be extended to the analysis of stack size and possibly
 communication bandwidth. With this functionality ever more reliable fail-over
-systems can be designed. When the system knows more precise bounds it can
+systems can be designed. When the system knows preciser bounds it can
 allocate more \glspl{Task} on a device whilst staying within safe memory
 bounds. The resource allocation can be done at runtime within the backend
 itself or a general backend can be devices that can calculate the resources