summaryrefslogtreecommitdiff
path: root/paper/eval.tex
diff options
context:
space:
mode:
Diffstat (limited to 'paper/eval.tex')
-rw-r--r--paper/eval.tex4
1 files changed, 2 insertions, 2 deletions
diff --git a/paper/eval.tex b/paper/eval.tex
index 969a82d..36ff225 100644
--- a/paper/eval.tex
+++ b/paper/eval.tex
@@ -21,7 +21,7 @@ looking up the variable in the state fails, a \CI{Left Error} will be returned.
The last case is more interesting, however. Here, we use bind (\CI{>>=}) to
simulate exception handling: the two evaluations of \CI{a1} and \CI{a2} may
fail, as may the application of the operator to its two arguments. Even though
-we don't know at this point \emph{why} or \emph{where} the evaluation failed,
+we do not know at this point \emph{why} or \emph{where} the evaluation failed,
\CI{>>=} will conveniently pass through any errors.
The abstraction of monad binding allows us to work with data or errors, without
@@ -42,7 +42,7 @@ to model it as a lookup table:
:: State :== [(Var, Int)]
\end{lstlisting}
-While possible, this has several drawbacks. First of all, we would need a
+Though possible, this has several drawbacks. First of all, we would need a
separate function to look up a variable in this store. We could implement that
function as follows: