fix: typos

Author: JPBotelho

content/en/docs/concepts/cluster-administration/admission-webhooks-good-practices.md

@@ -475,7 +475,7 @@ changes:
 ### Ensure that the mutating webhooks in your cluster are idempotent {#ensure-mutating-webhook-idempotent}
 
 Every mutating admission webhook should be _idempotent_. The webhook should be
-able to run on an object that it already modifed without making additional
+able to run on an object that it already modified without making additional
 changes beyond the original change.
 
 Additionally, all of the mutating webhooks in your cluster should, as a

content/en/docs/concepts/scheduling-eviction/node-pressure-eviction.md

@@ -229,7 +229,7 @@ then the values of other parameters will not be inherited as the default
 values and will be set to zero. In order to provide custom values, you
 should provide all the thresholds respectively. You can also set the kubelet config
 MergeDefaultEvictionSettings to true in the kubelet configuration file.
-If set to true and any paramater is changed, then the other parameters will
+If set to true and any parameter is changed, then the other parameters will
 inherit their default values instead of 0.
 
 The `containerfs.available` and `containerfs.inodesFree` (Linux nodes) default

content/en/docs/concepts/workloads/pods/pod-lifecycle.md

@@ -287,7 +287,7 @@ explains the behaviour of `init containers` when specify `restartpolicy` field o
 feature_gate_name="ContainerRestartRules" >}}
 
 If your cluster has the feature gate `ContainerRestartRules` enabled, you can specify 
-`restartPolicy` and `restartPolicyRules` on _inidividual containers_ to override the Pod
+`restartPolicy` and `restartPolicyRules` on _individual containers_ to override the Pod
 restart policy. Container restart policy and rules applies to {{< glossary_tooltip text="app containers" term_id="app-container" >}}
 in the Pod and to regular [init containers](/docs/concepts/workloads/pods/init-containers/).
 
@@ -331,7 +331,7 @@ spec:
 ```
 
 A Pod with Always restart policy with an init container that only execute once. If the init
-container fails, the Pod fails. This alllows the Pod to fail if the initialiaztion failed,
+container fails, the Pod fails. This allows the Pod to fail if the initialiaztion failed,
 but also keep running once the initialization succeeds:
 
 ```yaml

content/en/docs/reference/access-authn-authz/authentication.md

@@ -243,7 +243,7 @@ Read [X.509 client certificates](#x509-client-certificates) to learn about how t
 certificate.
 
 If you do issue certificates to clients, it is up to you (as a cloud platform administrator)
-to make sure that the certicate validity period, and other design choices you make, provide a
+to make sure that the certificate validity period, and other design choices you make, provide a
 suitable level of security.
 
 ### OpenID Connect tokens

content/en/docs/reference/access-authn-authz/certificate-signing-requests.md

@@ -112,7 +112,7 @@ Signers abstractly represent the entity or entities that might sign, or have
 signed, a security certificate.
 
 Any signer that is made available for outside a particular cluster should provide information
-about how the signer works, so that consumers can understand what that means for CertifcateSigningRequests
+about how the signer works, so that consumers can understand what that means for CertificateSigningRequests
 and (if enabled) [ClusterTrustBundles](#cluster-trust-bundles).
 This includes:
 

content/en/docs/reference/command-line-tools-reference/feature-gates/ReloadKubeletServerCertificateFile.md

@@ -14,4 +14,4 @@ stages:
 Enable the kubelet TLS server to update its certificate if the specified certificate file are changed.
 
 This feature is useful when specifying `tlsCertFile` and `tlsPrivateKeyFile` in kubelet configuration.
-The feature gate has no effect for other cases such as using TLS boostrap.
+The feature gate has no effect for other cases such as using TLS bootstrap.

content/en/docs/reference/command-line-tools-reference/feature-gates/SchedulerQueueingHints.md

@@ -23,7 +23,7 @@ stages:
  fromVersion: "1.34"
 ---
 Enables scheduler [queueing hints](/docs/concepts/scheduling-eviction/scheduling-framework/#queueinghint),
-which benefits to reduce the useless requeueing.
+which benefits to reduce the useless requeuing.
 The scheduler retries scheduling pods if something changes in the cluster that could make the pod scheduled.
 Queueing hints are internal signals that allow the scheduler to filter the changes in the cluster
 that are relevant to the unscheduled pod, based on previous scheduling attempts.

content/en/docs/reference/config-api/apiserver-audit.v1.md

@@ -253,7 +253,7 @@ be specified per rule in which case the union of both are omitted.</p>
 <td>
  <p>OmitManagedFields indicates whether to omit the managed fields of the request
 and response bodies from being written to the API audit log.
-This is used as a global default - a value of 'true' will omit the managed fileds,
+This is used as a global default - a value of 'true' will omit the managed fields,
 otherwise the managed fields will be included in the API audit log.
 Note that this can also be specified per rule in which case the value specified
 in a rule will override the global default.</p>
@@ -527,7 +527,7 @@ An empty list means no restrictions will apply.</p>
 and response bodies from being written to the API audit log.</p>
 <ul>
 <li>a value of 'true' will drop the managed fields from the API audit log</li>
-<li>a value of 'false' indicates that the managed fileds should be included
+<li>a value of 'false' indicates that the managed fields should be included
 in the API audit log
 Note that the value, if specified, in this rule will override the global default
 If a value is not specified then the global default specified in

content/en/docs/reference/config-api/kubeadm-config.v1beta3.md

@@ -591,7 +591,7 @@ control-plane node to the cluster.</p>
 </td>
 <td>
  <p><code>caCertPath</code> is the path to the SSL certificate authority used to secure
-comunications between a node and the control-plane.
+communications between a node and the control-plane.
 Defaults to &quot;/etc/kubernetes/pki/ca.crt&quot;.</p>
 </td>
 </tr>

content/en/docs/reference/config-api/kubeconfig.v1.md

@@ -55,21 +55,21 @@ TODO(jlowdermilk): remove this after eliminating downstream dependencies.</p>
 <a href="#NamedCluster"><code>[]NamedCluster</code></a>
 </td>
 <td>
- <p>Clusters is a map of referencable names to cluster configs</p>
+ <p>Clusters is a map of referenceable names to cluster configs</p>
 </td>
 </tr>
 <tr><td><code>users</code> <B>[Required]</B><br/>
 <a href="#NamedAuthInfo"><code>[]NamedAuthInfo</code></a>
 </td>
 <td>
- <p>AuthInfos is a map of referencable names to user configs</p>
+ <p>AuthInfos is a map of referenceable names to user configs</p>
 </td>
 </tr>
 <tr><td><code>contexts</code> <B>[Required]</B><br/>
 <a href="#NamedContext"><code>[]NamedContext</code></a>
 </td>
 <td>
- <p>Contexts is a map of referencable names to context configs</p>
+ <p>Contexts is a map of referenceable names to context configs</p>
 </td>
 </tr>
 <tr><td><code>current-context</code> <B>[Required]</B><br/>