Fix typos GKE documentation (#2253)

content/en/docs/gke/anthos.md

@@ -16,7 +16,7 @@ open source technologies, including Kubernetes, Istio, and Knative.
 Using Anthos, you can create a consistent setup across your on-premises and 
 cloud environments, helping you to automate policy and security at scale.
 
-Kubeflow on GKE On Prem is a work in progress. To track progess you can subscribe
+Kubeflow on GKE On Prem is a work in progress. To track progress you can subscribe
 to the GitHub issue [kubeflow/gcp-blueprints#138](https://github.com/kubeflow/gcp-blueprints/issues/138).
 
 ## Next steps

content/en/docs/gke/cloud-filestore.md

@@ -49,7 +49,7 @@ This guide assumes the following settings:
 
 * The `${PROJECT}` environment variable contains the ID of your GCP project. 
   You can find the project ID in 
-  your `${CONFIG_FILE}` configuraiton file, as the value for the `project` key.
+  your `${CONFIG_FILE}` configuration file, as the value for the `project` key.
 
   ```
   export PROJECT=<your GCP project ID>

content/en/docs/gke/deploy/management-setup.md

@@ -11,7 +11,7 @@ The management cluster is used to run [Cloud Config Connector](https://cloud.goo
 While the management cluster can be deployed in the same project as your Kubeflow cluster, typically you will want to deploy
 it in a separate project used for administering one or more Kubeflow instances.
 
-Optionally, the cluster can be configured with [Anthos Config Managmenet](https://cloud.google.com/anthos-config-management/docs) 
+Optionally, the cluster can be configured with [Anthos Config Management](https://cloud.google.com/anthos-config-management/docs) 
 to manage Google Cloud infrastructure using GitOps.
 
 ## FAQs

content/en/docs/gke/pipelines/authentication-sdk.md

@@ -16,7 +16,7 @@ Cloud using [the Kubeflow Pipelines SDK](/docs/pipelines/sdk/sdk-overview/).
 
 Kubeflow Pipelines includes an API service named `ml-pipeline-ui`. The
 `ml-pipeline-ui` API service is deployed in the same Kubernetes namespace you
-deployed Kubeflow Pipielines in.
+deployed Kubeflow Pipelines in.
 
 The Kubeflow Pipelines SDK can send REST API requests to this API service, but
 the SDK needs to know the hostname to connect to the API service.

content/en/docs/gke/private-clusters.md

@@ -96,7 +96,7 @@ These instructions explain how to deploy Kubeflow using private GKE.
    * Then rerun `make apply`
 
 1. The cloud endpoints controller doesn't work with private GKE ([kubeflow/gcp-blueprints#36](https://github.com/kubeflow/gcp-blueprints/issues/36)) as a workaround
-   you can run `kfctl` locally to create the endpoitn
+   you can run `kfctl` locally to create the endpoint
 
    ```
    kfctl apply -f .build/iap-ingress/ctl.isla.solutions_v1_cloudendpoint_${KFNAME}.yaml

content/en/docs/gke/troubleshooting-gke.md

@@ -102,7 +102,7 @@ https://${KF_NAME}.endpoints.${PROJECT}.cloud.goog
 
 Symptoms:
 
-  * When you access the the URL in Chrome you get the error: **server IP address could not be found**
+  * When you access the URL in Chrome you get the error: **server IP address could not be found**
   * nslookup for the domain name doesn't return the IP address associated with the ingress
 
     ```
@@ -317,7 +317,7 @@ because it could not verify that you owned the domain by doing an ACME challenge
 
 If there is a problem preventing either of the above then GCP will be unable to provision your certificate
 and eventually enter the permanent failure state `FailedNotVisible` indicating your endpoint isn't accessible. The most common 
-cause is the ingress can't be created becuase the K8s secret containing OAuth credentials doesn't
+cause is the ingress can't be created because the K8s secret containing OAuth credentials doesn't
 exist.
 
 To fix this you must first resolve the underlying problems preventing your ingress or DNS entry from being created.
@@ -531,7 +531,7 @@ To check your certificate:
           - ip: 35.186.212.202
      ```
 
-   * DNS entry for the domain has propogated. To verify this, use the following `nslookup` command example:
+   * DNS entry for the domain has propagated. To verify this, use the following `nslookup` command example:
 
      ```
      `nslookup ${DOMAIN}`