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 5eabfb07a1..614b0b60e2 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
@@ -110,7 +110,7 @@ Kubernetes provides two ways to add custom resources to your cluster:
 - CRDs are simple and can be created without any programming.
 - [API Aggregation](/docs/concepts/api-extension/apiserver-aggregation/) requires programming, but allows more control over API behaviors like how data is stored and conversion between API versions.
 
-Kubernetes provides these two options to meet the needs of different users, so that neither ease of use nor flexibility are compromised.
+Kubernetes provides these two options to meet the needs of different users, so that neither ease of use nor flexibility is compromised.
 
 Aggregated APIs are subordinate APIServers that sit behind the primary API server, which acts as a proxy. This arrangement is called [API Aggregation](/docs/concepts/api-extension/apiserver-aggregation/) (AA). To users, it simply appears that the Kubernetes API is extended.
 
@@ -245,4 +245,4 @@ When you add a custom resource, you can access it using:
 
 * Learn how to [Extend the Kubernetes API with CustomResourceDefinition](/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/).
 
-{{% /capture %}}
\ No newline at end of file
+{{% /capture %}}