diff --git a/latest/ug/nodes/node-health-nma.adoc b/latest/ug/nodes/node-health-nma.adoc
index 47aef89e..2877413e 100644
--- a/latest/ug/nodes/node-health-nma.adoc
+++ b/latest/ug/nodes/node-health-nma.adoc
@@ -478,7 +478,7 @@ The monitoring condition is `NetworkingReady` for issues in the following table
 [#node-health-Storage]
 == Storage node health issues
 
-The monitoring condition is `StorageReady` for issues in the following table that have a severity of “Condition”.
+The monitoring condition is `StorageReady` for issues in the following table that have a severity of “Event”.
 
 [%header,cols="4"]
 |===
diff --git a/latest/ug/nodes/node-repair.adoc b/latest/ug/nodes/node-repair.adoc
index 591a6033..606bfa6c 100644
--- a/latest/ug/nodes/node-repair.adoc
+++ b/latest/ug/nodes/node-repair.adoc
@@ -56,8 +56,8 @@ For a detailed list of node health issues detected by the EKS node monitoring ag
 
 |StorageReady
 |StorageReady indicates whether the node's storage subsystem is functioning correctly (disks, filesystems, I/O).
-|30m
-|Replace
+|N/A
+|None
 
 |Ready
 |Ready is the standard Kubernetes condition indicating the node is healthy and ready to accept pods.