diff --git a/pub/proposal/proposal.pdf b/pub/proposal/proposal.pdf
index 50f8c95..b69806a 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 d4fc5b1..e835dbb 100644
--- a/pub/proposal/proposal.tex
+++ b/pub/proposal/proposal.tex
@@ -383,13 +383,28 @@ complement the coursework to be implemented. As a result, the
 prototype will enhance the poster and presentation.
 
 \subsection{Risks}
-\begin{itemize}
-\item Time management - that's why the last part of modelling is
-  done after the simulator connector as it's not essential,
-  can be done manually
-\item Simulator not being good enough?
-\item Simulator could be too complex to be able to link with model.
-\end{itemize}
+%\begin{itemize}
+%\item Time management - that's why the last part of modelling is
+%  done after the simulator connector as it's not essential,
+%  can be done manually
+%\item Simulator not being good enough?
+%\item Simulator could be too complex to be able to link with model.
+%\end{itemize}
+
+The main risk is time management, as falling too far behind could 
+be detrimental. However, to prevent falling behind, certain days 
+will be planned to include breaks, which is included in the plan,
+to prevent a burnout. Even if a burnout were to occur, there should be 
+enough spare time built up from the pessimistic deadlines to 
+prevent falling behind schedule. 
+
+There is also a small risk of the current home flight simulators not 
+being suitable to test the formal model, as their SDKs may not have 
+the tools necessary or the formal model may be too complex to connect to 
+the simulator. If this were to be the case, there could be other 
+another way to test, such as manually flying the plane in the simulator, 
+but recording data in the model manually, to provide feedback on the 
+checklist tests.
 
 % END OF 4 PAGE LIMIT %
 \clearpage