[update] working design

Author: tedi-software

docs/assets/images/tedi_enterprise_small.png

@@ -23,6 +23,23 @@ Key elements featured include:
 
 ---
 
+
+
+## **Conceptual Architecture**
+{: .fs-5 }
+<img src="../../assets/images/tedi_enterprise_small.png" alt="Tedi" height="901" width="781">
+
+Conceptual
+{: .label .label-yellow } 
+Composable Architecture
+{: .label .label-blue } 
+Microservices
+{: .label .label-green }
+
+---
+
+## **System Architecture**
+{: .fs-5 }
 <img src="../../assets/images/adiag.png" alt="Tedi" height="1920" width="1080">
 
 
@@ -55,4 +72,4 @@ TEDI is functionally a layer-7 application, so for your network ingress and egre
 Middleware is supposed to plumb together software applications in a transparent way. The Producer and Consumer of data should be unaware, *and without care*, that the data is being transported from them or to them, in some manner that 
 they don't have to manage themselves.
 
-TEDI is the vehicle by which to move data from one point to another complete with configurable retry mechanics, comprehensive logging, and alerting.
+TEDI is the vehicle by which to move data from one point to another complete with configurable retry mechanics, comprehensive logging, and alerting.