fix typos

Author: Takashiidobe

content/en/docs/concepts/cluster-administration/system-metrics.md

@@ -214,7 +214,7 @@ allow-list:
 
 Additionally, the `cardinality_enforcement_unexpected_categorizations_total` meta-metric records the
 count of unexpected categorizations during cardinality enforcement, that is, whenever a label value
-is encountered that is not allowed with respect to the allow-list contraints.
+is encountered that is not allowed with respect to the allow-list constraints.
 
 ## {{% heading "whatsnext" %}}
 

content/en/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md

@@ -114,7 +114,7 @@ The general workflow of a device plugin includes the following steps:
          // informed allocation decision when possible.
          rpc GetPreferredAllocation(PreferredAllocationRequest) returns (PreferredAllocationResponse) {}
 
-         // PreStartContainer is called, if indicated by Device Plugin during registeration phase,
+         // PreStartContainer is called, if indicated by Device Plugin during registration phase,
          // before each container start. Device plugin can run device specific operations
          // such as resetting the device before making devices available to the container.
          rpc PreStartContainer(PreStartContainerRequest) returns (PreStartContainerResponse) {}
@@ -346,7 +346,7 @@ update and Kubelet needs to be restarted to reflect the correct resource capacit
 {{< /note >}}
 
 ```gRPC
-// AllocatableResourcesResponses contains informations about all the devices known by the kubelet
+// AllocatableResourcesResponses contains information about all the devices known by the kubelet
 message AllocatableResourcesResponse {
     repeated ContainerDevices devices = 1;
     repeated int64 cpu_ids = 2;

content/en/docs/concepts/policy/_index.md

@@ -64,5 +64,5 @@ Dynamic Admission Controllers that act as flexible policy engines are being deve
 ## Apply policies using Kubelet configurations
 
 Kubernetes allows configuring the Kubelet on each worker node.  Some Kubelet configurations act as policies:
-* [Process ID limts and reservations](/docs/concepts/policy/pid-limiting/) are used to limit and reserve allocatable PIDs.
+* [Process ID limits and reservations](/docs/concepts/policy/pid-limiting/) are used to limit and reserve allocatable PIDs.
 * [Node Resource Managers](/docs/concepts/policy/node-resource-managers/) can manage compute, memory, and device resources for latency-critical and high-throughput workloads. 

content/en/docs/concepts/security/security-checklist.md

@@ -390,7 +390,7 @@ availability state and recommended to improve your security posture:
 
 [`NodeRestriction`](/docs/reference/access-authn-authz/admission-controllers/#noderestriction)
 : Restricts kubelet's permissions to only modify the pods API resources they own
-or the node API ressource that represent themselves. It also prevents kubelet
+or the node API resource that represent themselves. It also prevents kubelet
 from using the `node-restriction.kubernetes.io/` annotation, which can be used
 by an attacker with access to the kubelet's credentials to influence pod
 placement to the controlled node.

content/en/docs/concepts/services-networking/endpoint-slices.md

@@ -210,7 +210,7 @@ perfectly full distribution of EndpointSlices. As an example, if there are 10
 new endpoints to add and 2 EndpointSlices with room for 5 more endpoints each,
 this approach will create a new EndpointSlice instead of filling up the 2
 existing EndpointSlices. In other words, a single EndpointSlice creation is
-preferrable to multiple EndpointSlice updates.
+preferable to multiple EndpointSlice updates.
 
 With kube-proxy running on each Node and watching EndpointSlices, every change
 to an EndpointSlice becomes relatively expensive since it will be transmitted to

content/en/docs/concepts/workloads/controllers/job.md

@@ -395,7 +395,7 @@ for pod failures independently for each index. To do so, set the
 `.spec.backoffLimitPerIndex` to specify the maximal number of pod failures
 per index.
 
-When the per-index backoff limit is exceeded for an index, Kuberentes considers the index as failed and adds it to the
+When the per-index backoff limit is exceeded for an index, Kubernetes considers the index as failed and adds it to the
 `.status.failedIndexes` field. The succeeded indexes, those with a successfully
 executed pods, are recorded in the `.status.completedIndexes` field, regardless of whether you set
 the `backoffLimitPerIndex` field.
@@ -940,7 +940,7 @@ the Job status, allowing the Pod to be removed by other controllers or users.
 
 {{< note >}}
 See [My pod stays terminating](/docs/tasks/debug/debug-application/debug-pods/) if you
-observe that pods from a Job are stucked with the tracking finalizer.
+observe that pods from a Job are stuck with the tracking finalizer.
 {{< /note >}}
 
 ### Elastic Indexed Jobs

content/en/docs/concepts/workloads/controllers/replicaset.md

@@ -225,7 +225,7 @@ pod1             1/1     Running   0          36s
 pod2             1/1     Running   0          36s
 ```
 
-In this manner, a ReplicaSet can own a non-homogenous set of Pods
+In this manner, a ReplicaSet can own a non-homogeneous set of Pods
 
 ## Writing a ReplicaSet manifest
 

