From 49bf5b534483e79fbe8be3409c9acf66113102dd Mon Sep 17 00:00:00 2001
From: Daniel Awerbuck <dawerbuc@usc.edu>
Date: Tue, 29 Jun 2021 18:53:23 +0000
Subject: [PATCH] Update Example01a_UnreliableMessageFlow_VirtualEvents.mp

---
 Example01a_UnreliableMessageFlow_VirtualEvents.mp | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/Example01a_UnreliableMessageFlow_VirtualEvents.mp b/Example01a_UnreliableMessageFlow_VirtualEvents.mp
index a652c55..9f9425f 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.
-- 
GitLab