From 1c3505d5554fc6931efc2a0337aa3c3050a9e236 Mon Sep 17 00:00:00 2001 From: Egor Ushakov Date: Sat, 26 Aug 2023 23:36:19 +0400 Subject: [PATCH] Update index.md Fix typo --- docs/methodology/event-storming/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/methodology/event-storming/index.md b/docs/methodology/event-storming/index.md index 61f84262b..97eb4c18e 100644 --- a/docs/methodology/event-storming/index.md +++ b/docs/methodology/event-storming/index.md @@ -162,7 +162,7 @@ Keep the model strictly consistent within these bounds. #### Step 8: Looking forward with insight storming -In event atorming for Event Driven Architecture (EDA) solutions it is helpful to include an additional method step at this point identifying useful predictive analytics insights. +In event storming for Event Driven Architecture (EDA) solutions it is helpful to include an additional method step at this point identifying useful predictive analytics insights. Insights storming extends the basic methodology by looking forward and considering what if you could know in advance that an event is going to occur. How would this change your actions, and what would you do in advance of that event actually happening? You can think of insight storming as extending the analysis to **Derived Events**. Rather than being the factual recording of a past event, a derived event is a forward-looking or predictive event, that is, "this event is probably going to happen at some time in the next n hours”.