diff --git a/papers/fmea_software_hardware/software_fmea.tex b/papers/fmea_software_hardware/software_fmea.tex
index 6b555cc..ec75a85 100644
--- a/papers/fmea_software_hardware/software_fmea.tex
+++ b/papers/fmea_software_hardware/software_fmea.tex
@@ -556,7 +556,7 @@ the multiplexer and the analogue to digital converter.
 The last two failures both lead to the system failure of  $VAL\_ERROR$ .
 They could lead to low or high reading as well, but we would only be able to determine this
 from knowledge of the software systems criteria for these.
-\clearpage
+%\clearpage
 \subsection{Software FMEA - variables in place of components}
 
 For software FMEA, we take the variables used by the system,
@@ -613,7 +613,7 @@ We must now determine putative system failure modes for these variables becoming
 \end{tabular}
 \end{table} 
 }
-\clearpage
+%\clearpage
 \subsection{Software FMEA - failure modes of the medium ($\mu P$) of the software}
 
 Microprocessors/Microcontrollers have sets of known failure modes, these include RAM, ROM
@@ -658,7 +658,7 @@ oscillator clock timing
 \end{table} 
 }
 
-\clearpage
+%\clearpage
 \subsection{Software FMEA - The software/hardware interface}
 
 As FMEA is applied separately to software and hardware