update based on review

Author: sanposhiho

content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md

@@ -60,7 +60,7 @@ spec:
   # Configure a topology spread constraint
   topologySpreadConstraints:
     - maxSkew: <integer>
-      minDomains: <integer> # optional; GA since v1.30
+      minDomains: <integer> # optional
       topologyKey: <string>
       whenUnsatisfiable: <string>
       labelSelector: <object>
@@ -96,14 +96,6 @@ your cluster. Those fields are:
   A domain is a particular instance of a topology. An eligible domain is a domain whose
   nodes match the node selector.
 
-  {{< note >}}
-  The `MinDomainsInPodTopologySpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
-  enables `minDomains` for pod topology spread. From v1.28 to v1.29,
-  the `MinDomainsInPodTopologySpread` gate 
-  is enabled by default. 
-  And, at v1.30, this feature graduated to stable and the feature gate and the gate doesn't support the disablement anymore.
-  {{< /note >}}
-
   - The value of `minDomains` must be greater than 0, when specified.
     You can only specify `minDomains` in conjunction with `whenUnsatisfiable: DoNotSchedule`.
   - When the number of eligible domains with match topology keys is less than `minDomains`,