From 0e5dfcea625faf65080388a0882cdb9b98f119b4 Mon Sep 17 00:00:00 2001 From: ni-richard Date: Tue, 10 Sep 2019 13:28:45 +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 c64e599..42e13d3 100644 --- a/Introduction.md +++ b/Introduction.md @@ -5,5 +5,5 @@ Efficiency in learning can be remarkably improved by presenting the content in a *** In the upper-left part of the page you can see the chat bot, right next to it is a custom web service, in the rightmost part is the web IDE and the remaining one is a fully-featured terminal environment with an optional console tab where you can insert arbitrary text. To manipulate the components, you can send commands on the backend side to the *TFW server*, where event handlers process your request and instruct the frontend through a *WebSocket* connection. -## Sequence of events +### 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. \ No newline at end of file