content/en/docs/contribute/style/diagram-guide.md

@@ -624,7 +624,7 @@ caption and the diagram referral.
 flowchart
 A[Diagram<br><br>Inline Mermaid or<br>SVG image files]
 B[Diagram Caption<br><br>Add Figure Number. and<br>Caption Text]
-C[Diagram Referral<br><br>Referenence Figure Number<br>in text]
+C[Diagram Referral<br><br>Reference Figure Number<br>in text]
 
     classDef box fill:#fff,stroke:#000,stroke-width:1px,color:#000;
     class A,B,C box

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

@@ -438,7 +438,7 @@ controller in the cluster, so they have several security features:
   `<signerNameDomain>/*`.
 * Signer-linked ClusterTrustBundles **must** be named with a prefix derived from
   their `spec.signerName` field.  Slashes (`/`) are replaced with colons (`:`),
-  and a final colon is appended.  This is followed by an arbitary name.  For
+  and a final colon is appended.  This is followed by an arbitrary name.  For
   example, the signer `example.com/mysigner` can be linked to a
   ClusterTrustBundle `example.com:mysigner:<arbitrary-name>`.
 

content/en/docs/reference/access-authn-authz/service-accounts-admin.md

@@ -166,7 +166,7 @@ purged by the control plane.
 If users use an invalidated auto-generated token, the token validator will
 
 1. add an audit annotation for the key-value pair
-  `authentication.k8s.io/legacy-token-invalidated: <secret name>/<namepace>`,
+  `authentication.k8s.io/legacy-token-invalidated: <secret name>/<namespace>`,
 1. increment the `invalid_legacy_auto_token_uses_total` metric count,
 1. update the Secret label `kubernetes.io/legacy-token-last-used` with the new
    date,

content/en/docs/reference/access-authn-authz/validating-admission-policy.md

