Update feature gate

Author: Jefftree

content/en/docs/concepts/overview/kubernetes-api.md

@@ -162,7 +162,7 @@ Kubernetes stores the serialized state of objects by writing them into
 
 A list of all group versions supported by a cluster is published at
 the `/api` and `/apis` endpoints. Each group version also advertises
-the list of resources supported via `/apis/<group>/<version` (for
+the list of resources supported via `/apis/<group>/<version>` (for
 example: `/apis/rbac.authorization.k8s.io/v1alpha1`). These endpoints
 are used by kubectl to fetch the list of resources supported by a
 cluster.
@@ -177,7 +177,8 @@ all resources supported by a cluster through two endpoints (`/api` and
 endpoint drastically reduces the number of requests sent to fetch the
 discovery for the average Kubernetes cluster. This may be accessed by
 requesting the respective endpoints with an Accept header indicating
-the aggregated discovery resource: `Accept:
+the aggregated discovery resource:
+`Accept:
 application/json;v=v2beta1;g=apidiscovery.k8s.io;as=APIGroupDiscoveryList`.
 
 The endpoint also supports ETag and protobuf encoding.

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

@@ -66,7 +66,8 @@ For a reference to old feature gates that are removed, please refer to
 | `APIServerIdentity` | `false` | Alpha | 1.20 | 1.25 |
 | `APIServerIdentity` | `true` | Beta | 1.26 | |
 | `APIServerTracing` | `false` | Alpha | 1.22 | |
-| `AggregatedDiscoveryEndpoint` | `false` | Alpha | 1.26 | |
+| `AggregatedDiscoveryEndpoint` | `false` | Alpha | 1.26 | 1.26 |
+| `AggregatedDiscoveryEndpoint` | `true` | Beta | 1.27 | |
 | `AnyVolumeDataSource` | `false` | Alpha | 1.18 | 1.23 |
 | `AnyVolumeDataSource` | `true` | Beta | 1.24 | |
 | `AppArmor` | `true` | Beta | 1.4 | |