diff --git a/certainty.tex b/certainty.tex
index 144e23b..ee77fed 100644
--- a/certainty.tex
+++ b/certainty.tex
@@ -12,8 +12,6 @@ variety of different adaptation patterns.
 
 \subsection{Evaluating Alternatives}
 
-% 24 Dec 2014 : GWA : TODO : Trim.
-
 The optional \texttt{evaluate} block of a \texttt{maybe} statement allows
 programmers to provide app-specific \textit{a posteriori} evaluation logic.
 However, in many cases, we expect that \texttt{maybe} statements will be used
diff --git a/discussion.tex b/discussion.tex
index 06ebfe0..b0c683c 100644
--- a/discussion.tex
+++ b/discussion.tex
@@ -1,5 +1,3 @@
-% 24 Dec 2014 : GWA : TODO : Trim.
-
 \section{Discussion}
 \label{sec-discussion}
 
diff --git a/related.tex b/related.tex
index d979f7c..d172843 100644
--- a/related.tex
+++ b/related.tex
@@ -14,7 +14,7 @@ computation should be performed. Fundamentally, the goals of AOP and the
 \texttt{maybe} statement differ, with AOP focusing on modularity and
 \texttt{maybe} focused on enabling adaptation by expressing uncertainty.
 
-\texttt{maybe} shares similaries with language-based approaches to adapting
+\texttt{maybe} shares similarities with language-based approaches to adapting
 energy consumption such as Eon~\cite{sensys07-eon} and
 Levels~\cite{sensys07-levels}. However, these approaches still require
 programmers to express certainty by associating code with energy states,