Added section title headers to every file, and moved references to the correct...

Added section title headers to every file, and moved references to the correct location within these sections.

Example01_SimpleMessageFlow_EventCoordination.mp

@@ -15,7 +15,7 @@ a "cross-cutting" derivation rule.
 References: 
 "Example 1: Simple interaction pattern" from Auguston, M. 
 "Monterey Phoenix System and Software Architecture and 
-Workflow Modeling Language Manual (Version 4). 2020. 
+Workflow Modeling Language Manual" (Version 4). 2020. 
 Available online: 
 https://wiki.nps.edu/display/MP/Documentation 
 

Example01a_UnreliableMessageFlow_VirtualEvents.mp

 /* Example 01a. Model of Unreliable Message Flow
-See also: Example 8: Unreliable Communication model from the Monterey Phoenix 
-System and Software Architecture and Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 8: Unreliable Communication model" from Auguston,
+M. "Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual" (Version 4). 2020.
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation
+
+Search terms:
 
 We may want to specify behaviors when some messages get lost in the transition. 
 It can be done using ‘virtual’ events.

Example02_DataFlow_EventSharing.mp

 /* Example 02. Model of Data Flow
-See also: Example 3: Data Flow model from the Monterey Phoenix System and 
-Software Architecture and Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 3: Data Flow model from the Monterey Phoenix"
+from Auguston, M. "Monterey Phoenix System and Software
+Architecture and Workflow Modeling Language Manual"
+(Version 4). 2020. Available online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
 
 data items as behaviors
 

Example03_ATMWithdrawal_BehaviorOfEnvironment.mp

 /* Example 03. Model of ATM Withdrawal
-See also: Example 4: Withdraw money from ATM model from the Monterey Phoenix System and 
-Software Architecture and Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 4: Withdraw money from ATM model" from Auguston,
+M. "Monterey Phoenix System and Software Architecture and
+Workflow Modeling Language Manual" (Version 4). 2020.
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation
+
+Search terms:
 
 Integrated system and environment behaviors
 	

Example04_StackBehavior_EnsureCondition.mp

 /* Example 04. Model of Stack Behavior
-See also: Example 5: Stack behavior model from the Monterey Phoenix 
-System and Software Architecture and Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 5: Stack behavior model" from Auguston, M. 
+"Monterey Phoenix System and Software Architecture and 
+Workflow Modeling Language Manual" (Version 4). 2020. 
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
 
 	The event trace is a set of events and the Boolean expressions
 in MP can embrace the traditional predicate calculus notation. A set

Example04a_StackBehavior_UserDefinedRelations.mp

 /* Example 04a. Model of Stack Behavior
-See also: Example 17: Stack behavior model with pop/push relationship 
-visualized from the Monterey Phoenix System and Software Architecture and 
-Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:  
+"Example 17: Stack behavior model" from Auguston, M. 
+"Monterey Phoenix System and Software Architecture and 
+Workflow Modeling Language Manual" (Version 4). 2020. 
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
 
 The event trace is a set of events and the Boolean expression constructs in MP 
 can support the traditional first order predicate calculus notation. 

Example04b_QueueBehavior_UserDefinedRelations.mp

 /* Example 04b. Model of Queue Behavior
-See also: Example 18: Queue behavior model from the Monterey Phoenix System and 
-Software Architecture and Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 18: Queue behavior model" from Auguston, M. 
+"Monterey Phoenix System and Software Architecture and 
+Workflow Modeling Language Manual" (Version 4). 2020. 
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
 
 This rule specifies the behavior of a queue in terms of queue operations 
 enqueue and dequeue. It is assumed that initially Queue is empty. 

Example05_CarRace_NestedComposition.mp

 /* Example 05. Model of Car Race
-See also: Example 6: Car race model from the Monterey Phoenix System and 
-Software Architecture and Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 6: Car race model" from Auguston, M. "Monterey
+Phoenix System and Software Architecture and Workflow
+Modeling Language Manual" (Version 4). 2020. Available
+online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
 
 more coordination patterns:
 -	ordering of selected events in concurrent threads

Example06_UnreliableChannel_AssertionChecking.mp

 /* Example 06. Model of Unreliable Channel
-See also: Example 10: Communicating via unreliable channel model from 
+See also:  from 
 the Monterey Phoenix System and Software Architecture and Workflow 
 Modeling Language Manual
 
+Purpose:
+
+Description:
+
+References:
+"Example 10: Communicating via unreliable channel model"
+from Auguston, M. "Monterey Phoenix System and Software
+Architecture and Workflow Modeling Language Manual"
+(Version 4). 2020. Available online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
+
 	Assertion checking, Communicating via unreliable channel.
 
 	MP models need to be tested and debugged like any other 

Example07_UnconstrainedStack_TraceAnnotation.mp

 /* Example 07. Model of Unconstrained Stack
-See also: Example 11: Testing/Debugging model’s behavior from the Monterey 
-Phoenix System and Software Architecture and Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 11: Testing/Debugging model’s behavior" from
+Auguston, M. "Monterey Phoenix System and Software
+Architecture and Workflow Modeling Language Manual"
+(Version 4). 2020. Available online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
 
 Trace annotation techniques 
 

Example08_EmployeeEmployer_CoordinationAcrossHierarchyLevels.mp

 /* Example 08. Model of Employee Employer
-See also: Example 13: Business process model from the Monterey Phoenix 
-System and Software Architecture and Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 13: Business process model" from Auguston, M. 
+"Monterey Phoenix System and Software Architecture and 
+Workflow Modeling Language Manual" (Version 4). 2020. 
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
 
 The web site http://www.infoq.com/articles/bpelbpm 
 “Why BPEL is not the holy grail for BPM “ 

Example09_PipeFilter_TraceAnnotationQueries.mp

 /*  Example 09. Model of Pipe Filter
-See also: Example 12: Pipe/Filter architecture model from the Monterey 
-Phoenix System and Software Architecture and Workflow Modeling Language 
-Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 12: Pipe/Filter architecture model" from Auguston,
+M. "Monterey Phoenix System and Software Architecture and 
+Workflow Modeling Language Manual" (Version 4). 2020. 
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation
+
+Search terms:
 
     pipe/filter architecture model with 2 filters
 

Example10_PublishSubscribe_EventReshuffling.mp

 /* Example 10. Model of Publish Subscribe
-See also: Example 7: Publish/Subscribe architecture model 
-from the Monterey Phoenix System and Software Architecture 
-and Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 7: Publish/Subscribe architecture" from Auguston,
+M. "Monterey Phoenix System and Software Architecture and 
+Workflow Modeling Language Manual" (Version 4). 2020. 
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
 
 	Publisher sends a notification to all active Subscribers 
     when new information is available.

Example11_RingTopology_UserDefinedRelations.mp

 /* Example 11. Model of Ring Topology
-See also: Example 16: User-defined relations from the Monterey Phoenix 
-System and Software Architecture and Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 16: User-defined relations" from Auguston, M. 
+"Monterey Phoenix System and Software Architecture and 
+Workflow Modeling Language Manual" (Version 4). 2020. 
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
 
     ring topology
     an example of user-defined relation use

Example12_CardiacArrestWorkflow_VirtualEvents.mp

 /* Example 12. Model of Cardiac Arrest Workflow
-See also: Examples 9 and 14 on Workflow patterns from the Monterey Phoenix 
-System and Software Architecture and Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 9: Workflow pattern" and "Example 14: Workflow 
+pattern" from Auguston, M. "Monterey Phoenix System and 
+Software Architecture and Workflow Modeling Language 
+Manual" (Version 4). 2020. Available online: 
+https://wiki.nps.edu/display/MP/Documentation
+
+Search terms:
 
 the web site
 http://workflowpatterns.com/patterns/control/index.php

Example13_ConsumersSuppliers_DependencyTracking.mp

 /* Example 13. Model of Consumers Suppliers
-See also: Example 29: Coordinating asynchronous threads and 
-tracking event dependency from the Monterey Phoenix System 
+See also:  from the Monterey Phoenix System 
 and Software Architecture and Workflow Modeling Language Manual
 
+Purpose:
+
+Description:
+
+References:
+"Example 29: Coordinating asynchronous threads and 
+tracking event dependency" from Auguston, M. "Monterey 
+Phoenix System and Software Architecture and Workflow 
+Modeling Language Manual" (Version 4). 2020. Available 
+online: 
+https://wiki.nps.edu/display/MP/Documentation
+
+Search terms:
+
 Asynchronous coordination and dependency definition example.
 
 user-defined relation related_to connects events within each 

Example14_ShoppingSpree_NumberAttributes.mp

 /* Example 14. Model of Shopping Spree
-See also: Example 21: Attribute use from the Monterey 
+
+Purpose:
+
+Description:
+
+References:
+"Example 21: Attribute use" from Auguston, M. "Monterey 
 Phoenix System and Software Architecture and Workflow 
-Modeling Language Manual
+Modeling Language Manual" (Version 4). 2020. Available 
+online: 
+https://wiki.nps.edu/display/MP/Documentation
+
+Search terms:
 
 Instructions: Run for Scopes 1 and up. Viewing of traces 
 also includes a "Swim Lanes" option.

Example15_BackpackWeight_IntervalAttributes.mp

 /* Example 15. Model of Backpack Weight
-See also: Example 22: Use of interval attributes from the 
-Monterey Phoenix System and Software Architecture and
-Workflow Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 22: Use of interval attributes" from Auguston, M. 
+"Monterey Phoenix System and Software Architecture and 
+Workflow Modeling Language Manual" (Version 4). 2020. 
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation
+
+Search terms:
 
     Use of interval attributes.
     

Example16_StackBehavior_ProbabilityCalculationsType1.mp

 /* Example 16. Model of Stack Behavior
-See also: Example 30: Type 1 probability from the Monterey 
-Phoenix System and Software Architecture and Workflow 
-Modeling Language Manual
+
+Purpose:
+
+Description:
+
+References:
+"Example 30: Type 1 probability" from Auguston, M. 
+"Monterey Phoenix System and Software Architecture and 
+Workflow Modeling Language Manual" (Version 4). 2020. 
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
 
 	Here is a simple stack behavior model. Valid behaviors don’t permit
 a scenario when Pop operation is applied to the empty stack. For the

Example17_SharedEvents_ProbabilityCalculationsType1.mp

 /* Example 17. Model of Shared Events
-See also: Example 31: Shared events with probabilities from 
+See also:  from 
 the Monterey Phoenix System and Software Architecture and 
 Workflow Modeling Language Manual
 
+Purpose:
+
+Description:
+
+References:
+"Example 31: Shared events with probabilities" from Auguston, 
+M. "Monterey Phoenix System and Software Architecture and 
+Workflow Modeling Language Manual" (Version 4). 2020. 
+Available online: 
+https://wiki.nps.edu/display/MP/Documentation 
+
+Search terms:
+
 	A simple example of shared events. If one root has a, the other root
 also has a. If neither root has a, then root 1 must have b, and root 2
 must have c. Additionally, probabilities show how "SHARE ALL" increases