X-Git-Url: https://git.stderr.nl/gitweb?p=matthijs%2Fprojects%2Finternship.git;a=blobdiff_plain;f=Report%2FMain%2FProblems%2FChallenges.tex;h=39806fae30510fa7f35b4f5904c97cdcf14c37d3;hp=06bd72c81ea6b46321b91c6efc8f8b41ed856b16;hb=bda4ad2a7baf347f8bb7239ae998088a6987b73b;hpb=b8ed8189b345f81d7a91535959b3776593062535

diff --git a/Report/Main/Problems/Challenges.tex b/Report/Main/Problems/Challenges.tex
index 06bd72c..39806fa 100644
--- a/Report/Main/Problems/Challenges.tex
+++ b/Report/Main/Problems/Challenges.tex
@@ -1,13 +1,13 @@
 \section{Challenges and Solutions}
-This section will describe the challenges faced during each of the tasks and the
-solutions found for both the task itself and the challenges.
+This section will describe the challenges faced during the work I have performed
+and the solutions found for both the task itself and the challenges.
 
 \subsection{What is MontiumC?}
-A critical question popped up during at the beginning of my internship: What is
+A critical question popped up at the beginning of my internship: What is
 MontiumC? Previously, there was no real specification of MontiumC. There was
 documentation about the functions that could be used, some examples and a lot of
 personal knowledge in the heads of the Recore employees, but ultimately MontiumC
-was "whatever the compiler eats".
+was ``whatever the compiler eats''.
 
 To be able to create a proper set of transformations, the constraints on the
 input and output of that transformation process should be properly specified.