diff --git a/content/runbooks/kubernetes/KubeHpaMaxedOut.md b/content/runbooks/kubernetes/KubeHpaMaxedOut.md
index db1defd..14a2e2e 100644
--- a/content/runbooks/kubernetes/KubeHpaMaxedOut.md
+++ b/content/runbooks/kubernetes/KubeHpaMaxedOut.md
@@ -7,13 +7,14 @@ weight: 20
 
 ## Meaning
 
-Horizontal Pod Autoscaler has been running at max replicas for longer
+The Horizontal Pod Autoscaler (HPA) has been running at maximum replicas for longer
 than 15 minutes.
 
 ## Impact
 
-Horizontal Pod Autoscaler won't be able to add new pods and thus scale application.
-**Notice** for some services maximizing HPA is in fact desired.
+The Horizontal Pod Autoscaler will not be able to add new pods, thus preventing the
+application from scaling. 
+**Notice** For some services, maximizing HPA utilization is actually desired.
 
 ## Diagnosis
 
@@ -26,7 +27,7 @@ Check why HPA was unable to scale:
 
 If using basic metrics like CPU/Memory then ensure to set proper values for
 `requests`.
-For memory based scaling ensure there are no memory leaks.
-If using custom metrics then tine tune how app scales accordingly to it.
+For memory-based scaling, ensure there are no memory leaks.
+If using custom metrics, fine-tune how the app scales according to it.
 
 Use performance tests to see how the app scales.