Remove duplicate words (#7243)

* Remove duplicate words

* Remove generated-reference change

docs/concepts/api-extension/custom-resources.md

@@ -159,7 +159,7 @@ Aggregated APIs offer more advanced API features and customization of other feat
 | Multi-versioning | Allows serving the same object through two API versions. Can help ease API changes like renaming fields. Less important if you control your client versions. | No | Yes |
 | Custom Storage | If you need storage with a different performance mode (for example, time-series database instead of key-value store) or isolation for security (for example, encryption secrets or different | No | Yes |
 | Custom Business Logic | Perform arbitrary checks or actions when creating, reading, updating or deleting an object | No, but can get some of the same effects with Initializers or Finalizers (requires programming) | Yes |
-| Subresources | {::nomarkdown}<ul><li>Add extra operations other than CRUD, such as "scale" or "exec"</li><li>Allows systems like like HorizontalPodAutoscaler and PodDisruptionBudget interact with your new resource</li><li>Finer-grained access control: user writes spec section, controller writes status section.</li><li>Allows incrementing object Generation on custom resource data mutation (requires separate spec and status sections in the resource)</li></ul>{:/} | No but planned | Yes, any Subresource |
+| Subresources | {::nomarkdown}<ul><li>Add extra operations other than CRUD, such as "scale" or "exec"</li><li>Allows systems like HorizontalPodAutoscaler and PodDisruptionBudget interact with your new resource</li><li>Finer-grained access control: user writes spec section, controller writes status section.</li><li>Allows incrementing object Generation on custom resource data mutation (requires separate spec and status sections in the resource)</li></ul>{:/} | No but planned | Yes, any Subresource |
 | strategic-merge-patch | The new endpoints support PATCH with `Content-Type: application/strategic-merge-patch+json`. Useful for updating objects that may be modified both locally, and by the server. For more information, see ["Update API Objects in Place Using kubectl patch"](/docs/tasks/run-application/update-api-object-kubectl-patch/) | No | Yes |
 | Protocol Buffers | The new resource supports clients that want to use Protocol Buffers | No | Yes |
 | OpenAPI Schema | Is there an OpenAPI (swagger) schema for the types that can be dynamically fetched from the server? Is the user protected from misspelling field names by ensuring only allowed fields are set? Are types enforced (in other words, don't put an `int` in a `string` field?) | No but planned | Yes |

docs/concepts/overview/extending.md

@@ -181,7 +181,7 @@ Different networking fabrics can be supported via node-level [Network Plugins](/
 ### Scheduler Extensions
 
 The scheduler is a special type of controller that watches pods, and assigns
-pods to nodes. The default scheduler can be be replaced entirely, while
+pods to nodes. The default scheduler can be replaced entirely, while
 continuing to use other Kubernetes components, or [multiple
 schedulers](/docs/tasks/administer-cluster/configure-multiple-schedulers/)
 can run at the same time.

docs/concepts/overview/object-management-kubectl/declarative-config.md

@@ -517,7 +517,7 @@ Primitive fields are replaced or cleared.
 
 ### Merging changes to map fields
 
-Fields that represent maps are merged by comparing each of the subfields or elements of of the map:
+Fields that represent maps are merged by comparing each of the subfields or elements of the map:
 
 **Note:** '-' is used for "not applicable" because the value is not used.
 

docs/concepts/storage/dynamic-provisioning.md

@@ -30,7 +30,7 @@ that provisioner when provisioning.
 A cluster administrator can define and expose multiple flavors of storage (from
 the same or different storage systems) within a cluster, each with a custom set
 of parameters. This design also ensures that end users don’t have to worry
-about the the complexity and nuances of how storage is provisioned, but still
+about the complexity and nuances of how storage is provisioned, but still
 have the ability to select from multiple storage options.
 
 More information on storage classes can be found

docs/concepts/storage/persistent-volumes.md

@@ -74,7 +74,7 @@ Once a user has a claim and that claim is bound, the bound PV belongs to the use
 {% assign for_k8s_version="v1.9" %}{% include feature-state-alpha.md %}
 The purpose of the PVC protection is to ensure that PVCs in active use by a pod are not removed from the system as this may result in data loss.
 
-**Note:** PVC is in active use by a pod when the the pod status is `Pending` and the pod is assigned to a node or the pod status is `Running`.
+**Note:** PVC is in active use by a pod when the pod status is `Pending` and the pod is assigned to a node or the pod status is `Running`.
 {: .note}
 
 When the [PVC protection alpha feature](/docs/tasks/administer-cluster/pvc-protection/) is enabled, if a user deletes a PVC in active use by a pod, the PVC is not removed immediately. PVC removal is postponed until the PVC is no longer actively used by any pods.

docs/concepts/storage/volumes.md

@@ -239,7 +239,7 @@ A CSI persistent volume has the following fields for users to specify:
   name can have '`.`', '`-`', '`_`' or digits in it.
 - `volumeHandle`: A string value that uniquely identify the volume name returned
   from the CSI volume plugin's `CreateVolume` call. The volume handle is then
-  used in all subsequent calls to the the volume driver for referencing the volume.
+  used in all subsequent calls to the volume driver for referencing the volume.
 - `readOnly`: An optional boolean value indicating whether the volume is to be
   published as read only. Default is false.
 

docs/concepts/workloads/controllers/replicaset.md

@@ -181,7 +181,7 @@ from service for debugging, data recovery, etc. Pods that are removed in this wa
 ### Scaling a ReplicaSet
 
 A ReplicaSet can be easily scaled up or down by simply updating the `.spec.replicas` field. The ReplicaSet controller
-ensures that that a desired number of pods with a matching label selector are available and operational.
+ensures that a desired number of pods with a matching label selector are available and operational.
 
 ### ReplicaSet as an Horizontal Pod Autoscaler Target