diff --git a/README.md b/README.md
index 981267dc44545a7f401cbcb07958ff53a2a536ae..cfde8d1cd62545d46b4c156403d55827861beee0 100644
--- a/README.md
+++ b/README.md
@@ -182,7 +182,7 @@ Each module can see all information and decide how it reacts to the current comb
 The logical flow of the application game loop goes as follows:
 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 posts appropriate messages for other modules (e.g. place structure)
+3. `GuiHandler` checks if user input targets the GUI, updates the global state (e.g. change source frequency, change mouse state to "Zeichnen") and posts appropriate messages for other modules (e.g. place structure)
 4. `WaveHandler` checks if any messages that target it have been posted
 5. `SlimBlockchainHandler` reacts to its messages and user input
 6. `DrawingHandler` reacts to its messages and user input