diff --git a/website/content/en/docs/concepts/disruption.md b/website/content/en/docs/concepts/disruption.md
index e1b04af71a79..e76ad889af34 100644
--- a/website/content/en/docs/concepts/disruption.md
+++ b/website/content/en/docs/concepts/disruption.md
@@ -52,7 +52,7 @@ When a Karpenter node is deleted, the Karpenter finalizer will block deletion an
     # Delete all nodes owned by any nodepool
     kubectl delete nodes -l karpenter.sh/nodepool
 
-    # Delete all nodeclaims owned by a specific nodepoolXS
+    # Delete all nodeclaims owned by a specific nodepool
     kubectl delete nodeclaims -l karpenter.sh/nodepool=$NODEPOOL_NAME
     ```
 * **NodePool Deletion**: NodeClaims are owned by the NodePool through an [owner reference](https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/#owner-references-in-object-specifications) that launched them. Karpenter will gracefully terminate nodes through cascading deletion when the owning NodePool is deleted.
@@ -309,7 +309,7 @@ A pod with the `karpenter.sh/do-not-disrupt` annotation and a 300 second (5 minu
 If the pod is still running 55 minutes after the Node begins to drain, the pod will be deleted to ensure its `terminationGracePeriodSeconds` value is respected.
 
 If a pod's `terminationGracePeriodSeconds` value exceeds that of the Node it is scheduled to, Karpenter will prioritize the Node's `terminationGracePeriod`.
-The pod will be deleted as soon as the Node begins to drain, and it will not receive it's full `terminationGracePeriodSeconds`.
+The pod will be deleted as soon as the Node begins to drain, and it will not receive its full `terminationGracePeriodSeconds`.
 {{% /alert %}}
 
 ### NodePool Disruption Budgets
diff --git a/website/content/en/docs/concepts/nodeclasses.md b/website/content/en/docs/concepts/nodeclasses.md
index 8a9c7dc4ceaf..8bf56b9aa97a 100644
--- a/website/content/en/docs/concepts/nodeclasses.md
+++ b/website/content/en/docs/concepts/nodeclasses.md
@@ -57,7 +57,7 @@ spec:
     cpuCFSQuota: true
     clusterDNS: ["10.0.1.100"]
   # Optional, dictates UserData generation and default block device mappings.
-  # May be ommited when using an `alias` amiSelectorTerm, otherwise required.
+  # May be omitted when using an `alias` amiSelectorTerm, otherwise required.
   amiFamily: AL2
 
   # Required, discovers subnets to attach to instances
@@ -792,7 +792,7 @@ alias: bottlerocket@v1.20.4
 ```
 The Windows family does not support pinning, so only `latest` is supported.
 
-The following commands can be used to determine the versions availble for an alias in your region:
+The following commands can be used to determine the versions available for an alias in your region:
 
 {{< tabpane text=true right=false >}}
   {{% tab "AL2023" %}}
