Capitalize Clang.

[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..b92430ba198363eea0e0b88cc9b0512ef1e1846d 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
@@ -181,7 +181,7 @@ know the LLVM community.
 
 LLVM has a pretty large amount of documentation, I spent most of my first
 weeks with reading tutorials and documents. Since there was already a (very
-preliminary) version of the clang-based frontend, I also had some code to play
+preliminary) version of the Clang-based frontend, I also had some code to play
 with.
 
 During this period, it was not completely clear what the frontend should