Skip to content

docs: fix typos in concepts documentation #9429

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Archong-Liu wants to merge 3 commits into
base: main
Choose a base branch
from
Open

docs: fix typos in concepts documentation #9429

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
955c901
docs: fix typos in concepts documentation
Archong-Liu Jul 19, 2026
d204706
docs: replicate typo fixes to preview and versioned docs
Archong-Liu Jul 22, 2026
380c523
Merge branch 'main' into docs/fix-concepts-typos
Archong-Liu Jul 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions website/content/en/docs/concepts/disruption.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions website/content/en/docs/concepts/nodeclasses.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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" %}}
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/docs/concepts/nodepools.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/docs/concepts/scheduling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down