Merge pull request #19221 from zacharysarah/dev-1.18-repair

Repair and sync the dev-1.18 branch

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 %}}

content/en/docs/reference/access-authn-authz/extensible-admission-controllers.md

@@ -631,6 +631,8 @@ So a webhook response to add that label would be:
 ## Webhook configuration
 
 To register admission webhooks, create `MutatingWebhookConfiguration` or `ValidatingWebhookConfiguration` API objects.
+The name of a `MutatingWebhookConfiguration` or a `ValidatingWebhookConfiguration` object must be a valid
+[DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
 
 Each configuration can contain one or more webhooks.
 If multiple webhooks are specified in a single configuration, each should be given a unique name.

content/en/docs/reference/access-authn-authz/service-accounts-admin.md

@@ -18,7 +18,7 @@ incomplete features are referred to in order to better describe service accounts
 {{% /capture %}}
 
 {{% capture body %}}
-## User accounts vs service accounts
+## User accounts versus service accounts
 
 Kubernetes distinguishes between the concept of a user account and a service account
 for a number of reasons: