diff --git a/models/Application_examples/Agile_Production_Platform_Supply_Chain_Interaction.mp b/models/Application_examples/Agile_Production_Platform_Supply_Chain_Interaction.mp
index b7744b21b7743742550b3cdd2cae88994eaed25f..7717fc47e5b8d5da234cbbe4208218eee93a1d99 100644
--- a/models/Application_examples/Agile_Production_Platform_Supply_Chain_Interaction.mp
+++ b/models/Application_examples/Agile_Production_Platform_Supply_Chain_Interaction.mp
@@ -7,26 +7,27 @@ Modified collaboratively in Teams by Kristin Giammarco and
 	Joshua Beaver on the 17th of September, 2020.
 Edited by Pamela Dyer in September, 2021.
 
-Purpose: To illustrate a model of interactions among 
-raw material suppliers, component suppliers, finished 
-product suppliers, the customer, and the "Agile Production 
-Platform" (APP).
+Purpose: To illustrate a model that focuses on the 
+interrelations of supply chains with the "Agile Production 
+Platform" (APP) as the intermediary.
 
 Description: This model demonstrates using MP to find both 
-desired and undesired scenarios of Personal Protective 
-Equipment (PPE) supply chains within the APP. The APP 
-represents the linkage platform being designed to enable 
-agile production / building of alternative supply chains.
-
-Specifically in this model, the focus is on interrelations 
-of supply chains with the APP as the intermediary. Raw 
-material suppliers, component suppliers, finished product 
-suppliers, the customer, and the APP are all taken into 
-account. In general, the goal of the model is to check 
-that each phase of supplier is able to produce the 
-expected product.
-
-Running this model at Scope 1 generates 
+desired and undesired scenarios resulting from interactions 
+among supply chains. Raw material suppliers, component 
+suppliers, finished product suppliers, the customer, and 
+the APP are all taken into account. In general, the goal 
+of the model is to check that each phase of supplier is 
+able to produce the expected product. Here the product 
+is a general term. When run at Scope 1, there are 55 traces 
+generated. An example of Expected Emergent Behavior coming 
+out of this is: the component supplier was still at maximum 
+capacity even though the APP pooled more suppliers at all 
+levels of production, so the order was not fulfilled (an 
+Unfavorable Outcome). An example of Unexpected Emergent 
+Behavior coming out of this model is: a nonconforming 
+material still making its way to the customer, either 
+through a miscommunication or lack of inspection (also an 
+Unfavorable Outcome).
 
 References:
 Beaver, Joshua. "Analyzing Emergent Behavior of Supply