diff --git a/proposals/009/assets/cloud-cyware.drawio.svg b/proposals/009/assets/cloud-cyware.drawio.svg
new file mode 100644
index 0000000..d01b429
--- /dev/null
+++ b/proposals/009/assets/cloud-cyware.drawio.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/proposals/009/assets/k8s-multi.webp b/proposals/009/assets/k8s-multi.webp
deleted file mode 100644
index 900f303..0000000
Binary files a/proposals/009/assets/k8s-multi.webp and /dev/null differ
diff --git a/proposals/009/techdetails.md b/proposals/009/techdetails.md
index f26c956..5e89c33 100644
--- a/proposals/009/techdetails.md
+++ b/proposals/009/techdetails.md
@@ -13,10 +13,10 @@ For this solution we will go with vanilla Kubernetes, but if this were a real pr
Our cluster architecture will consist of a multi-cloud control plane to ensure we can continue to manage our fleet if we suffer a single cloud provider outage, as well as multi-cloud node runtimes to distribute workloads to the cloud provider of our choice.
-Here is an image I borrowed that shows (replace on-premise with Azure) how the architecture might look:
+Here is an diagram that illustrates (at a very high-level) how the architecture might look:
+