Nov 17, 2022
diff --git a/benefit-handle-anomalies.md b/benefit-handle-anomalies.md

 In a statechart approach, failures are generally failures of background [activities](glossary/activity.html){:.glossary}.  When a background activity fails, a simple thing to do is to inform the statechart about the failure (by sending an [event](glossary/event.html){:.glossary} that describes the error), and describe _in the statechart_ how the failure should be handled, typically by introducing a new [transition](glossary/transition.html){:.glossary} to deal with the error.

 This simple act causes the error to be explicitly visible in the statechart, _and_therfore to the development team and other stakeholders.  It allows [QA teams to discover](benefit-qa-exploration-tool.html) that the error state exists, possibly prompting them to actually test this path.  It allows designers to design the error states [that have been uncovered](benefit-all-states-explored.html).
 This simple act causes the error to be explicitly visible in the statechart, _and_therefore to the development team and other stakeholders.  It allows [QA teams to discover](benefit-qa-exploration-tool.html) that the error state exists, possibly prompting them to actually test this path.  It allows designers to design the error states [that have been uncovered](benefit-all-states-explored.html).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -10,4 +10,4 @@ In a lot of bottom-up approaches, it is common to forego the error states: When

		In a statechart approach, failures are generally failures of background [activities](glossary/activity.html){:.glossary}. When a background activity fails, a simple thing to do is to inform the statechart about the failure (by sending an [event](glossary/event.html){:.glossary} that describes the error), and describe _in the statechart_ how the failure should be handled, typically by introducing a new [transition](glossary/transition.html){:.glossary} to deal with the error.

		This simple act causes the error to be explicitly visible in the statechart, _and_therfore to the development team and other stakeholders. It allows [QA teams to discover](benefit-qa-exploration-tool.html) that the error state exists, possibly prompting them to actually test this path. It allows designers to design the error states [that have been uncovered](benefit-all-states-explored.html).
		This simple act causes the error to be explicitly visible in the statechart, _and_therefore to the development team and other stakeholders. It allows [QA teams to discover](benefit-qa-exploration-tool.html) that the error state exists, possibly prompting them to actually test this path. It allows designers to design the error states [that have been uncovered](benefit-all-states-explored.html).