Demonstration missions added

docs/README.md

@@ -72,7 +72,21 @@ You'll need to browse to the right MOOSE Class within the inheritance tree struc
 
 ![MOOSE framework](Presentations\MOOSE\Dia2.JPG)
 
-## 3.1) MOOSE Core Classes
+
+## 3.1) MOOSE Demonstration Missions
+
+The framework comes with [demonstration missions](https://github.com/FlightControl-Master/MOOSE_MISSIONS), 
+that you can try out and helps you to code.  
+These missions provide examples of defined use cases how the MOOSE framework can be utilized. Each test mission is located in a separate directory, which contains at least one .lua file and .miz file.
+The .lua file contains the mission script file that shows how the use case was implemented.
+You can copy/paste code the code snippets from this .lua file into your missions, as it will accellerate your mission developments.
+You will learn, see, and understand how the different MOOSE classes need to be applied, and how you can create
+more complex mission scenarios by combining these MOOSE classes into a complex but powerful mission engine.
+
+These exact test missions are also demonstrated at the demo videos in the YouTube channel.
+
+
+## 3.2) MOOSE Core Classes
 
 These classes define the base building blocks of the MOOSE framework. These classes are heavily used within the MOOSE framework.
 
@@ -100,7 +114,7 @@ The POINT_VEC3 class manages the 3D simulation space, while the POINT_VEC2 class
 * [ZONES](Documentation/Zone.html): A set of zone classes that provide the functionality to validate the presence of GROUPS, UNITS, CLIENTS, STATICS within a certain ZONE. The zones can take various forms and can be movable.
 
 
-## 3.2) MOOSE Wrapper Classes
+## 3.3) MOOSE Wrapper Classes
 
 MOOSE Wrapper Classes provide an object oriented hierarchical mechanism to manage the DCS objects within the simulator.
 Wrapper classes provide another easier mechanism to control Groups, Units, Statics, Airbases and other objects.
@@ -132,7 +146,7 @@ The CLIENT class derives from the UNIT class, thus contains the complete UNIT AP
 The STATIC class derives from the POSITIONABLE class, thus contains also the position API set.
 
 
-## 3.3) MOOSE Functional Classes
+## 3.4) MOOSE Functional Classes
 
 MOOSE Functional Classes provide various functions that are useful in mission design.
 
@@ -146,7 +160,7 @@ MOOSE Functional Classes provide various functions that are useful in mission de
 
 * [SCORING](Documentation/Scoring.html): Administer the scoring of player achievements, and create a CSV file logging the scoring events for use at team or squadron websites.
 
-## 3.4) MOOSE AI Controlling Classes
+## 3.5) MOOSE AI Controlling Classes
 
 MOOSE AI Controlling Classes provide mechanisms to control AI over long lasting processes.  
 These AI Controlling Classes are based on FSM (Finite State Machine) Classes, and provided an encapsulated way to make AI behave or execute an activity.
@@ -161,7 +175,7 @@ These AI Controlling Classes are based on FSM (Finite State Machine) Classes, an
 
 * [AI_CARGO](Documentation/AI_Cargo.html): Make AI behave as cargo. Various CARGO types exist.
 
-## 3.5) MOOSE Human Tasking Classes
+## 3.6) MOOSE Human Tasking Classes
 
 MOOSE Tasking Classes provide a comprehensive Mission Orchestration System.
 Through COMMANDCENTERs, multiple logical MISSIONs can be orchestrated for coalitions.
@@ -180,7 +194,7 @@ Each TASK has a TASK ACTION flow, which is the flow that a player (hosted by a U
 
 * [TASK_CAS](Documentation/Task_A2G.html): Models a CAS Task, where a Player is routed towards an attack zone with enemies nearby, and various ground targets need to be eliminated.
 
-## 3.6) MOOSE Action Classes
+## 3.7) MOOSE Action Classes
 
 MOOSE Action Classes are task action sub-flows, that can be used and combined, to quickly define a comprehensive end-to-end task action flow.
 For example, for the SEAD Task, the task action flow combines the actions ASSIGN, ROUTE, ACCOUNT and ASSIST task action sub-flows.