Deleting JPG Files ...

Moose Development/Moose/Core/Fsm.lua

@@ -87,7 +87,7 @@
 -- 
 -- ### 1.1.2) Transition Handling
 -- 
--- ![Transition Handlers](..\Presentations\FSM\Dia4.jpg)
+-- ![Transition Handlers](..\Presentations\FSM\Dia4.JPG)
 -- 
 -- An FSM transitions in **4 moments** when an Event is being triggered and processed.  
 -- The mission designer can define for each moment specific logic within methods implementations following a defined API syntax.  
@@ -109,7 +109,7 @@
 -- 
 -- ### 1.1.3) Event Triggers
 -- 
--- ![Event Triggers](..\Presentations\FSM\Dia5.jpg)
+-- ![Event Triggers](..\Presentations\FSM\Dia5.JPG)
 -- 
 -- The FSM creates for each Event two **Event Trigger methods**.  
 -- There are two modes how Events can be triggered, which is **synchronous** and **asynchronous**:
@@ -152,7 +152,7 @@
 -- Two Transition Rules are created, where upon the event Switch,
 -- the FsmDemo will transition from state Green to Red and vise versa.
 -- 
--- ![Transition Example](..\Presentations\FSM\Dia6.jpg)
+-- ![Transition Example](..\Presentations\FSM\Dia6.JPG)
 -- 
 --      local FsmDemo = FSM:New() -- #FsmDemo
 --      FsmDemo:SetStartState( "Green" )
@@ -162,7 +162,7 @@
 -- In the above example, the FsmDemo could flare every 5 seconds a Green or a Red flare into the air.
 -- The next code implements this through the event handling method **OnAfterSwitch**.
 -- 
--- ![Transition Flow](..\Presentations\FSM\Dia7.jpg)
+-- ![Transition Flow](..\Presentations\FSM\Dia7.JPG)
 -- 
 --      function FsmDemo:OnAfterSwitch( From, Event, To, FsmUnit )
 --        self:E( { From, Event, To, FsmUnit } )

docs/Documentation/Cargo.html

@@ -2411,6 +2411,7 @@ The UNIT carrying the package.</p>
 		<dl class="function">
 <dt>
 
+		<em></em>
 <a id="#(AI_CARGO_UNIT).CargoCarrier" >
 <strong>AI_CARGO_UNIT.CargoCarrier</strong>
 </a>

docs/Documentation/Fsm.html

@@ -163,7 +163,7 @@ These rules define when an FSM can transition from a specific state towards an o
 
 <h3>1.1.2) Transition Handling</h3>
 
-<p><img src="..\Presentations\FSM\Dia4.jpg" alt="Transition Handlers"/></p>
+<p><img src="..\Presentations\FSM\Dia4.JPG" alt="Transition Handlers"/></p>
 
 <p>An FSM transitions in <strong>4 moments</strong> when an Event is being triggered and processed. <br/>
 The mission designer can define for each moment specific logic within methods implementations following a defined API syntax. <br/>
@@ -189,7 +189,7 @@ These parameters are on the correct order: From, Event, To:</p>
 
 <h3>1.1.3) Event Triggers</h3>
 
-<p><img src="..\Presentations\FSM\Dia5.jpg" alt="Event Triggers"/></p>
+<p><img src="..\Presentations\FSM\Dia5.JPG" alt="Event Triggers"/></p>
 
 <p>The FSM creates for each Event two <strong>Event Trigger methods</strong>. <br/>
 There are two modes how Events can be triggered, which is <strong>synchronous</strong> and <strong>asynchronous</strong>:</p>
@@ -237,7 +237,7 @@ It will set the start state of FsmDemo to Green.
 Two Transition Rules are created, where upon the event Switch,
 the FsmDemo will transition from state Green to Red and vise versa.</p>
 
-<p><img src="..\Presentations\FSM\Dia6.jpg" alt="Transition Example"/></p>
+<p><img src="..\Presentations\FSM\Dia6.JPG" alt="Transition Example"/></p>
 
 <pre><code> local FsmDemo = FSM:New() -- #FsmDemo
  FsmDemo:SetStartState( "Green" )
@@ -248,7 +248,7 @@ the FsmDemo will transition from state Green to Red and vise versa.</p>
 <p>In the above example, the FsmDemo could flare every 5 seconds a Green or a Red flare into the air.
 The next code implements this through the event handling method <strong>OnAfterSwitch</strong>.</p>
 
-<p><img src="..\Presentations\FSM\Dia7.jpg" alt="Transition Flow"/></p>
+<p><img src="..\Presentations\FSM\Dia7.JPG" alt="Transition Flow"/></p>
 
 <pre><code> function FsmDemo:OnAfterSwitch( From, Event, To, FsmUnit )
    self:E( { From, Event, To, FsmUnit } )

docs/Documentation/Spawn.html

@@ -1692,6 +1692,9 @@ The group that was spawned. You can use this group for further actions.</p>
 	
 
 
+	
+<p> Don't repeat the group from Take-Off till Landing and back Take-Off by ReSpawning.</p>
+
 </dd>
 </dl>
 		<dl class="function">
@@ -2486,7 +2489,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):Schedule( 600, 0.5 )
 
 
 	
-<p> When the first Spawn executes, all the Groups need to be made visible before start.</p>
+<p> Flag that indicates if all the Groups of the SpawnGroup need to be visible when Spawned.</p>
 
 </dd>
 </dl>