diff --git a/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md b/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md
index 223cdbb8e7..098a797481 100644
--- a/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md
+++ b/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md
@@ -691,7 +691,7 @@ is lost.
 The API server sets certain fields to default values in the live configuration if they are
 not specified when the object is created.
 
-Here's a configuration file for a Deployment. The file does not specify `strategy` or `selector`:
+Here's a configuration file for a Deployment. The file does not specify `strategy`:
 
 {{< code file="simple_deployment.yaml" >}}
 
@@ -721,7 +721,7 @@ spec:
   minReadySeconds: 5
   replicas: 1 # defaulted by apiserver
   selector:
-    matchLabels: # defaulted by apiserver - derived from template.metadata.labels
+    matchLabels:
       app: nginx
   strategy:
     rollingUpdate: # defaulted by apiserver - derived from strategy.type
@@ -750,10 +750,6 @@ spec:
 # ...
 ```
 
-**Note:** Some of the fields' default values have been derived from
-the values of other fields that were specified in the configuration file,
-such as the `selector` field.
-
 In a patch request, defaulted fields are not re-defaulted unless they are explicitly cleared
 as part of a patch request. This can cause unexpected behavior for
 fields that are defaulted based