Merge remote-tracking branch 'upstream/main' into dev-1.23

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

@@ -30,9 +30,9 @@ mutating and validating (respectively)
 which are configured in the API.
 
 Admission controllers may be "validating", "mutating", or both. Mutating
-controllers may modify the objects they admit; validating controllers may not.
+controllers may modify related objects to the requests they admit; validating controllers may not.
 
-Admission controllers limit requests to create, delete, modify or connect to (proxy). They do not support read requests.
+Admission controllers limit requests to create, delete, modify objects or connect to proxy. They do not limit requests to read objects.
 
 The admission control process proceeds in two phases. In the first phase,
 mutating admission controllers are run. In the second phase, validating

content/en/docs/reference/access-authn-authz/authentication.md

@@ -104,7 +104,7 @@ See [Managing Certificates](/docs/tasks/administer-cluster/certificates/) for ho
 ### Static Token File
 
 The API server reads bearer tokens from a file when given the `--token-auth-file=SOMEFILE` option on the command line.  Currently, tokens last indefinitely, and the token list cannot be
-changed without restarting API server.
+changed without restarting the API server.
 
 The token file is a csv file with a minimum of 3 columns: token, user name, user uid,
 followed by optional group names.

content/en/docs/reference/access-authn-authz/authorization.md

@@ -134,7 +134,7 @@ The output is similar to this:
 no
 ```
 
-Similarly, to check whether a Service Account named `dev-sa` in Namespace `dev`
+Similarly, to check whether a ServiceAccount named `dev-sa` in Namespace `dev`
 can list Pods in the Namespace `target`:
 
 ```bash