diff --git a/symptom_ex_process/abstract.tex b/symptom_ex_process/abstract.tex
index ac93d95..aeb2a7a 100644
--- a/symptom_ex_process/abstract.tex
+++ b/symptom_ex_process/abstract.tex
@@ -21,7 +21,7 @@ its components.
 Once the failure modes have been determined for a sub-system,
 we can consider this to be a `derived component'
 which can be combined with others to form
-to model higher level sub-systems, which in turn can
+higher level sub-systems, which in turn can
 be converted to derived components. 
 In this way a hierarchy representing the fault behaviour
 of a system can be built from the bottom~up. 
diff --git a/symptom_ex_process/fmmd.tex b/symptom_ex_process/fmmd.tex
index add268d..748445b 100644
--- a/symptom_ex_process/fmmd.tex
+++ b/symptom_ex_process/fmmd.tex
@@ -6,8 +6,11 @@
 The symptom abstraction process described here, is a core process in the 
 %Failure Mode Modular De-Composition 
 FMMD modelling technique. FMMD builds a hierarchy of failure mode behaviours from the bottom up.
-To start with collections of base components are grouped into functional~groups, which are analysed
-and then treated as components in thier own right. These higher level, or derived compoenents,
+To start with collections of base components are chosen to form functional~groups, which are analysed
+w.r.t. its failure mode behaviour.
+These functional groups
+can then be treated as a components in their own right.
+These higher level, or derived compoenents,
 can be used to build derived components at higher levels of abstraction, and ultimately
 are used to build an FMMD fault model hierarchy of the system modelled.
 Intermediate FMMD structures may be re-used in other designs, and 
diff --git a/symptom_ex_process/symptom_ex_process.tex b/symptom_ex_process/symptom_ex_process.tex
index e24e69e..99ff19a 100644
--- a/symptom_ex_process/symptom_ex_process.tex
+++ b/symptom_ex_process/symptom_ex_process.tex
@@ -5,7 +5,7 @@
 \input{fmmd}
 %\input{introduction}
 \input{topbot}
-\input{sys_abs}
+%\input{sys_abs}
 \input{process}
 \input{algorithm}
 
@@ -13,7 +13,7 @@
 {
 \input{./symptom_ex_process/introduction}
 \input{./symptom_ex_process/topbot}
-\input{./symptom_ex_process/sys_abs}
+%\input{./symptom_ex_process/sys_abs}
 \input{./symptom_ex_process/process}
 \input{./symptom_ex_process/algorithm}
 }
diff --git a/symptom_ex_process/topbot.tex b/symptom_ex_process/topbot.tex
index 8f65f67..c8611b5 100644
--- a/symptom_ex_process/topbot.tex
+++ b/symptom_ex_process/topbot.tex
@@ -12,12 +12,12 @@ Static testing is also applied. This is theoretical analysis of the design of th
 perspective.
 Three main techniques are currently used,
 Statistical failure models, FMEA (Failure mode Effects Analysis) and FTA (Fault Tree Analysis).
-The FMMD technique is aimed primarily as design verification for
+The FMMD technique is a static modelling methodology, aimed primarily as design verification for
 safety critical systems.
 However, FMMD  also provides the mathematical frame work
-to assist in the production of these three results of static analysis.
-From the model created by the FMMD technique, the three  above failure mode
-descriptions can be derived.
+to assist in the production of the three traditional methods of static analysis.
+From the model created by the FMMD technique, statistical, FTA and FMEA models
+can be derived.
 FMMD can model electrical, mechanical and software using a common notation,
 and can thus model an entire electro mechanical software controlled system.
 
@@ -90,7 +90,7 @@ for each `component'.
 
 If we look at the sound system example, 
 the CD~player could fail in several distinct ways, 
-and this couldbe due to a large number of
+and this could be due to a large number of
 component failure modes.
 %no matter what has happened to it or has gone wrong inside it.
 
@@ -115,8 +115,8 @@ to perform a specific function.
 
 When we have analysed the fault behaviour of a functional group, we can treat it as a `black box'.
 The fault behaviour will consist of a set of `symptoms' caused by combinations
-of the component failure modes.
-We can make a new `component' derived from the functional~group.
+of its component failure modes.
+We can thus make a new `component' derived from the functional~group.
 The symptoms are the failure modes of this new `derived component'.
 
 %We can now call our functional~group a sub-system or a derived~component.