diff --git a/content/en/docs/concepts/workloads/pods/sidecar-containers.md b/content/en/docs/concepts/workloads/pods/sidecar-containers.md
index b358ee4c12637..72021b8476954 100644
--- a/content/en/docs/concepts/workloads/pods/sidecar-containers.md
+++ b/content/en/docs/concepts/workloads/pods/sidecar-containers.md
@@ -97,9 +97,9 @@ maintain sidecar containers without affecting the primary application.
 Sidecar containers share the same network and storage namespaces with the primary
 container. This co-location allows them to interact closely and share resources.
 
-From Kubernetes perspective, sidecars graceful termination is less important. 
-When other containers took all alloted graceful termination time, sidecar containers
-will receive the `SIGTERM` following with `SIGKILL` faster than may be expected. 
+From a Kubernetes perspective, the sidecar container's graceful termination is less important.
+When other containers take all allotted graceful termination time, the sidecar containers
+will receive the `SIGTERM` signal, followed by the `SIGKILL` signal, before they have time to terminate gracefully. 
 So exit codes different from `0` (`0` indicates successful exit), for sidecar containers are normal
 on Pod termination and should be generally ignored by the external tooling.