From d942390c63cb056a1e87777f0140384f8c63d8a2 Mon Sep 17 00:00:00 2001 From: Sun Lintong Date: Fri, 16 Mar 2018 00:53:24 +0800 Subject: [PATCH] It's better to be "behavior" (#7738) * Correct spelling mistake The whole file only appeared once * Correct spell Correct the word "resource" spell. * Is "kube/.config" should be ".kube/config" It seems that the file is ".kube/config" * behaviour to behavior --- docs/admin/admission-controllers.md | 2 +- docs/admin/authentication.md | 2 +- docs/admin/high-availability/building.md | 2 +- docs/admin/multiple-zones.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/admin/admission-controllers.md b/docs/admin/admission-controllers.md index 32d676f6a8..4aeacc2c84 100644 --- a/docs/admin/admission-controllers.md +++ b/docs/admin/admission-controllers.md @@ -329,7 +329,7 @@ When the admission controller sets a compute resource request, it does this by * the pod spec rather than mutating the `container.resources` fields. The annotations added contain the information on what compute resources were auto-populated. -See the [InitialResouces proposal](https://git.k8s.io/community/contributors/design-proposals/autoscaling/initial-resources.md) for more details. +See the [InitialResources proposal](https://git.k8s.io/community/contributors/design-proposals/autoscaling/initial-resources.md) for more details. ### LimitPodHardAntiAffinity diff --git a/docs/admin/authentication.md b/docs/admin/authentication.md index 2c106e4406..6d1db7e15c 100644 --- a/docs/admin/authentication.md +++ b/docs/admin/authentication.md @@ -373,7 +373,7 @@ users: refresh-token: q1bKLFOyUiosTfawzA93TzZIDzH2TNa2SMm0zEiPKTUwME6BkEo6Sql5yUWVBSWpKUGphaWpxSVAfekBOZbBhaEW+VlFUeVRGcluyVF5JT4+haZmPsluFoFu5XkpXk5BXq name: oidc ``` -Once your `id_token` expires, `kubectl` will attempt to refresh your `id_token` using your `refresh_token` and `client_secret` storing the new values for the `refresh_token` and `id_token` in your `kube/.config`. +Once your `id_token` expires, `kubectl` will attempt to refresh your `id_token` using your `refresh_token` and `client_secret` storing the new values for the `refresh_token` and `id_token` in your `.kube/config`. ##### Option 2 - Use the `--token` Option diff --git a/docs/admin/high-availability/building.md b/docs/admin/high-availability/building.md index 1ae1b74c6e..4175c3d6f6 100644 --- a/docs/admin/high-availability/building.md +++ b/docs/admin/high-availability/building.md @@ -219,7 +219,7 @@ endpoints. You can switch to the new reconciler by adding the flag {% include feature-state-alpha.md %} If you want to know more, you can check the following resources: -- [issue kubernetes/kuberenetes#22609](https://github.com/kubernetes/kubernetes/issues/22609), +- [issue kubernetes/kubernetes#22609](https://github.com/kubernetes/kubernetes/issues/22609), which gives additional context - [master/reconcilers/mastercount.go](https://github.com/kubernetes/kubernetes/blob/dd9981d038012c120525c9e6df98b3beb3ef19e1/pkg/master/reconcilers/mastercount.go#L63), the implementation of the master count reconciler diff --git a/docs/admin/multiple-zones.md b/docs/admin/multiple-zones.md index e15b61bf2a..2bb6c818f7 100644 --- a/docs/admin/multiple-zones.md +++ b/docs/admin/multiple-zones.md @@ -36,7 +36,7 @@ zone information. Kubernetes will automatically spread the pods in a replication controller or service across nodes in a single-zone cluster (to reduce the impact of -failures.) With multiple-zone clusters, this spreading behaviour is +failures.) With multiple-zone clusters, this spreading behavior is extended across zones (to reduce the impact of zone failures.) (This is achieved via `SelectorSpreadPriority`). This is a best-effort placement, and so if the zones in your cluster are heterogeneous