uml/state-machine-diagram.md

@@ -8,7 +8,7 @@ This kind of diagram can be greatly used to get a detailed understanding of the
 For example, you can use it in the early design phase of a new software system to model the behavior of a specific component to describe it's workflow. Especially, when the behavior of an object (lifecycle) or operation is not well understood yet.
 
 # Obligations for the lectures and the final exam in "Softwaretechnik" (Tips for Modeling)
-When creating a **state machine diagram**, remember that it must contain all necessary information (states, activities, actions, transitions, events, guards, and triggers). Otherwise this type of diagram is useless and can be thrown away. Especially for transitions between states it is important to specify the relevant events, guards, and triggers.
+When creating a **state machine diagram**, remember that it must contain all necessary information (states, activities, actions, transitions, events, guards, and triggers). Otherwise this type of diagram is useless and can be thrown away. Especially for transitions between states it is important to specify the relevant triggers, guards, and behaviors.
 An example class diagram is shown in [Example State Machine Diagram](#an-example-state-machine-diagram-for-the-given-scenario).
 
 # What is a State?