fix typo

3 files changed, 4 insertions, 4 deletions

diff --git a/contributors/design-proposals/multicluster/federated-replicasets.md b/contributors/design-proposals/multicluster/federated-replicasets.md
index 9ed57bc7..59459b1c 100644
--- a/contributors/design-proposals/multicluster/federated-replicasets.md
+++ b/contributors/design-proposals/multicluster/federated-replicasets.md
@@ -286,7 +286,7 @@ enumerated the key idea elements:
    + [E1] Master rejects LRS creation (for known or unknown
       reason). In this case another attempt to create a LRS should be
       attempted in 1m or so. This action can be tied with
-      [[I5]](#heading=h.ififs95k9rng). Until the the LRS is created
+      [[I5]](#heading=h.ififs95k9rng). Until the LRS is created
       the situation is the same as [E5]. If this happens multiple
       times all due replicas should be moved elsewhere and later moved
       back once the LRS is created.
diff --git a/contributors/design-proposals/storage/container-storage-interface.md b/contributors/design-proposals/storage/container-storage-interface.md
index 5e85623a..9a1b3d5e 100644
--- a/contributors/design-proposals/storage/container-storage-interface.md
+++ b/contributors/design-proposals/storage/container-storage-interface.md
@@ -201,7 +201,7 @@ Once the following conditions are true, the external-attacher should call `Contr
 Before starting the `ControllerPublishVolume` operation, the external-attacher should add these finalizers to these Kubernetes API objects:
 
 * To the `VolumeAttachment` so that when the object is deleted, the external-attacher has an opportunity to detach the volume first. External attacher removes this finalizer once the volume is fully detached from the node.
-* To the `PersistentVolume` referenced by `VolumeAttachment` so the the PV cannot be deleted while the volume is attached. External attacher needs information from the PV to perform detach operation. The attacher will remove the finalizer once all `VolumeAttachment` objects that refer to the PV are deleted, i.e. the volume is detached from all nodes.
+* To the `PersistentVolume` referenced by `VolumeAttachment` so the PV cannot be deleted while the volume is attached. External attacher needs information from the PV to perform detach operation. The attacher will remove the finalizer once all `VolumeAttachment` objects that refer to the PV are deleted, i.e. the volume is detached from all nodes.
 
 If the operation completes successfully, the external-attacher will:
 
@@ -587,7 +587,7 @@ In order to upgrade drivers using the recommended driver deployment mechanism, t
 #### Deleting Volumes
 
 1. A user deletes a `PersistentVolumeClaim` object bound to a CSI volume.
-2. The external-provisioner for the CSI driver sees the the `PersistentVolumeClaim` was deleted and triggers the retention policy:
+2. The external-provisioner for the CSI driver sees the `PersistentVolumeClaim` was deleted and triggers the retention policy:
   1. If the retention policy is `delete`
     1. The external-provisioner triggers volume deletion by issuing a `DeleteVolume` call against the CSI volume plugin container.
     2. Once the volume is successfully deleted, the external-provisioner deletes the corresponding `PersistentVolume` object.
diff --git a/contributors/guide/owners.md b/contributors/guide/owners.md
index 021d28e8..ea743a61 100644
--- a/contributors/guide/owners.md
+++ b/contributors/guide/owners.md
@@ -84,7 +84,7 @@ filters:
 Instead, set a `.*` key inside `filters` (as shown in the previous example).
 
 **WARNING**: The `approve` plugin [does not currently respect `filters`][test-infra-7690].
-Until that is fixed, `filters` should only be used for the the `labels` key (as shown in the above example).
+Until that is fixed, `filters` should only be used for the `labels` key (as shown in the above example).
 
 ### OWNERS_ALIASES