diff --git a/submission_thesis/CH8_Conclusion/copy.tex b/submission_thesis/CH8_Conclusion/copy.tex
index ee21466..2155bd6 100644
--- a/submission_thesis/CH8_Conclusion/copy.tex
+++ b/submission_thesis/CH8_Conclusion/copy.tex
@@ -376,13 +376,13 @@ If we require FMMD to produce full FTA diagrams, we need to add these
 attributes to the FMMD UML model\footnote{Top down failure mode models, such as FTA, are additionally 
 useful in guiding diagnostic analysis.}.
 \fmmdglossINHIBIT
-
+%
 \paragraph{Environment, operational states and inhibit gates: additions to the UML model.}
-
+%
 FTA, in addition to using symbols borrowed from digital logic introduces three new symbols to   
 model environmental, operational state and inhibit gates; % we discuss here 
 how these can be incorporated into the FMMD model is discussed below.
-
+%
 A  system will be expected to perform in a given environment.
 %
 Environment in the context of this study
@@ -488,11 +488,11 @@ are added to  UML diagram in figure \ref{fig:cfg} are represented in figure \ref
 
 \clearpage
 
-\subsection{Retrospective Failure Mode analysis and FMMD}
+\subsection{Retrospective failure mode analysis and FMMD}
 
 The reasons for applying retrospective failure mode analysis could be:
 \begin{itemize}
- \item approving previously un-assessed systems to a safety standard,
+ %\item approving previously un-assessed systems to a safety standard,
  \item to re-visit a safety analysis after a small h/w or s/w change,
  \item upon discovery of a new {\bc} {\fm},
  \item or to determine  the failure mode behaviour of an previously un-assessed instrument used in safety critical verification.
@@ -516,7 +516,7 @@ failure modes.
 %come to light.
 %
 %
-\paragraph{Retrospective Failure Mode analysis and software.}
+\paragraph{Retrospective failure mode analysis and software.}
 %
 We can apply retrospective FMMD to electronic and software hybrid systems as well.
 %