improve the Motivation

Author: Jrmy2402

vertical-pod-autoscaler/enhancements/8459-memory-per-cpu/README.md

@@ -31,7 +31,7 @@ Many workloads scale their memory requirements proportionally to CPU. Today, VPA
 By introducing `memoryPerCPU`, users can enforce a predictable ratio between CPU and memory, reducing risk of misconfiguration and simplifying tuning for ratio-based workloads.
 
 In addition, some environments or organizations prefer to keep a fixed CPU-to-memory ratio for reasons such as:
-* **Billing models** – Many cloud providers price instances based on predefined CPU/memory bundles. Enforcing a fixed ratio makes VPA recommendations align better with billing units, avoiding unexpected cost patterns.
+* **Billing alignment** – Many cloud providers and SaaS/managed service vendors price resources based on fixed CPU-to-memory bundles (e.g., 1 CPU → 4 Gi RAM). Enforcing the same ratio at the VPA level ensures that workloads scale consistently with these billing models, preventing recommendations that would break cost expectations.
 * **Operational simplicity** – A consistent CPU/memory ratio across workloads reduces variability and simplifies capacity planning.
 
 ### Goals