diff --git a/component_failure_modes_definition/component_failure_modes_definition.tex b/component_failure_modes_definition/component_failure_modes_definition.tex
index 58022dd..e4433b8 100644
--- a/component_failure_modes_definition/component_failure_modes_definition.tex
+++ b/component_failure_modes_definition/component_failure_modes_definition.tex
@@ -754,11 +754,18 @@ Consider for instance an electrical circuit that has a TEST line.
 When the TEST line is activated, it supplies a test signal
 which will validate the circuit. This circuit will have two operational states,
 NORMAL and TEST mode.
-
 It is natural to apply the operational states to functional groups.
 Functional groups by definition implement functionality, or purpose
 of particular sub-systems, and therefore are the best objects to model
 operational states.
+\paragraph{Inhibit Conditions}
+Some failure modes may only be active given specific environmental conditions
+or when other failures are already active.
+To model this, an `inhibit' class has been added.
+This is an optional atribute of 
+a failure mode. This inhibit class can be triggered
+on a combination of environmental or failure modes.
+
 
 \paragraph{UML Diagram Additional Objects.}
 The additional objects System, Environment and Operational States
@@ -768,7 +775,7 @@ are added to  UML diagram in figure \ref{fig:cfg} and represented in figure \ref
 
 \begin{figure}[h]
  \centering
- \includegraphics[width=400pt,keepaspectratio=true]{./component_failure_modes_definition/cfg2.jpg}
+ \includegraphics[width=400pt,keepaspectratio=true]{./master_uml.jpg}
  % cfg2.jpg: 702x464 pixel, 72dpi, 24.76x16.37 cm, bb=0 0 702 464
  \caption{Complete UML diagram}
  \label{fig:cfg2}