From 2138ff2d99e35b50afd224e4819556872f503c39 Mon Sep 17 00:00:00 2001 From: Robin Clark Date: Wed, 6 Oct 2010 09:08:19 +0100 Subject: [PATCH] . --- fmmd_design_aide/fmmd_design_aide.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fmmd_design_aide/fmmd_design_aide.tex b/fmmd_design_aide/fmmd_design_aide.tex index aa7582e..cbed15f 100644 --- a/fmmd_design_aide/fmmd_design_aide.tex +++ b/fmmd_design_aide/fmmd_design_aide.tex @@ -31,7 +31,7 @@ of its failure mode behaviour. A feature of FMMD analysis is symptom collection. Common symptoms are collected after analysis, and this means that the failure modes of the {\fg} are examined. The symptoms will be detectable (like a value of of range) -or undetectable (like a logic state of value being incorrect). +or undetectable (like a logic state or value being incorrect). The `undetectable' failure modes are the most worrying for thesafety critical designer. It is these that are, generally the ones that stand out as single failure modes. For instance, out of range values, we know we can cope with; they