diff --git a/pub/proposal/proposal.pdf b/pub/proposal/proposal.pdf
index e405b08..ce1df50 100644
Binary files a/pub/proposal/proposal.pdf and b/pub/proposal/proposal.pdf differ
diff --git a/pub/proposal/proposal.tex b/pub/proposal/proposal.tex
index 8c22167..c2d1d8b 100644
--- a/pub/proposal/proposal.tex
+++ b/pub/proposal/proposal.tex
@@ -54,7 +54,7 @@
     \item Procedures in checklists must be tested in simulators~\cite{nasa-design},
       which usually means trained pilots test it, as the tests need
       to work consistently~\cite{manifesto} (making sure it's not lengthy,
-      concicse and gets critical procedures)
+      concise and gets critical procedures)
       	\lfcomment{Testing for what? What's the baseline? I guess you will need some kind of evidence/argument that demonstrates that with and without the checklist results are markedly different. }
     \item Checklists are usually carried out in high
         workload environments, especially emergency ones
@@ -85,7 +85,7 @@
       \begin{itemize}
         \item Can be done in an amount of time that will not endanger aircraft
         \item Provides reproducible results
-        \item Procedures will not endanger aircraft or crew further (Crew refering to Checklist Manifesto with the cargo door blowout)
+        \item Procedures will not endanger aircraft or crew further (Crew referring to Checklist Manifesto with the cargo door blowout)
       \end{itemize}
       \lfcomment{Again, explain testing against what}
     \item Results in being able to see where to improve checklists
@@ -134,7 +134,9 @@
 \section{Aims and Objectives}
 \subsection*{Aims}
 \begin{enumerate}
-    \item Test Checklists
+    \item Test Checklists for flaws that can compromise the
+      aircraft or that the checklist will not take too long
+      and overload pilot further
     \item Test multiple conditions for that checklist
     \item Find problems in the checklist
     \item Find how reproducible the checklist is