From 2b37edbaafa9d848f9d5183fe8300e73eaee4254 Mon Sep 17 00:00:00 2001
From: Pascal Engeler <engelerp@phys.ethz.ch>
Date: Wed, 8 Sep 2021 11:41:04 +0200
Subject: [PATCH] one should be precise

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index daccf98..a975c40 100644
--- a/README.md
+++ b/README.md
@@ -180,7 +180,7 @@ The application is split into different modules, each module handles a subset of
 Much like the name suggests, the `Toolbox` is passed around from one module to the next, and each can then access everything stored within it. 
 Each module can see all information and decide how it reacts to the current combination of state, messages and events (user input).
 The logical flow of the application game loop goes as follows:
-1. `InputHandler` writes new user input into the `Toolbox` event chain
+1. `InputHandler` fetches and writes new user input into the `Toolbox` event chain
 2. `TimeoutHandler` checks if there is any user input, and if timeout occurs posts reset requests to the `Toolbox` mailbox targeting all other modules
 3. `GuiHandler` checks if user input targets the GUI, updates the global state (e.g. change source frequency, change game mode to "Zeichnen") and sends appropriate messages to other modules (e.g. place structure)
 4. `WaveHandler` checks if any messages that target it have been posted
-- 
GitLab