diff --git a/content/en/docs/concepts/workloads/controllers/replicaset.md b/content/en/docs/concepts/workloads/controllers/replicaset.md
index c0ae664037132..fbd27929ba499 100644
--- a/content/en/docs/concepts/workloads/controllers/replicaset.md
+++ b/content/en/docs/concepts/workloads/controllers/replicaset.md
@@ -313,10 +313,10 @@ ensures that a desired number of Pods with a matching label selector are availab
 ### Pod Deletion Cost 
 {{< feature-state for_k8s_version="v1.21" state="alpha" >}}
 
-Using the `controller.kubernetes.io/pod-deletion-cost`, users can set a preference regarding 
+Using the `controller.kubernetes.io/pod-deletion-cost` annotation, users can set a preference regarding 
 which pods to remove first when downscaling a ReplicSet.
 
-The annotation should be set on the pod, the expected type is `int32`. It represents the cost of
+The annotation should be set on the pod, and the expected type is `int32`. It represents the cost of
 deleting a pod compared to other pods belonging to the same ReplicaSet. Pods with lower deletion
 cost are preferred to be deleted before pods with higher deletion cost. 
 
@@ -328,7 +328,7 @@ This feature is alpha and disabled by default. You can enable it by setting the
 `PodDeletionCost` in both kube-apiserver and kube-controller-manager.
 
 #### Warnings:
-- This is honored on a best-effort basis, and so it does not offer any guarantees on pod deletion order.
+- This is honored on a best-effort basis, so it does not offer any guarantees on pod deletion order.
 - Users should avoid updating the annotation frequently (e.g., updating it based on a metric value)
   because doing so will generate a significant number of pod updates on the apiserver.
 
diff --git a/content/en/docs/reference/command-line-tools-reference/feature-gates.md b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
index 3b4f4d9fa8e2f..45b6cfee24c1f 100644
--- a/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+++ b/content/en/docs/reference/command-line-tools-reference/feature-gates.md
@@ -667,7 +667,7 @@ Each feature gate is designed for enabling/disabling a specific feature:
 - `PVCProtection`: Enable the prevention of a PersistentVolumeClaim (PVC) from
   being deleted when it is still used by any Pod.
 - `PodDeletionCost`: Enable the [Pod Deletion Cost](/docs/content/en/docs/concepts/workloads/controllers/replicaset/#pod-deletion-cost)
-   feature which allow users to influence Replicaset downscaling order.
+   feature which allows users to influence ReplicaSet downscaling order.
 - `PersistentLocalVolumes`: Enable the usage of `local` volume type in Pods.
   Pod affinity has to be specified if requesting a `local` volume.
 - `PodDisruptionBudget`: Enable the [PodDisruptionBudget](/docs/tasks/run-application/configure-pdb/) feature.