@@ -375,7 +375,7 @@ When an API request is validated with this admission policy, the resulting audit
 ```
 
 In this example the annotation will only be included if the `spec.replicas` of the Deployment is more than
-50, otherwise the CEL expression evalutes to null and the annotation will not be included.
+50, otherwise the CEL expression evaluates to null and the annotation will not be included.
 
 Note that audit annotation keys are prefixed by the name of the `ValidatingAdmissionWebhook` and a `/`. If
 another admission controller, such as an admission webhook, uses the exact same audit annotation key, the 

content/en/docs/reference/command-line-tools-reference/feature-gates/kubelet-pod-resources-dynamice-resources.md

@@ -8,5 +8,5 @@ _build:
 Extend the kubelet's pod resources gRPC endpoint to
 to include resources allocated in `ResourceClaims` via `DynamicResourceAllocation` API.
 See [resource allocation reporting](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources) for more details.
-with informations about the allocatable resources, enabling clients to properly
+with information about the allocatable resources, enabling clients to properly
 track the free compute resources on a node.

content/en/docs/reference/command-line-tools-reference/kubelet.md

@@ -609,7 +609,7 @@ ZeroLimitedNominalConcurrencyShares=true|false (BETA - default=false)<br/>
 <td colspan="2">--kube-reserved strings&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: &lt;None&gt;</td>
 </tr>
 <tr>
-<td></td><td style="line-height: 130%; word-wrap: break-word;">A set of <code>&lt;resource name&gt;=&lt;resource quantity&gt;</code> (e.g. &quot;<code>cpu=200m,memory=500Mi,ephemeral-storage=1Gi,pid='100'</code>&auot;) pairs that describe resources reserved for kubernetes system components. Currently <code>cpu</code>, <code>memory</code> and local <code>ephemeral-storage</code> for root file system are supported. See <a href="https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#kube-reserved">here</a> for more detail. (DEPRECATED: This parameter should be set via the config file specified by the kubelet's <code>--config</code> flag. See <a href="https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/">kubelet-config-file</a> for more information.)</td>
+<td></td><td style="line-height: 130%; word-wrap: break-word;">A set of <code>&lt;resource name&gt;=&lt;resource quantity&gt;</code> (e.g. &quot;<code>cpu=200m,memory=500Mi,ephemeral-storage=1Gi,pid='100'</code>&quot;) pairs that describe resources reserved for kubernetes system components. Currently <code>cpu</code>, <code>memory</code> and local <code>ephemeral-storage</code> for root file system are supported. See <a href="https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#kube-reserved">here</a> for more detail. (DEPRECATED: This parameter should be set via the config file specified by the kubelet's <code>--config</code> flag. See <a href="https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/">kubelet-config-file</a> for more information.)</td>
 </tr>
 
 <tr>
@@ -1087,5 +1087,4 @@ Insecure values:
 <td></td><td style="line-height: 130%; word-wrap: break-word;">Specifies interval for kubelet to calculate and cache the volume disk usage for all pods and volumes. To disable volume calculations, set to a negative number. (DEPRECATED: This parameter should be set via the config file specified by the kubelet's <code>--config</code> flag. See <a href="https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/">kubelet-config-file</a> for more information.)</td>
 </tr>
 </tbody>
-</table>
-
+</table>

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.v1beta4.md

@@ -16,7 +16,7 @@ Use <code>APIServer.ExtraEnvs</code>, <code>ControllerManager.ExtraEnvs</code>,
 <code>Etcd.Local.ExtraEnvs</code>.</li>
 <li>The <code>ResetConfiguration</code> API type is now supported in v1beta4.
 Users are able to reset a node by passing a <code>--config</code> file to <code>kubeadm reset</code>.</li>
-<li><code>dry-run</code> mode is now configureable in InitConfiguration and JoinConfiguration config files.</li>
+<li><code>dry-run</code> mode is now configurable in InitConfiguration and JoinConfiguration config files.</li>
 <li>Replace the existing string/string extra argument maps with structured extra arguments
 that support duplicates. The change applies to <code>ClusterConfiguration</code> - <code>APIServer.ExtraArgs</code>,
 <code>ControllerManager.ExtraArgs</code>, <code>Scheduler.ExtraArgs</code>. Also to <code>NodeRegistrationOptions.KubeletExtraArgs</code>.</li>

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/>

content/en/docs/reference/config-api/kubelet-config.v1beta1.md

@@ -545,7 +545,7 @@ Default: 50</p>
 <td>
    <p>eventBurst is the maximum size of a burst of event creations, temporarily
 allows event creations to burst to this number, while still not exceeding
-eventRecordQPS. This field canot be a negative number and it is only used
+eventRecordQPS. This field cannot be a negative number and it is only used
 when eventRecordQPS &gt; 0.
 Default: 100</p>
 </td>

content/en/docs/reference/config-api/kubelet-credentialprovider.v1.md

@@ -63,7 +63,7 @@ This response should be set to the same apiVersion as CredentialProviderRequest.
 <a href="#credentialprovider-kubelet-k8s-io-v1-PluginCacheKeyType"><code>PluginCacheKeyType</code></a>
 </td>
 <td>
-   <p>cacheKeyType indiciates the type of caching key to use based on the image provided
+   <p>cacheKeyType indicates the type of caching key to use based on the image provided
 in the request. There are three valid values for the cache key type: Image, Registry, and
 Global. If an invalid value is specified, the response will NOT be used by the kubelet.</p>
 </td>

content/en/docs/reference/instrumentation/metrics.md

@@ -1482,14 +1482,14 @@ Alpha metrics do not have any API guarantees. These metrics must be used at your
 	</ul>
 	</div><div class="metric" data-stability="alpha">
 	<div class="metric_name">ephemeral_volume_controller_create_failures_total</div>
-	<div class="metric_help">Number of PersistenVolumeClaims creation requests</div>
+	<div class="metric_help">Number of PersistentVolumeClaims creation requests</div>
 	<ul>
 	<li><label class="metric_detail">Stability Level:</label><span class="metric_stability_level">ALPHA</span></li>
 	<li data-type="counter"><label class="metric_detail">Type:</label> <span class="metric_type">Counter</span></li>
 	</ul>
 	</div><div class="metric" data-stability="alpha">
 	<div class="metric_name">ephemeral_volume_controller_create_total</div>
-	<div class="metric_help">Number of PersistenVolumeClaims creation requests</div>
+	<div class="metric_help">Number of PersistentVolumeClaims creation requests</div>
 	<ul>
 	<li><label class="metric_detail">Stability Level:</label><span class="metric_stability_level">ALPHA</span></li>
 	<li data-type="counter"><label class="metric_detail">Type:</label> <span class="metric_type">Counter</span></li>

content/en/docs/reference/kubernetes-api/cluster-resources/api-service-v1.md

@@ -62,7 +62,7 @@ APIServiceSpec contains information for locating and communicating with a server
 
 - **groupPriorityMinimum** (int32), required
 
-  GroupPriorityMininum is the priority this group should have at least. Higher priority means that the group is preferred by clients over lower priority ones. Note that other versions of this group might specify even higher GroupPriorityMininum values such that the whole group gets a higher priority. The primary sort is based on GroupPriorityMinimum, ordered highest number to lowest (20 before 10). The secondary sort is based on the alphabetical comparison of the name of the object.  (v1.bar before v1.foo) We'd recommend something like: *.k8s.io (except extensions) at 18000 and PaaSes (OpenShift, Deis) are recommended to be in the 2000s
+  GroupPriorityMinimum is the priority this group should have at least. Higher priority means that the group is preferred by clients over lower priority ones. Note that other versions of this group might specify even higher GroupPriorityMinimum values such that the whole group gets a higher priority. The primary sort is based on GroupPriorityMinimum, ordered highest number to lowest (20 before 10). The secondary sort is based on the alphabetical comparison of the name of the object.  (v1.bar before v1.foo) We'd recommend something like: *.k8s.io (except extensions) at 18000 and PaaSes (OpenShift, Deis) are recommended to be in the 2000s
 
 - **versionPriority** (int32), required