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=8bc81f57fcf25bcba6ab7e295063523e1340bfe5;hp=3246baba351fe8d58ca9987fb3383175fb5a855e;hb=28976641f199e6c3ad3a17aa82cbb87b0e31a9d0;hpb=90643309f86996e21c5b287ab0cfedb04ce020ce

diff --git a/Report/Main/Future.tex b/Report/Main/Future.tex
index 3246bab..8bc81f5 100644
--- a/Report/Main/Future.tex
+++ b/Report/Main/Future.tex
@@ -32,8 +32,8 @@ more invasive changes to LLVM.
 
 These changes are generic for LLVM and not needed specifically for the Montium.
 Currently, most MontiumC code seems to still work with only a little
-change to LLVM, but especially with the new hardware, some missed out
-optimizations might become more useful.
+change to LLVM, but especially with the new hardware, these missed
+optimizations might become more of problem.
 
 \section{LLVM based backend}
 Currently, the frontend is using the LLVM framework, while the backend is
@@ -46,9 +46,9 @@ 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
 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 code than
-the old Montium, though. Also, the added work of migrating to a new framework
-and new language is also a extra cost.
+more. The new hardware design might be a lot more suitable for reusing LLVM code than
+the old Montium, however. Also, the added work of migrating to a new framework
+and new language is also an extra cost.
 
 Currently, doing this might or might not be a good idea. What is required first,
 is doing a more in-depth investigation of the LLVM backend framework (which is,