diff --git a/content/en/docs/reference/using-api/server-side-apply.md b/content/en/docs/reference/using-api/server-side-apply.md
index 4caa7f1119da5..866f24140a4e0 100644
--- a/content/en/docs/reference/using-api/server-side-apply.md
+++ b/content/en/docs/reference/using-api/server-side-apply.md
@@ -214,17 +214,6 @@ Here's an example of a Server-Side Apply message body (fully specified intent):
 of a **patch** request to a valid `v1/configmaps` resource, and with the
 appropriate request `Content-Type`).
 
-## Server-Side Apply for custom resources {#custom-resources}
-
-By default, Server-Side Apply treats
-{{< glossary_tooltip term_id="CustomResourceDefinition" text="custom resources" >}}
-as unstructured data. All keys are treated the same as if they were struct fields for
-a built-in API, and all lists are considered atomic.
-
-If the CustomResourceDefinition defines a
-[schema](/docs/reference/kubernetes-api/extend-resources/custom-resource-definition-v1/#JSONSchemaProps)
-that contains annotations as defined in [Merge strategy](#merge-strategy),
-then these annotations will be used when merging objects of this type.
 
 ## Operations in scope for field management {#apply-and-update}