What-am-I-looking-at-here.md

@@ -30,15 +30,15 @@ Light host 0-2 by default each create and upload four AAS to the AAS Server and
 
 Why doesn't a light host host exactly one light?  
 Frankly, to have a bit more to see and because it would be quite wasteful. It also demonstrates, how one additional device can send controls to multiple assets (here, LEDs), reducing costs of integration of existing Assets into an Industrie4.0-environment.  
-Changing the amount of lights present on a light host is quite simple, too and provides an easy entry point in understanding the Demo itself. More on that in the [documentation for the startup script](TODO).
+Changing the amount of lights present on a light host is quite simple, too and provides an easy entry point in understanding the Demo itself. More on that in the documentation for the startup scripts [here](implementation/start_component.sh) and [here](implementation/run_demo.sh).
 
 ## ESP32 Controller
 
-The ESP32 Controller demonstrates how to integrate components utilizing a proprietary protocol into a BaSyx environment. ESP32 #0 through #2 are controlled via a simple proprietary protocol, [explained here](TODO), while the ESP32 Controller uploads their AAS and hosts the submodels doing the actual controlling. 
+The ESP32 Controller demonstrates how to integrate components utilizing a proprietary protocol into a BaSyx environment. ESP32 #0 through #2 are controlled via a simple proprietary protocol, [explained here](Proprietary-Protocol), while the ESP32 Controller uploads their AAS and hosts the submodels doing the actual controlling. 
 
 ## ProprietaryLight0-2
 
-These are ESP32 microcontrollers, connected to single Red/green LEDs each and via WiFi to the rest of the network. They implement a proprietary protocol and are integrated into the BaSyx environment by the ESP32 Controller. The protocol is [explained here](TODO).
+These are ESP32 microcontrollers, connected to single Red/green LEDs each and via WiFi to the rest of the network. They implement a proprietary protocol and are integrated into the BaSyx environment by the ESP32 Controller. The protocol is [explained here](Proprietary-Protocol).
 
 ## Light Controller
 
@@ -60,4 +60,4 @@ The demonstration controller uses predefined calls to represent the condition of
 ## AASX Server
 
 The AASX Server hosts an [AASX Server](https://github.com/admin-shell-io/aasx-server), as provided by the [Industrial Digital Twin Association e.V.](https://idtwin.org/). More specifically the `blazor` variant. As of now the AASX Server and the BaSyx environment are incompatible. It is here, to have it as part of the Demo for future evaluation of compatibility  and eventual integration.   
-Slightly more detail on compatibility [here](BaSyx-Adventures#compatibility-with-adminshellios-aasx-server).
+Slightly more detail on compatibility [here](initial considerations/BaSyx-Adventures#compatibility-with-adminshellios-aasx-server).