Update using_gke_with_terraform.html.markdown (#13961) (#10006)

[upstream:35d7a23379d9338dc208c5bcf91b945459c90b58]

Signed-off-by: Modular Magician <[email protected]>

Author: modular-magician

.changelog/13961.txt

@@ -0,0 +1,3 @@
+```release-note:note
+Fixes a typo in the docs
+```

website/docs/guides/using_gke_with_terraform.html.markdown

@@ -59,7 +59,7 @@ provider "kubernetes" {
   )
 }
 ```
-Although the above can result in authentication errors, over time, as the token recorded in the google_client_cofig data resource is short lived (thus it expires) and it's stored in state.  Fortunately, the [kubernetes provider can accept valid credentials from an exec-based plugin](https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs#exec-plugins) to fetch a new token before each Terraform operation (so long as you have the [gke-cloud-auth-plugin for kubectl installed](https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke)), like so:
+Although the above can result in authentication errors, over time, as the token recorded in the google_client_config data resource is short lived (thus it expires) and it's stored in state.  Fortunately, the [kubernetes provider can accept valid credentials from an exec-based plugin](https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs#exec-plugins) to fetch a new token before each Terraform operation (so long as you have the [gke-cloud-auth-plugin for kubectl installed](https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke)), like so:
 
 ```hcl
 # Retrieve an access token as the Terraform runner