diff --git a/submission_thesis/CH5_Examples/context_calltree.dia b/submission_thesis/CH5_Examples/context_calltree.dia
index dc6eac6..20e146c 100644
Binary files a/submission_thesis/CH5_Examples/context_calltree.dia and b/submission_thesis/CH5_Examples/context_calltree.dia differ
diff --git a/submission_thesis/CH5_Examples/context_diagram2_PID.dia b/submission_thesis/CH5_Examples/context_diagram2_PID.dia
index f24ca9f..eb3023a 100644
Binary files a/submission_thesis/CH5_Examples/context_diagram2_PID.dia and b/submission_thesis/CH5_Examples/context_diagram2_PID.dia differ
diff --git a/submission_thesis/CH5_Examples/context_software.dia b/submission_thesis/CH5_Examples/context_software.dia
index 1f92add..785d9c4 100644
Binary files a/submission_thesis/CH5_Examples/context_software.dia and b/submission_thesis/CH5_Examples/context_software.dia differ
diff --git a/submission_thesis/CH5_Examples/software.tex b/submission_thesis/CH5_Examples/software.tex
index b537592..aaae1b6 100644
--- a/submission_thesis/CH5_Examples/software.tex
+++ b/submission_thesis/CH5_Examples/software.tex
@@ -84,7 +84,7 @@ and traceable way. Each function is subject to pre-conditions (constraints on it
 post-conditions (constraints on its outputs) and function wide invariants (rules).
 
 
-\paragraph{Mapping contract `pre-condition' violations to failure modes.}
+\paragraph{Mapping contract `pre-condition' violations to component failure modes.}
 
 A precondition, or requirement for a contract software function
 defines the correct ranges of input conditions for the function
@@ -92,12 +92,22 @@ to operate successfully.
 %
 % C Garret said this was unclear so I have added the following two sentences.
 %
-If we consider a software function to be a {\fg} in the FMMD sense,
-we see that it is can be considered to be a collection of functions that it
-calls and variables/inputs that it uses.
+%If we consider a software function to be a {\fg} in the FMMD sense, i.e.
+We can consider a software function to be 
+a collection of code, functions called and values/variables used.
+In this way it is similar to an electronic circuit, which is a collection
+of components connected in a specific way.
+In this analogy the connections are the code, and the functions and variables are the components.
 %
-If we consider these functions and inputs to be its components,
-any erroneous behaviour from them can be considered to be a component failure mode.
+%EHHRHHHUH
+%EERRGHHH COUGH COUGH
+%
+%
+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
+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'.