diff --git a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
index 05b343da06716..ef0a0ca050d34 100644
--- a/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
+++ b/content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
@@ -184,8 +184,8 @@ It is typical that code relying on the device will start failing and Pod may get
 into Failed phase if `restartPolicy` for the Pod was not `Always` or enter the crash loop
 otherwise.
 
-Before the Kubernetes version 1.31, the way to know whether Pod is associated with the
-failed device was to use the [PodResources API](#monitoring-device-plugin-resources).
+Before Kubernetes v1.31, the way to know whether or not a Pod is associated with the
+failed device is to use the [PodResources API](#monitoring-device-plugin-resources).
 
 {{< feature-state feature_gate_name="ResourceHealthStatus" >}}