Revise MVK documentation: enhance CLI-centric explanations, clarify use cases, and expand introduction with personal experiences and tooling insights.

pages/uses04.md

@@ -1,6 +1,6 @@
 # Minimal Viable Kubernetes
 
-Use Cases ?
+## Use Cases
 
 ### 🏠 Local development
 
@@ -15,14 +15,12 @@ Use Cases ?
 
 <!--
 
-We live in the command line, so MVK is CLI centric. It uses a very simple command line tool, `infctl` to marshal scripts and commands in a stop by step manner, similar to the way we right pipelines in the cloud.
+prodduction can be never upgraded, rather, new productdion can replace old, provin infra as code and migrating to major updates
 
-It is simple to get started, so that startups and the impatient can become productive with Kubernetes quickly, without having to rely on managed offerings and in order to self host easily.
+We are already backing up our data right ?
 
-Each pipeline use steps of code that are repeatable, idempotent and using infrastructure as code.
+how can we prove our backups are valid without DR tests, rehearsals ?
 
-Kubernetes *can run anywhere* so MVK takes that principle and applies this to the self hosted approach making it possible to have the same setup on-prem and in the cloud
-
-It is important to keep things simple so as to be understandable, maintainable and easy to change and extend to our own use cases
+we can if we have infra as code
 
 -->