home.md

@@ -33,7 +33,7 @@ The Changes I've made are pretty much self explanatory, see [here](https://gitla
 2. Implementing the [BaSyx Submodel API](https://app.swaggerhub.com/apis/BaSyx/basyx_submodel_http_rest_api/v1) on an ESP32. This would eliminate the need for a way more poweful machine like the Raspberry Pi, especially, if pushing the relevant AAS and registering can be done, too. This might bring the cost of integration of existing gear into a I4.0 environment down by an order of magnitude.
 3. ~Containerizing the components. I've worked extensively using environment variables here, so it should be quite suited for docker images.  
 At least for a "off the shelf" container to run the whole demo virtually on your local machine I can see good use.~
-4. Create a nice looking demonstration stand. Right now, the whole thing is basically a pile of wires and computers - not very appealing. Maybe even create a PCB and case for the [Demonstration Controller](What-am-I-looking-at-here#demonstration-controller)
+4. ~Create a nice looking demonstration stand. Right now, the whole thing is basically a pile of wires and computers - not very appealing. Maybe even create a PCB and case for the [Demonstration Controller](What-am-I-looking-at-here#demonstration-controller)~
 5. Implement the lookup of relevant AAS and submodels for the [Light Controller](implementation/Light-Controller-walkthrough#lightcontroller) and [Light Animator](implementation/Light-Animator-walkthrough#lightanimator) by looking up implementations of types of AAS and Submodels instead of relying on a naming convention I made up.
 6. ~Reimplement the Demo using other frameworks - or at least evaluate their interoperability, especially after BaSyx v2 gets released.~