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 f50eda6bb3cdd..9c435e68a5070 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
@@ -199,7 +199,7 @@ service PodResourcesLister {
 
 List endpoint provides information on resources of running pods with details such as
 id of exclusively allocated CPUs, device id as it was reported by device plugins and id of
-NUMA node where these devices are allocated.
+the NUMA node where these devices are allocated.
 
 ```gRPC
 // ListPodResourcesResponse is the response returned by List function
@@ -312,4 +312,3 @@ Here are some examples of device plugin implementations:
 * Read about using [hardware acceleration for TLS ingress](https://kubernetes.io/blog/2019/04/24/hardware-accelerated-ssl/tls-termination-in-ingress-controllers-using-kubernetes-device-plugins-and-runtimeclass/) with Kubernetes
 * Learn about the [Topology Manager](/docs/tasks/administer-cluster/topology-manager/)
 
-