Put spaces in example and definition labels.

[matthijs/master-project/report.git] / Chapters / Context.tex

diff --git a/Chapters/Context.tex b/Chapters/Context.tex
index 7e620a073e3cd648459b274e23d7543ea5283c9b..7c256da703a056ddad87c6901c7ad34b070c1fe7 100644 (file)
--- a/Chapters/Context.tex
+++ b/Chapters/Context.tex
@@ -40,15 +40,15 @@
   this not been done before?}. Using a functional language for describing hardware
   is not a new idea at all. In fact, there has been research into functional
   hardware description even before the conventional hardware description
-  languages were created. Examples of these are µFP \cite[sheeran83] and
+  languages were created. Examples of these are µFP \cite[sheeran83]\ and
   Ruby \cite[jones90]. Functional languages were not nearly as advanced
   as they are now, and functional hardware description never really got
   off. 
 
   Recently, there have been some renewed efforts, especially using the
-  Haskell functional language. Examples are Lava \cite[claessen00] (an
-  \small{EDSL}) and ForSyde \cite[sander04] (an \small{EDSL} using
-  Template Haskell). \cite[baaij09] has a more complete overview of the
+  Haskell functional language. Examples are Lava \cite[claessen00]\ (an
+  \small{EDSL}) and ForSyde \cite[sander04]\ (an \small{EDSL} using
+  Template Haskell). \cite[baaij09]\ has a more complete overview of the
   current field.
 
   We will now have a look at the existing hardware description languages,
@@ -80,7 +80,7 @@
     embedded functional hardware description languages (in particular
     those using Haskell) are limited. Below a number of downsides are
     sketched of the recent attempts using the Haskell language.
-    \cite[baaij09] has a more complete overview of these and other
+    \cite[baaij09]\ has a more complete overview of these and other
     languages.
     
     This list uses Lava and ForSyDe as examples, but tries to generalize