Update Example01_SimpleMessageFlow_EventCoordination.mp,...

Update Example01_SimpleMessageFlow_EventCoordination.mp, Example01a_UnreliableMessageFlow_VirtualEvents.mp, Example02_DataFlow_EventSharing.mp, Example03_ATMWithdrawal_BehaviorOfEnvironment.mp, Example04_StackBehavior_EnsureCondition.mp, Example04a_StackBehavior_UserDefinedRelations.mp, Example04b_QueueBehavior_UserDefinedRelations.mp, Example05_CarRace_NestedComposition.mp, Example06_UnreliableChannel_AssertionChecking.mp, Example07_UnconstrainedStack_TraceAnnotation.mp files

Example01_SimpleMessageFlow_EventCoordination.mp

@@ -8,7 +8,8 @@ a modified event trace, merging behaviors of Sender and Receiver
 and adding the PRECEDES relation for the selected send/receive pairs.
 The coordination operation behaves as a "cross-cutting" derivation rule.
 
-Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces also includes a
+"Swim Lanes" option.
 
 ==========================================================*/
 

Example01a_UnreliableMessageFlow_VirtualEvents.mp

@@ -3,7 +3,8 @@
 We may want to specify behaviors when some messages get lost in the transition. 
 It can be done using ‘virtual’ events.
 
-Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim 
+Lanes" option.
 
 ==========================================================*/
 

Example02_DataFlow_EventSharing.mp

@@ -18,9 +18,10 @@ only event traces where corresponding event sharing is implemented.
 
 Event traces specified by the schema represent system’s emergent behavior, 
 where behaviors of subsystems are influenced by the coordination.
-This is a toy example of System_of_Systems emerging behavior modeling.
+This is a toy example of System of Systems emerging behavior modeling.
 
-Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces also includes a 
+"Swim Lanes" option.
 
 ==========================================================*/
 

Example03_ATMWithdrawal_BehaviorOfEnvironment.mp

@@ -21,7 +21,8 @@ By selecting a representative enough trace (containing all events and interactio
 like traces 2 or 3 for scope 1), and then collapsing root event, it becomes possible 
 to view a traditional "box-and-arrow" architecture diagram, i.e. to visualize an architecture view.
 
-Instructions: Run for Scopes 1 and up. "Sequence" mode yields views very similar to the UML or SysML Sequence Diagrams. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. "Sequence" mode yields views very similar to the UML or SysML 
+Sequence Diagrams. Viewing of traces also includes a "Swim Lanes" option.
 
 ==========================================================*/
 

Example04_StackBehavior_EnsureCondition.mp

@@ -27,7 +27,8 @@ and demonstrates an example of combining imperative (event grammar)
 and declarative (Boolean expressions) constructs for behavior
 specification.
 
-Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces also 
+includes a "Swim Lanes" option.
 
 ==========================================================*/
 

Example04a_StackBehavior_UserDefinedRelations.mp

@@ -17,7 +17,8 @@ as yet another kind of behavior composition, and demonstrates an
 example of combining imperative (event grammar) and declarative 
 (Boolean expressions) constructs for behavior specification.
 
-Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim 
+Lanes" option.
 
 ==========================================================*/
 

Example04b_QueueBehavior_UserDefinedRelations.mp

@@ -25,7 +25,8 @@ as yet another kind of behavior composition, and demonstrates an
 example of combining imperative (event grammar) and declarative 
 (Boolean expressions) constructs for behavior specification.
 
-Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces also includes a 
+"Swim Lanes" option.
 
 ==========================================================*/
 

Example05_CarRace_NestedComposition.mp

@@ -6,7 +6,8 @@ more coordination patterns:
 	
 -	one-many coordination.
 
-Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces also 
+includes a "Swim Lanes" option.
 
 ==========================================================*/
 

Example06_UnreliableChannel_AssertionChecking.mp

@@ -20,7 +20,8 @@
     if the property should always hold, it makes sense to convert it 
     into the ENSURE condition.
 
-	Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+	Instructions: Run for Scopes 1 and up. Viewing of traces also 
+	includes a "Swim Lanes" option.
 
 ==========================================================*/
 

Example07_UnconstrainedStack_TraceAnnotation.mp

@@ -17,7 +17,8 @@ might  violate certain property, and how to annotate these particular
 events in the trace with additional messages. Programmers will recognize 
 the use of debugging print statements for traditional program testing/debugging.
 
-Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim Lanes" option.
+Instructions: Run for Scopes 1 and up. Viewing of traces also includes a 
+"Swim Lanes" option.
 
 ==========================================================*/