Revise introduction in slides.md to clarify the purpose of Minimal Viable Kubernetes and share personal experiences with Kubernetes deployment.

slides.md

@@ -57,31 +57,43 @@ Jon Brookes 2025
 <img src="/containers.webp" alt="preload" style="display:none;" />
 
 <!--
-This is an introduction to Minimal Viable Kubernetes (MVK). What it is, why it is brought into being and its tooling.
 
-17/18 I was working with Docker, for a time then 
+Welcome
 
-and now Swarm, then K8s
+this is an intro to MVK and why I made it ...
 
-one week deploying K8s 
+My K8s exp
 
-Self hosted, AWS vms and vmware on prem
+up to 17/18 I was working with Docker
 
-already on call, the next week on call 24X7 with k8s in the mix
+then Swarm, migrated to K8s
 
-MVK has my experieces and thoughts from this time and untill now 
+AWS cloud and vmware on prem
+
+one week deploying self-hosted K8s with ansible
+
+the next week on call 24X7 with k8s in the mix
+
+Since then, I worked on managed k8s in Azure and AWS, often with Terraform
+
+MVK uses k3s but could as well be
+
+* k0s
+* minik8s
+* talos
+
+I would like to move toward Talos but k3s for now 
+
+I wanted to 
+
+* use my own knowlege to deliver my own self managed k8s
+* bring down the cost of k8s
+* share what I know and pass it on
 
-I've deployed with terraform, tofu of managed k8s on Azure, AWS and now need MVK, so I made it.
 
-It is based on k3s but could as well be
 
-k0s
-minik8s
-talos
 
-I like talos and want to use it more
 
-it is MVK
 -->
 
 ---