From 470f932dd8649592152b0388c653d114e81ee74d Mon Sep 17 00:00:00 2001 From: Andrew Allbright Date: Wed, 19 Feb 2020 03:14:25 -0500 Subject: [PATCH] Latin Abbreviations "vs" Updated to "versus" (#19181) * grep -lR ' vs ' ./content/en/docs | xargs sed -i '' -e 's/ vs / versus /g' * Update content/en/docs/concepts/configuration/overview.md Co-Authored-By: Tim Bannister * Update content/en/docs/concepts/policy/resource-quotas.md Co-Authored-By: Tim Bannister Co-authored-by: Tim Bannister --- content/en/docs/concepts/configuration/overview.md | 3 +-- .../extend-kubernetes/api-extension/custom-resources.md | 2 +- content/en/docs/concepts/policy/resource-quotas.md | 2 +- .../docs/reference/access-authn-authz/admission-controllers.md | 2 +- 4 files changed, 4 insertions(+), 5 deletions(-) diff --git a/content/en/docs/concepts/configuration/overview.md b/content/en/docs/concepts/configuration/overview.md index 1f67727322..ca56089b01 100644 --- a/content/en/docs/concepts/configuration/overview.md +++ b/content/en/docs/concepts/configuration/overview.md @@ -30,7 +30,7 @@ This is a living document. If you think of something that is not on this list bu - Put object descriptions in annotations, to allow better introspection. -## "Naked" Pods vs ReplicaSets, Deployments, and Jobs +## "Naked" Pods versus ReplicaSets, Deployments, and Jobs {#naked-pods-vs-replicasets-deployments-and-jobs} - Don't use naked Pods (that is, Pods not bound to a [ReplicaSet](/docs/concepts/workloads/controllers/replicaset/) or [Deployment](/docs/concepts/workloads/controllers/deployment/)) if you can avoid it. Naked Pods will not be rescheduled in the event of a node failure. @@ -108,4 +108,3 @@ The caching semantics of the underlying image provider make even `imagePullPolic {{% /capture %}} - diff --git a/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md b/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md index 660d589169..c96ae1f5c7 100644 --- a/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md +++ b/content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md @@ -202,7 +202,7 @@ When you create a custom resource, either via a CRDs or an AA, you get many feat | Finalizers | Block deletion of extension resources until external cleanup happens. | | Admission Webhooks | Set default values and validate extension resources during any create/update/delete operation. | | UI/CLI Display | Kubectl, dashboard can display extension resources. | -| Unset vs Empty | Clients can distinguish unset fields from zero-valued fields. | +| Unset versus Empty | Clients can distinguish unset fields from zero-valued fields. | | Client Libraries Generation | Kubernetes provides generic client libraries, as well as tools to generate type-specific client libraries. | | Labels and annotations | Common metadata across objects that tools know how to edit for core and custom resources. | diff --git a/content/en/docs/concepts/policy/resource-quotas.md b/content/en/docs/concepts/policy/resource-quotas.md index 14fde56066..92f43fe3a3 100644 --- a/content/en/docs/concepts/policy/resource-quotas.md +++ b/content/en/docs/concepts/policy/resource-quotas.md @@ -376,7 +376,7 @@ pods 0 10 * `Exist` * `DoesNotExist` -## Requests vs Limits +## Requests compared to Limits {#requests-vs-limits} When allocating compute resources, each container may specify a request and a limit value for either CPU or memory. The quota can be configured to quota either value. diff --git a/content/en/docs/reference/access-authn-authz/admission-controllers.md b/content/en/docs/reference/access-authn-authz/admission-controllers.md index 2e741afd76..2ab54051a4 100644 --- a/content/en/docs/reference/access-authn-authz/admission-controllers.md +++ b/content/en/docs/reference/access-authn-authz/admission-controllers.md @@ -737,7 +737,7 @@ phase, and therefore is the last admission controller to run. `MutatingAdmissionWebhook` appears before it in this list, because it runs in the mutating phase. - For earlier versions, there was no concept of validating vs mutating and the + For earlier versions, there was no concept of validating versus mutating and the admission controllers ran in the exact order specified. {{% /capture %}}