diff --git a/website/content/en/docs/concepts/nodepools.md b/website/content/en/docs/concepts/nodepools.md
index 1ff498d7412d..17fa415b89ca 100644
--- a/website/content/en/docs/concepts/nodepools.md
+++ b/website/content/en/docs/concepts/nodepools.md
@@ -194,7 +194,7 @@ See [Taints and Tolerations](https://kubernetes.io/docs/concepts/scheduling-evic
 
 ## spec.template.spec.startupTaints
 
-Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node is can be initialized.
+Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node can be initialized.
 These taints must be cleared before pods can be deployed to a node.
 
 ## spec.template.spec.expireAfter
diff --git a/website/content/en/docs/concepts/scheduling.md b/website/content/en/docs/concepts/scheduling.md
index d1288fc51bc3..cc7b6cc0430c 100755
--- a/website/content/en/docs/concepts/scheduling.md
+++ b/website/content/en/docs/concepts/scheduling.md
@@ -23,7 +23,7 @@ For example, if the NodePool sets limits that allow only a particular zone to be
 Constraints you can request include:
 
 * **Resource requests**: Request that certain amount of memory or CPU be available.
-* **Node selection**: Choose to run on a node that is has a particular label (`nodeSelector`).
+* **Node selection**: Choose to run on a node that has a particular label (`nodeSelector`).
 * **Node affinity**: Draws a pod to run on nodes with particular attributes (affinity).
 * **Topology spread**: Use topology spread to help ensure availability of the application.
 * **Pod affinity/anti-affinity**: Draws pods towards or away from topology domains based on the scheduling of other pods.
diff --git a/website/content/en/preview/concepts/disruption.md b/website/content/en/preview/concepts/disruption.md
index 736bbf07b555..f06ab94d6af1 100644
--- a/website/content/en/preview/concepts/disruption.md
+++ b/website/content/en/preview/concepts/disruption.md
@@ -52,7 +52,7 @@ When a Karpenter node is deleted, the Karpenter finalizer will block deletion an
     # Delete all nodes owned by any nodepool
     kubectl delete nodes -l karpenter.sh/nodepool
 
-    # Delete all nodeclaims owned by a specific nodepoolXS
+    # Delete all nodeclaims owned by a specific nodepool
     kubectl delete nodeclaims -l karpenter.sh/nodepool=$NODEPOOL_NAME
     ```
 * **NodePool Deletion**: NodeClaims are owned by the NodePool through an [owner reference](https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/#owner-references-in-object-specifications) that launched them. Karpenter will gracefully terminate nodes through cascading deletion when the owning NodePool is deleted.
@@ -309,7 +309,7 @@ A pod with the `karpenter.sh/do-not-disrupt` annotation and a 300 second (5 minu
 If the pod is still running 55 minutes after the Node begins to drain, the pod will be deleted to ensure its `terminationGracePeriodSeconds` value is respected.
 
 If a pod's `terminationGracePeriodSeconds` value exceeds that of the Node it is scheduled to, Karpenter will prioritize the Node's `terminationGracePeriod`.
-The pod will be deleted as soon as the Node begins to drain, and it will not receive it's full `terminationGracePeriodSeconds`.
+The pod will be deleted as soon as the Node begins to drain, and it will not receive its full `terminationGracePeriodSeconds`.
 {{% /alert %}}
 
 ### NodePool Disruption Budgets
diff --git a/website/content/en/preview/concepts/nodeclasses.md b/website/content/en/preview/concepts/nodeclasses.md
index 9ca16acf543c..9ec318924eff 100644
--- a/website/content/en/preview/concepts/nodeclasses.md
+++ b/website/content/en/preview/concepts/nodeclasses.md
@@ -57,7 +57,7 @@ spec:
     cpuCFSQuota: true
     clusterDNS: ["10.0.1.100"]
   # Optional, dictates UserData generation and default block device mappings.
-  # May be ommited when using an `alias` amiSelectorTerm, otherwise required.
+  # May be omitted when using an `alias` amiSelectorTerm, otherwise required.
   amiFamily: AL2
 
   # Required, discovers subnets to attach to instances
@@ -792,7 +792,7 @@ alias: bottlerocket@v1.20.4
 ```
 The Windows family does not support pinning, so only `latest` is supported.
 
-The following commands can be used to determine the versions availble for an alias in your region:
+The following commands can be used to determine the versions available for an alias in your region:
 
 {{< tabpane text=true right=false >}}
   {{% tab "AL2023" %}}
diff --git a/website/content/en/preview/concepts/nodepools.md b/website/content/en/preview/concepts/nodepools.md
index 1ff498d7412d..17fa415b89ca 100644
--- a/website/content/en/preview/concepts/nodepools.md
+++ b/website/content/en/preview/concepts/nodepools.md
@@ -194,7 +194,7 @@ See [Taints and Tolerations](https://kubernetes.io/docs/concepts/scheduling-evic
 
 ## spec.template.spec.startupTaints
 
-Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node is can be initialized.
+Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node can be initialized.
 These taints must be cleared before pods can be deployed to a node.
 
 ## spec.template.spec.expireAfter
diff --git a/website/content/en/preview/concepts/scheduling.md b/website/content/en/preview/concepts/scheduling.md
index d1288fc51bc3..cc7b6cc0430c 100755
--- a/website/content/en/preview/concepts/scheduling.md
+++ b/website/content/en/preview/concepts/scheduling.md
@@ -23,7 +23,7 @@ For example, if the NodePool sets limits that allow only a particular zone to be
 Constraints you can request include:
 
 * **Resource requests**: Request that certain amount of memory or CPU be available.
-* **Node selection**: Choose to run on a node that is has a particular label (`nodeSelector`).
+* **Node selection**: Choose to run on a node that has a particular label (`nodeSelector`).
 * **Node affinity**: Draws a pod to run on nodes with particular attributes (affinity).
 * **Topology spread**: Use topology spread to help ensure availability of the application.
 * **Pod affinity/anti-affinity**: Draws pods towards or away from topology domains based on the scheduling of other pods.
diff --git a/website/content/en/v1.0/concepts/disruption.md b/website/content/en/v1.0/concepts/disruption.md
index edc069dcdfdb..4c532b072a66 100644
--- a/website/content/en/v1.0/concepts/disruption.md
+++ b/website/content/en/v1.0/concepts/disruption.md
@@ -52,7 +52,7 @@ When a Karpenter node is deleted, the Karpenter finalizer will block deletion an
     # Delete all nodes owned by any nodepool
     kubectl delete nodes -l karpenter.sh/nodepool
 
-    # Delete all nodeclaims owned by a specific nodepoolXS
+    # Delete all nodeclaims owned by a specific nodepool
     kubectl delete nodeclaims -l karpenter.sh/nodepool=$NODEPOOL_NAME
     ```
 * **NodePool Deletion**: NodeClaims are owned by the NodePool through an [owner reference](https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/#owner-references-in-object-specifications) that launched them. Karpenter will gracefully terminate nodes through cascading deletion when the owning NodePool is deleted.
@@ -244,7 +244,7 @@ A pod with the `karpenter.sh/do-not-disrupt` annotation and a 300 second (5 minu
 
 If the pod is still running 55 minutes after the Node begins to drain, the pod will be deleted to ensure its `terminationGracePeriodSeconds` value is respected.
 If a pod's `terminationGracePeriodSeconds` value exceeds that of the Node it is scheduled to, Karpenter will prioritize the Node's `terminationGracePeriod`.
-The pod will be deleted as soon as the Node begins to drain, and it will not receive it's full `terminationGracePeriodSeconds`.
+The pod will be deleted as soon as the Node begins to drain, and it will not receive its full `terminationGracePeriodSeconds`.
 {{% /alert %}}
 
 ### NodePool Disruption Budgets
diff --git a/website/content/en/v1.0/concepts/nodeclasses.md b/website/content/en/v1.0/concepts/nodeclasses.md
index e55ef0d2c981..cde35c346358 100644
--- a/website/content/en/v1.0/concepts/nodeclasses.md
+++ b/website/content/en/v1.0/concepts/nodeclasses.md
@@ -57,7 +57,7 @@ spec:
     cpuCFSQuota: true
     clusterDNS: ["10.0.1.100"]
   # Optional, dictates UserData generation and default block device mappings.
-  # May be ommited when using an `alias` amiSelectorTerm, otherwise required.
+  # May be omitted when using an `alias` amiSelectorTerm, otherwise required.
   amiFamily: AL2
 
   # Required, discovers subnets to attach to instances
@@ -736,7 +736,7 @@ alias: bottlerocket@v1.20.4
 ```
 The Windows family does not support pinning, so only `latest` is supported.
 
-The following commands can be used to determine the versions availble for an alias in your region:
+The following commands can be used to determine the versions available for an alias in your region:
 
 {{< tabpane text=true right=false >}}
   {{% tab "AL2023" %}}
diff --git a/website/content/en/v1.0/concepts/nodepools.md b/website/content/en/v1.0/concepts/nodepools.md
index b73352c446ce..89e318ccb304 100644
--- a/website/content/en/v1.0/concepts/nodepools.md
+++ b/website/content/en/v1.0/concepts/nodepools.md
@@ -183,7 +183,7 @@ See [Taints and Tolerations](https://kubernetes.io/docs/concepts/scheduling-evic
 
 ## spec.template.spec.startupTaints
 
-Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node is can be initialized.
+Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node can be initialized.
 These taints must be cleared before pods can be deployed to a node.
 
 ## spec.template.spec.expireAfter
diff --git a/website/content/en/v1.0/concepts/scheduling.md b/website/content/en/v1.0/concepts/scheduling.md
index f0e460aa6848..10de065d4b7e 100755
--- a/website/content/en/v1.0/concepts/scheduling.md
+++ b/website/content/en/v1.0/concepts/scheduling.md
@@ -23,7 +23,7 @@ For example, if the NodePool sets limits that allow only a particular zone to be
 Constraints you can request include:
 
 * **Resource requests**: Request that certain amount of memory or CPU be available.
-* **Node selection**: Choose to run on a node that is has a particular label (`nodeSelector`).
+* **Node selection**: Choose to run on a node that has a particular label (`nodeSelector`).
 * **Node affinity**: Draws a pod to run on nodes with particular attributes (affinity).
 * **Topology spread**: Use topology spread to help ensure availability of the application.
 * **Pod affinity/anti-affinity**: Draws pods towards or away from topology domains based on the scheduling of other pods.
diff --git a/website/content/en/v1.12/concepts/disruption.md b/website/content/en/v1.12/concepts/disruption.md
index 1d6e614e9337..c0b1a122c671 100644
--- a/website/content/en/v1.12/concepts/disruption.md
+++ b/website/content/en/v1.12/concepts/disruption.md
@@ -52,7 +52,7 @@ When a Karpenter node is deleted, the Karpenter finalizer will block deletion an
     # Delete all nodes owned by any nodepool
     kubectl delete nodes -l karpenter.sh/nodepool
 
-    # Delete all nodeclaims owned by a specific nodepoolXS
+    # Delete all nodeclaims owned by a specific nodepool
     kubectl delete nodeclaims -l karpenter.sh/nodepool=$NODEPOOL_NAME
     ```
 * **NodePool Deletion**: NodeClaims are owned by the NodePool through an [owner reference](https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/#owner-references-in-object-specifications) that launched them. Karpenter will gracefully terminate nodes through cascading deletion when the owning NodePool is deleted.
@@ -287,7 +287,7 @@ A pod with the `karpenter.sh/do-not-disrupt` annotation and a 300 second (5 minu
 If the pod is still running 55 minutes after the Node begins to drain, the pod will be deleted to ensure its `terminationGracePeriodSeconds` value is respected.
 
 If a pod's `terminationGracePeriodSeconds` value exceeds that of the Node it is scheduled to, Karpenter will prioritize the Node's `terminationGracePeriod`.
-The pod will be deleted as soon as the Node begins to drain, and it will not receive it's full `terminationGracePeriodSeconds`.
+The pod will be deleted as soon as the Node begins to drain, and it will not receive its full `terminationGracePeriodSeconds`.
 {{% /alert %}}
 
 ### NodePool Disruption Budgets
diff --git a/website/content/en/v1.12/concepts/nodeclasses.md b/website/content/en/v1.12/concepts/nodeclasses.md
index e43c3bf6574f..204fe5f203d0 100644
--- a/website/content/en/v1.12/concepts/nodeclasses.md
+++ b/website/content/en/v1.12/concepts/nodeclasses.md
@@ -57,7 +57,7 @@ spec:
     cpuCFSQuota: true
     clusterDNS: ["10.0.1.100"]
   # Optional, dictates UserData generation and default block device mappings.
-  # May be ommited when using an `alias` amiSelectorTerm, otherwise required.
+  # May be omitted when using an `alias` amiSelectorTerm, otherwise required.
   amiFamily: AL2
 
   # Required, discovers subnets to attach to instances
@@ -782,7 +782,7 @@ alias: bottlerocket@v1.20.4
 ```
 The Windows family does not support pinning, so only `latest` is supported.
 
-The following commands can be used to determine the versions availble for an alias in your region:
+The following commands can be used to determine the versions available for an alias in your region:
 
 {{< tabpane text=true right=false >}}
   {{% tab "AL2023" %}}
diff --git a/website/content/en/v1.12/concepts/nodepools.md b/website/content/en/v1.12/concepts/nodepools.md
index 153cbfc7cc83..f052a3b58c3a 100644
--- a/website/content/en/v1.12/concepts/nodepools.md
+++ b/website/content/en/v1.12/concepts/nodepools.md
@@ -193,7 +193,7 @@ See [Taints and Tolerations](https://kubernetes.io/docs/concepts/scheduling-evic
 
 ## spec.template.spec.startupTaints
 
-Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node is can be initialized.
+Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node can be initialized.
 These taints must be cleared before pods can be deployed to a node.
 
 ## spec.template.spec.expireAfter
diff --git a/website/content/en/v1.12/concepts/scheduling.md b/website/content/en/v1.12/concepts/scheduling.md
index d1288fc51bc3..cc7b6cc0430c 100755
--- a/website/content/en/v1.12/concepts/scheduling.md
+++ b/website/content/en/v1.12/concepts/scheduling.md
@@ -23,7 +23,7 @@ For example, if the NodePool sets limits that allow only a particular zone to be
 Constraints you can request include:
 
 * **Resource requests**: Request that certain amount of memory or CPU be available.
-* **Node selection**: Choose to run on a node that is has a particular label (`nodeSelector`).
+* **Node selection**: Choose to run on a node that has a particular label (`nodeSelector`).
 * **Node affinity**: Draws a pod to run on nodes with particular attributes (affinity).
 * **Topology spread**: Use topology spread to help ensure availability of the application.
 * **Pod affinity/anti-affinity**: Draws pods towards or away from topology domains based on the scheduling of other pods.
diff --git a/website/content/en/v1.13/concepts/disruption.md b/website/content/en/v1.13/concepts/disruption.md
index 1d6e614e9337..c0b1a122c671 100644
--- a/website/content/en/v1.13/concepts/disruption.md
+++ b/website/content/en/v1.13/concepts/disruption.md
@@ -52,7 +52,7 @@ When a Karpenter node is deleted, the Karpenter finalizer will block deletion an
     # Delete all nodes owned by any nodepool
     kubectl delete nodes -l karpenter.sh/nodepool
 
-    # Delete all nodeclaims owned by a specific nodepoolXS
+    # Delete all nodeclaims owned by a specific nodepool
     kubectl delete nodeclaims -l karpenter.sh/nodepool=$NODEPOOL_NAME
     ```
 * **NodePool Deletion**: NodeClaims are owned by the NodePool through an [owner reference](https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/#owner-references-in-object-specifications) that launched them. Karpenter will gracefully terminate nodes through cascading deletion when the owning NodePool is deleted.
@@ -287,7 +287,7 @@ A pod with the `karpenter.sh/do-not-disrupt` annotation and a 300 second (5 minu
 If the pod is still running 55 minutes after the Node begins to drain, the pod will be deleted to ensure its `terminationGracePeriodSeconds` value is respected.
 
 If a pod's `terminationGracePeriodSeconds` value exceeds that of the Node it is scheduled to, Karpenter will prioritize the Node's `terminationGracePeriod`.
-The pod will be deleted as soon as the Node begins to drain, and it will not receive it's full `terminationGracePeriodSeconds`.
+The pod will be deleted as soon as the Node begins to drain, and it will not receive its full `terminationGracePeriodSeconds`.
 {{% /alert %}}
 
 ### NodePool Disruption Budgets
diff --git a/website/content/en/v1.13/concepts/nodeclasses.md b/website/content/en/v1.13/concepts/nodeclasses.md
index 57bf68b1a25b..71b61b55d352 100644
--- a/website/content/en/v1.13/concepts/nodeclasses.md
+++ b/website/content/en/v1.13/concepts/nodeclasses.md
@@ -57,7 +57,7 @@ spec:
     cpuCFSQuota: true
     clusterDNS: ["10.0.1.100"]
   # Optional, dictates UserData generation and default block device mappings.
-  # May be ommited when using an `alias` amiSelectorTerm, otherwise required.
+  # May be omitted when using an `alias` amiSelectorTerm, otherwise required.
   amiFamily: AL2
 
   # Required, discovers subnets to attach to instances
@@ -792,7 +792,7 @@ alias: bottlerocket@v1.20.4
 ```
 The Windows family does not support pinning, so only `latest` is supported.
 
-The following commands can be used to determine the versions availble for an alias in your region:
+The following commands can be used to determine the versions available for an alias in your region:
 
 {{< tabpane text=true right=false >}}
   {{% tab "AL2023" %}}
diff --git a/website/content/en/v1.13/concepts/nodepools.md b/website/content/en/v1.13/concepts/nodepools.md
index 33aad1d389da..e9e893b49923 100644
--- a/website/content/en/v1.13/concepts/nodepools.md
+++ b/website/content/en/v1.13/concepts/nodepools.md
@@ -193,7 +193,7 @@ See [Taints and Tolerations](https://kubernetes.io/docs/concepts/scheduling-evic
 
 ## spec.template.spec.startupTaints
 
-Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node is can be initialized.
+Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node can be initialized.
 These taints must be cleared before pods can be deployed to a node.
 
 ## spec.template.spec.expireAfter
diff --git a/website/content/en/v1.13/concepts/scheduling.md b/website/content/en/v1.13/concepts/scheduling.md
index d1288fc51bc3..cc7b6cc0430c 100755
--- a/website/content/en/v1.13/concepts/scheduling.md
+++ b/website/content/en/v1.13/concepts/scheduling.md
@@ -23,7 +23,7 @@ For example, if the NodePool sets limits that allow only a particular zone to be
 Constraints you can request include:
 
 * **Resource requests**: Request that certain amount of memory or CPU be available.
-* **Node selection**: Choose to run on a node that is has a particular label (`nodeSelector`).
+* **Node selection**: Choose to run on a node that has a particular label (`nodeSelector`).
 * **Node affinity**: Draws a pod to run on nodes with particular attributes (affinity).
 * **Topology spread**: Use topology spread to help ensure availability of the application.
 * **Pod affinity/anti-affinity**: Draws pods towards or away from topology domains based on the scheduling of other pods.
diff --git a/website/content/en/v1.14/concepts/disruption.md b/website/content/en/v1.14/concepts/disruption.md
index 736bbf07b555..f06ab94d6af1 100644
--- a/website/content/en/v1.14/concepts/disruption.md
+++ b/website/content/en/v1.14/concepts/disruption.md
@@ -52,7 +52,7 @@ When a Karpenter node is deleted, the Karpenter finalizer will block deletion an
     # Delete all nodes owned by any nodepool
     kubectl delete nodes -l karpenter.sh/nodepool
 
-    # Delete all nodeclaims owned by a specific nodepoolXS
+    # Delete all nodeclaims owned by a specific nodepool
     kubectl delete nodeclaims -l karpenter.sh/nodepool=$NODEPOOL_NAME
     ```
 * **NodePool Deletion**: NodeClaims are owned by the NodePool through an [owner reference](https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/#owner-references-in-object-specifications) that launched them. Karpenter will gracefully terminate nodes through cascading deletion when the owning NodePool is deleted.
@@ -309,7 +309,7 @@ A pod with the `karpenter.sh/do-not-disrupt` annotation and a 300 second (5 minu
 If the pod is still running 55 minutes after the Node begins to drain, the pod will be deleted to ensure its `terminationGracePeriodSeconds` value is respected.
 
 If a pod's `terminationGracePeriodSeconds` value exceeds that of the Node it is scheduled to, Karpenter will prioritize the Node's `terminationGracePeriod`.
-The pod will be deleted as soon as the Node begins to drain, and it will not receive it's full `terminationGracePeriodSeconds`.
+The pod will be deleted as soon as the Node begins to drain, and it will not receive its full `terminationGracePeriodSeconds`.
 {{% /alert %}}
 
 ### NodePool Disruption Budgets
diff --git a/website/content/en/v1.14/concepts/nodeclasses.md b/website/content/en/v1.14/concepts/nodeclasses.md
index 8a9c7dc4ceaf..8bf56b9aa97a 100644
--- a/website/content/en/v1.14/concepts/nodeclasses.md
+++ b/website/content/en/v1.14/concepts/nodeclasses.md
@@ -57,7 +57,7 @@ spec:
     cpuCFSQuota: true
     clusterDNS: ["10.0.1.100"]
   # Optional, dictates UserData generation and default block device mappings.
-  # May be ommited when using an `alias` amiSelectorTerm, otherwise required.
+  # May be omitted when using an `alias` amiSelectorTerm, otherwise required.
   amiFamily: AL2
 
   # Required, discovers subnets to attach to instances
@@ -792,7 +792,7 @@ alias: bottlerocket@v1.20.4
 ```
 The Windows family does not support pinning, so only `latest` is supported.
 
-The following commands can be used to determine the versions availble for an alias in your region:
+The following commands can be used to determine the versions available for an alias in your region:
 
 {{< tabpane text=true right=false >}}
   {{% tab "AL2023" %}}
diff --git a/website/content/en/v1.14/concepts/nodepools.md b/website/content/en/v1.14/concepts/nodepools.md
index 1ff498d7412d..17fa415b89ca 100644
--- a/website/content/en/v1.14/concepts/nodepools.md
+++ b/website/content/en/v1.14/concepts/nodepools.md
@@ -194,7 +194,7 @@ See [Taints and Tolerations](https://kubernetes.io/docs/concepts/scheduling-evic
 
 ## spec.template.spec.startupTaints
 
-Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node is can be initialized.
+Taints that are added to nodes to indicate that a certain condition must be met, such as starting an agent or setting up networking, before the node can be initialized.
 These taints must be cleared before pods can be deployed to a node.
 
 ## spec.template.spec.expireAfter
diff --git a/website/content/en/v1.14/concepts/scheduling.md b/website/content/en/v1.14/concepts/scheduling.md
index d1288fc51bc3..cc7b6cc0430c 100755
--- a/website/content/en/v1.14/concepts/scheduling.md
+++ b/website/content/en/v1.14/concepts/scheduling.md
@@ -23,7 +23,7 @@ For example, if the NodePool sets limits that allow only a particular zone to be
 Constraints you can request include:
 
 * **Resource requests**: Request that certain amount of memory or CPU be available.
-* **Node selection**: Choose to run on a node that is has a particular label (`nodeSelector`).
+* **Node selection**: Choose to run on a node that has a particular label (`nodeSelector`).
 * **Node affinity**: Draws a pod to run on nodes with particular attributes (affinity).
 * **Topology spread**: Use topology spread to help ensure availability of the application.
 * **Pod affinity/anti-affinity**: Draws pods towards or away from topology domains based on the scheduling of other pods.