diff --git a/source/usage/Get it Running - Step by Step.md b/source/usage/Get it Running - Step by Step.md
index 69d7319..564a1e0 100644
--- a/source/usage/Get it Running - Step by Step.md	
+++ b/source/usage/Get it Running - Step by Step.md	
@@ -5,7 +5,7 @@ This document provides a step by step Instruction on how to get FabAcess running
 - 1 or more users registered to your system
 - QR-Codes generated to acess a machine
 - 1 Shelly configured as a door-opener
-- 1 Shelly configured to identify if a machine is just switched on or realy running
+- 1 Shelly configured to identify if a machine is just switched on or realy running (TO-DO)
 
 
 **Step 1 Installing the BFFH-Server**
@@ -198,5 +198,7 @@ Define a machine called "door" in the bffh.dhall<br>
 `]`<br>
 - assign the role DoorUser/internal to all users
 
-It is imporatant all users have admin aka manage permissions, as the request to open the door by a user, thet the door "in Use" by this user. The door can only be re-activated when the previous user "un-uses" the door or if an othe user can "force free" the door prior to using the door hin/herself
+It is imporatant all users have admin aka manage permissions, as the request to open the door by a user, thet the door "in Use" by this user. The door can only be re-activated when the previous user "un-uses" the door or if an othe user can "force free" the door prior to using the door hin/herself.<br>
 **Note** in this special case, where all users will need admin capabilities the role could also contain only the permission `lab.door.use` and all permissions (disclos, manage, read, write) assigned to the machine would simply match `lab.door.use` (e.g. disclose = "lab.door.use"`).
+
+**Identify if a machine is just switched on or realy running (TO-DO)