X-Git-Url: https://git.stderr.nl/gitweb?p=matthijs%2Fprojects%2Finternship.git;a=blobdiff_plain;f=Report%2FMain%2FFuture.tex;fp=Report%2FMain%2FFuture.tex;h=bfa737accb7e30a22689615182c1722cbfaf188d;hp=8bc81f57fcf25bcba6ab7e295063523e1340bfe5;hb=0ac3f8b7cfb60e71b9f95dc8bf1752e1e971685f;hpb=1ae051d27cb9debbfa570ac82846c8a8d86287f2

diff --git a/Report/Main/Future.tex b/Report/Main/Future.tex
index 8bc81f5..bfa737a 100644
--- a/Report/Main/Future.tex
+++ b/Report/Main/Future.tex
@@ -1,6 +1,7 @@
 \chapter{Future work}
 \label{FutureWork}
-This chapter will describe outstanding tasks and issues.
+This chapter will describe tasks for the future and issues that remain
+to be resolved.
 
 \section{Verifiers}
 Currently, when faulty MontiumC is written, this will be detected very late in
@@ -43,7 +44,7 @@ backend would benefit from being able to use existing LLVM code and passes,
 utility code, etc. Also, this would enable the compiler to become a single
 binary executable, instead of having a seperate executable and a Java program.
 
-However, the main risk here is when the LLVM framework turns out to be not fully
+However, the main risk here is that the LLVM framework might turn out to be not fully
 suitable for the Montium backend. When nothing can be reused, the amount of code
 needed is not any less, and if the framework poses limitations, might even be
 more. The new hardware design might be a lot more suitable for reusing LLVM code than