From bff0e68efa9235c366f49fc9de602800063af96f Mon Sep 17 00:00:00 2001
From: Jeremy <jeremyrrickard@gmail.com>
Date: Tue, 20 Jul 2021 10:10:29 -0600
Subject: [PATCH] Change wording around end of year holidays
Signed-off-by: Jeremy <jeremyrrickard@gmail.com>
---
.../_posts/2021-07-20-Kubernetes-Release-Cadence/index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/en/blog/_posts/2021-07-20-Kubernetes-Release-Cadence/index.md b/content/en/blog/_posts/2021-07-20-Kubernetes-Release-Cadence/index.md
index 3f563cedfb..6575466283 100644
--- a/content/en/blog/_posts/2021-07-20-Kubernetes-Release-Cadence/index.md
+++ b/content/en/blog/_posts/2021-07-20-Kubernetes-Release-Cadence/index.md
@@ -16,8 +16,8 @@ This blog post provides a high level overview about what this means for the Kube
Starting with the [Kubernetes 1.22 release](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.22), a lightweight policy will drive the creation of each release schedule. This policy states:
* The first Kubernetes release of a calendar year should start at the second or third
- week of January to provide people more room after coming back from the
- winter holidays.
+ week of January to provide people more time for contributors coming back from the
+ end of year holidays.
* The last Kubernetes release of a calendar year should be finished by the middle of
December.
* A Kubernetes release cycle has a length of approximately 15 weeks.