From 2bf6e3bb3da9f4910e8f38077af1e5170fee2201 Mon Sep 17 00:00:00 2001 From: ni-richard Date: Mon, 16 Sep 2019 22:21:41 +0200 Subject: [PATCH] Updated Introduction (markdown) --- Introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Introduction.md b/Introduction.md index 49a9ce4..2eef75d 100644 --- a/Introduction.md +++ b/Introduction.md @@ -8,4 +8,4 @@ In the upper-left part of the page you can see the chat bot, right next to it is ### Sequence of events Everything that has a beginning has an end. Generally, you can define the steps of an exercise using a [finite-state machine](https://en.wikipedia.org/wiki/Finite-state_machine). This means that certain events can trigger a transition from one state to another. For instance, you want the user to login in your web service, and if it was successful, you would trigger the next step by notifying the *TFW server*, which will forward your message to the *FSM* instance that evaluates your request, and finally the state change happens, and additional logic is executed to prepare the environment for the next step until the last. -In the second chapter, you will find detailed description regarding each component. \ No newline at end of file +In the third chapter, you will find detailed description regarding each component. \ No newline at end of file