Skip to content

Commit 451149c

Browse files
authored
Merge pull request kubernetes#2765 from kubernetes/divya-mohan0209-patch-1
Update README.md
2 parents 662e455 + e49d911 commit 451149c

File tree

1 file changed

+3
-3
lines changed
  • keps/sig-release/2572-release-cadence

1 file changed

+3
-3
lines changed

keps/sig-release/2572-release-cadence/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -267,10 +267,10 @@ With the proposed change in cadence, the notional schedules for the remainder of
267267
| 49 | 3 | 14 (December 06) |
268268

269269
This KEP will be in the `alpha` stage for the Kubernetes 1.22 Release. During
270-
this time, SIG-Release will focus on communication of the cadence change through
270+
this time, SIG Release will focus on communication of the cadence change through
271271
all available mechanisms. The KEP will promote to the `beta` stage for the
272272
Kubernetes 1.23 Release, which will be the final release of 2021. After
273-
the 1.23, 1.24, and 1.25 Releases, will will collect feedback and incorporate
273+
the 1.23, 1.24, and 1.25 Releases, SIG Release will collect feedback and incorporate
274274
that feedback into the lightweight framework surrounding release schedule
275275
development and promote this KEP to `stable` for the 1.26 Release.
276276

@@ -369,7 +369,7 @@ Some downstream projects, such as Helm have already begun
369369
[planning](https://github.com/helm/community/blob/main/hips/hip-0002.md#minor-releases)
370370
for this change.
371371

372-
To mitigate this risk, SIG-Release will perform the following actions:
372+
To mitigate this risk, SIG Release will perform the following actions:
373373

374374
* Once this KEP has merged, an email will be sent to the [k/dev](https://groups.google.com/g/kubernetes-dev) list
375375
* A community meeting occurring during the 1.22 Release Cycle will be used to communicate the change

0 commit comments

Comments
 (0)