diff --git a/submission_thesis/CH5_Examples/software.tex b/submission_thesis/CH5_Examples/software.tex
index aaae1b6..f148e46 100644
--- a/submission_thesis/CH5_Examples/software.tex
+++ b/submission_thesis/CH5_Examples/software.tex
@@ -106,11 +106,11 @@ In this analogy the connections are the code, and the functions and variables ar
 If we consider the 
 calls and variables/inputs to be components of a function,
 %
-any erroneous behaviour from them has the same effect as component failure mode
+any erroneous behaviour from them has the same effect as component failure modes
 on an electronic {\fg}. %HHmmm HHHHMMMM XXXXXX gora den har nar dets finns into nagon some harker hela tiden
 %
-For a software function, a violation of a pre-condition is 
-in effect a failure mode of `one of its components'.
+For a software function, we consider a violation of a pre-condition to be
+equivalent to failure mode of `one of its components'.
 
 
 \paragraph{Mapping contract `post-condition' violations to symptoms.}