diff --git a/mybib.bib b/mybib.bib
index d886fcb..41f26fa 100644
--- a/mybib.bib
+++ b/mybib.bib
@@ -128,11 +128,11 @@ Database
 	number = "",
 	pages = "",
 	year = "2011",
-	note = "6th IET International Conference on System Safety, 2011",
+	note = "",
 	issn = "",
 	doi = "",
 	url = "",
-	author = "R.P. Clark et all",
+	author = "R. Clark and A. Fish and C. Garret and J. Howse",
 	keywords = "Failsafe",
 	keywords = "EN298",
 	keywords = "gas-safety",
diff --git a/papers/fmmd_software_hardware/software_fmmd.tex b/papers/fmmd_software_hardware/software_fmmd.tex
index 8a7d310..3aa5a92 100644
--- a/papers/fmmd_software_hardware/software_fmmd.tex
+++ b/papers/fmmd_software_hardware/software_fmmd.tex
@@ -777,8 +777,7 @@ With these failure modes, we can analyse our first functional group, see table~\
                                 &   voltage on pin high         &                 \\ \hline 
 
      2: $R_{SHORT}$               &  resistor shorted,         &    $LOW$          \\ 
-                                   &   voltage on pin low         &                   \\   \hline \hline 
-
+                                   &   voltage on pin low         &                   \\   \hline  
 
  
      3: $ADC_{STUCKAT}$            &  ADC reads out         &      $V\_ERR$          \\   
@@ -1070,7 +1069,7 @@ re-use this analysis for each {\ft} input in the system.
 %
 %A software specification for a hardware interface will concentrate on
 %how to interpret raw readings, or what signals to apply for actuators.
-Additionally, using FMMD we  can determine a failure model for the hardware/software interface. % interface as well.
+Additionally, using FMMD we can determine a failure model for the hardware/software interface. % interface as well.
 
 %Its solved. Hoooo-ray !!!!!!!!!!!!!!!!!!!!!!!!