diff --git a/Example01a_UnreliableMessageFlow_VirtualEvents.mp b/Example01a_UnreliableMessageFlow_VirtualEvents.mp
index a652c55521b73f9a2e1e4b49b57362a50dd58038..9f9425f477c5738ac3d45dc716350bf95c335a35 100644
--- a/Example01a_UnreliableMessageFlow_VirtualEvents.mp
+++ b/Example01a_UnreliableMessageFlow_VirtualEvents.mp
@@ -2,10 +2,12 @@
 See also: Example 8: Unreliable Communication model from the Monterey Phoenix 
 System and Software Architecture and Workflow Modeling Language Manual
 
-Purpose: Demonstrate scenario similar to 1a in which Receiver may not receive.
+Purpose: Illustrate use of | as split of multiple outcomes.
 
+Description: 
 We may want to specify behaviors when some messages get lost in the transition. 
-It can be done using ‘virtual’ events.
+It can be done using ‘virtual’ events. This will give us an event trace of both
+the outcome before and after the | operator. 
 
 Instructions: Run for Scopes 1 and up. Viewing of traces also includes a "Swim 
 Lanes" option.