Revert "Repair and sync the dev-1.18 branch" (#19228)

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 versus mutating and the
+    For earlier versions, there was no concept of validating vs mutating and the
 admission controllers ran in the exact order specified.
 
 {{% /capture %}}

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

@@ -631,8 +631,6 @@ 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 versus service accounts
+## User accounts vs service accounts
 
 Kubernetes distinguishes between the concept of a user account and a service account
 for a number of reasons:

content/en/docs/reference/command-line-tools-reference/feature-gates.md

@@ -146,7 +146,7 @@ different Kubernetes components.
 | `TokenRequestProjection` | `true` | Beta | 1.12 | |
 | `TTLAfterFinished` | `false` | Alpha | 1.12 | |
 | `TopologyManager` | `false` | Alpha | 1.16 | |
-| `ValidateProxyRedirects` | `false` | Alpha | 1.12 | 1.13 |
+| `ValidateProxyRedirects` | `false` | Alpha | 1.10 | 1.13 |
 | `ValidateProxyRedirects` | `true` | Beta | 1.14 | |
 | `VolumePVCDataSource` | `false` | Alpha | 1.15 | 1.15 |
 | `VolumePVCDataSource` | `true` | Beta | 1.16 | |

content/en/docs/reference/kubectl/docker-cli-to-kubectl.md

@@ -281,7 +281,7 @@ kubectl get po -l run=nginx-app
 ```
 
 {{< note >}}
-When you use kubectl, you don't delete the pod directly. You have to first delete the Deployment that owns the pod. If you delete the pod directly, the Deployment recreates the pod.
+When you use kubectl, you don't delete the pod directly.You have to first delete the Deployment that owns the pod. If you delete the pod directly, the Deployment recreates the pod.
 {{< /note >}}
 
 ## docker login