From 7095fcce17330d122d6bbb2cb64dc4ae1a738033 Mon Sep 17 00:00:00 2001 From: Jeremy Rickard Date: Fri, 16 Jul 2021 13:34:16 -0600 Subject: [PATCH] Update content/en/blog/_posts/2021-07-12-Kubernetes-Release-Cadence/index.md Co-authored-by: Sascha Grunert --- .../blog/_posts/2021-07-12-Kubernetes-Release-Cadence/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2021-07-12-Kubernetes-Release-Cadence/index.md b/content/en/blog/_posts/2021-07-12-Kubernetes-Release-Cadence/index.md index e7dd6c51c2..0ef377ebc4 100644 --- a/content/en/blog/_posts/2021-07-12-Kubernetes-Release-Cadence/index.md +++ b/content/en/blog/_posts/2021-07-12-Kubernetes-Release-Cadence/index.md @@ -55,7 +55,7 @@ These proposed dates reflect only the start and end dates, and they are subject The only major change end users will experience is a slower release cadence. Kubernetes release artifacts, release notes, and all other aspects of any given release will stay the same. -With less releases to consume per year, end user organizations will spend less time on upgrades and more time on supporting their Kubernetes clusters. It also means that Kubernetes releases are in support for a slightly longer period of time. +With less releases to consume per year, it's intended that end user organizations will spend less time on upgrades and gain more time on supporting their Kubernetes clusters. It also means that Kubernetes releases are in support for a slightly longer period of time. ## What this means for Kubernetes contributors