From 5d9f802cd773e739ce81ef825e8c27b7fb8724a9 Mon Sep 17 00:00:00 2001 From: Daniel Lee Date: Thu, 28 Mar 2024 21:19:12 +0100 Subject: [PATCH] Update gke.md - spelling (#3740) Corrects the spelling for the word `recommend` in the first sentence in the `Why?` section. --- site/content/en/docs/Guides/Best Practices/gke.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/en/docs/Guides/Best Practices/gke.md b/site/content/en/docs/Guides/Best Practices/gke.md index aef0a67fbb..5ae4abe6a2 100644 --- a/site/content/en/docs/Guides/Best Practices/gke.md +++ b/site/content/en/docs/Guides/Best Practices/gke.md @@ -13,7 +13,7 @@ On this page, we've collected several [Google Kubernetes Engine (GKE)](https://c ### Why? -We recommned using [Release Channels](https://cloud.google.com/kubernetes-engine/docs/concepts/release-channels) for all GKE clusters. Using Release Channels has several advantages: +We recommend using [Release Channels](https://cloud.google.com/kubernetes-engine/docs/concepts/release-channels) for all GKE clusters. Using Release Channels has several advantages: * Google automatically manages the version and upgrade cadence for your Kubernetes Control Plane and its nodes. * Clusters on a Release Channel are allowed to use the `No minor upgrades` and `No minor or node upgrades` [scope of maintenance exclusions](https://cloud.google.com/kubernetes-engine/docs/concepts/maintenance-windows-and-exclusions#limitations-maint-exclusions) - in other words, enrolling a cluster in a Release Channel gives you _more control_ over node upgrades. * Clusters enrolled in `rapid` channel have access to the newest Kubernetes version first. Agones strives to [support the newest release in `rapid` channel]({{< relref "Installation#agones-and-kubernetes-supported-versions" >}}) to allow you to test the newest Kubernetes soon after it's available in GKE.