Merge pull request #40886 from xak2000/patch-1

Fix well-known label name

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

@@ -253,7 +253,7 @@ confusing and troubleshooting is less straightforward.
 You need a mechanism to ensure that all the nodes in a topology domain (such as a
 cloud provider region) are labelled consistently.
 To avoid you needing to manually label nodes, most clusters automatically
-populate well-known labels such as `topology.kubernetes.io/hostname`. Check whether
+populate well-known labels such as `kubernetes.io/hostname`. Check whether
 your cluster supports this.
 
 ## Topology spread constraint examples