Merge remote-tracking branches 'svenja/patch-3', 'svenja/patch-4', 'svenja/patch-5', 'svenja/patch-6', 'svenja/patch-7', 'svenja/patch-8' and 'svenja/patch-9' into statechart_vs_state_machine

plugins/org.yakindu.sct.doc.user/src/user-guide/overview.textile

@@ -6,7 +6,7 @@ h1(#what-are-yakindu-statechart-tools). What are YAKINDU Statechart Tools?
 The statechart tools are a central part of YAKINDU: the modular toolkit for model-driven development of embedded systems. It is based on the open-source development platform Eclipse. YAKINDU Statechart Tools (YAKINDU SCT) provide the following tools to deal with state machine diagrams:
 
 * *Statechart diagram editor* to graphically create and edit statecharts
-* *Statechart simulator* to simulate the behavior of statecharts
+* *Statechart simulator* to simulate the behavior of state machines
 * *Code generators for Java, C, C++* to transform statecharts into code
 * *Custom generator projects* to easily create model-to-text transformations with Xtend or Java
 * *Integrated validator* to check for syntactical or semantical problems of the statechart model 
@@ -31,7 +31,7 @@ You may ask: Where does the money for open-source development come from? Well, i
 
 h2(#who-is-using-yakindu-statechart-tools). Who is using YAKINDU Statechart Tools?
 
-Initially YAKINDU Statechart Tools have been designed for the embedded systems industry: automotive, system controls, vending machines etc. However, YAKINDU Statechart Tools are bringing benefit to everyone who needs to design, simulate and develop behavior. People can use YAKINDU Statechart Tools to generate Java, C, or C++ code.
+Initially YAKINDU Statechart Tools have been designed for the embedded systems industry: automotive, system controls, vending machines etc. However, YAKINDU Statechart Tools are bringing benefit to everyone who needs to design, simulate and develop behavior with state machines (Finite State Machines, FSM). People can use YAKINDU Statechart Tools to generate Java, C, or C++ code.
 
 ###.. FIXME: Decide what to do with the following subsection regarding the document structure.
 ###.. FIXME: h3(#what-is-the-structure-of-this-documentation). What is the structure of this documentation?