Cosmetic fixes.

[matthijs/projects/internship.git] / Report / Main / Problems / Challenges.tex

diff --git a/Report/Main/Problems/Challenges.tex b/Report/Main/Problems/Challenges.tex
index d5bc0145919f7f1d4f3de0b8a2159587d8259f7c..982397a8a2ed8aa802d64a574837e11ffb16db4b 100644 (file)
--- a/Report/Main/Problems/Challenges.tex
+++ b/Report/Main/Problems/Challenges.tex
@@ -33,7 +33,7 @@ makes use of corner cases in the compiler that have been missed in (or left out
 of) the specification, because they will not work reliably in all cases.
 
 The best way to detect these cases is making the compiler check its input using
-an the specification. This way, any code operating outside of the specification
+the specification. This way, any code operating outside of the specification
 can be detected automatically. Writing such checks has not happened yet, mainly
 because the impact of the new hardware on MontiumC is not quite clear yet.
 
@@ -100,7 +100,7 @@ lot of instructions. Second, the code is effectively software pipelined
 to make it run more efficiently.
 
 In figure \ref{ExampleHigh} the same code is displayed, but this time
-using higer level C features (for loops, arra indexing). This is the
+using higer level C features (for loops, array indexing). This is the
 level of code we are trying to achieve, but we're not there yet. It
 should be noted that this is still not "normal" C, since we use the
 "imul" function instead of the normal * operator. However, since the