diff options
| -rw-r--r-- | contributors/design-proposals/architecture/0000-kep-template.md | 2 | ||||
| -rw-r--r-- | contributors/design-proposals/architecture/1-kubernetes-enhancement-proposal-process.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/contributors/design-proposals/architecture/0000-kep-template.md b/contributors/design-proposals/architecture/0000-kep-template.md index 76d57fbd..8ba4da4a 100644 --- a/contributors/design-proposals/architecture/0000-kep-template.md +++ b/contributors/design-proposals/architecture/0000-kep-template.md @@ -165,7 +165,7 @@ Major milestones in the life cycle of a KEP should be tracked in design - the date implementation started - the first Kubernetes release where an initial version of the KEP was available -- the version of Kubneretes where the KEP graduated to general availability +- the version of Kubernetes where the KEP graduated to general availability - when the KEP was retired or superseded ## Drawbacks [optional] diff --git a/contributors/design-proposals/architecture/1-kubernetes-enhancement-proposal-process.md b/contributors/design-proposals/architecture/1-kubernetes-enhancement-proposal-process.md index ecea9a00..ff50b829 100644 --- a/contributors/design-proposals/architecture/1-kubernetes-enhancement-proposal-process.md +++ b/contributors/design-proposals/architecture/1-kubernetes-enhancement-proposal-process.md @@ -289,7 +289,7 @@ with the following example structure │ └── retired ├── sig-node │ ├── deferred -│ ├── kublet +│ ├── kubelet │ ├── orphaned │ └── retired ├── sig-release |