Merge pull request #37373 from windsonsea/topspre

fix alignment in topology-spread-constraints.md

Author: k8s-ci-robot

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

@@ -45,7 +45,6 @@ and you'd like the cluster to self-heal in the case that there is a problem.
 
 Pod topology spread constraints offer you a declarative way to configure that.
 
-
 ## `topologySpreadConstraints` field
 
 The Pod API includes a field, `spec.topologySpreadConstraints`. The usage of this field looks like
@@ -202,7 +201,6 @@ You can't make a reliable assumption about the meaning of a private label key
 between different contexts.
 {{< /note >}}
 
-
 Suppose you have a 4-node cluster with the following labels:
 
 ```
@@ -580,7 +578,8 @@ or more scattered.
 
 `podAffinity`
 : attracts Pods; you can try to pack any number of Pods into qualifying
-  topology domain(s)
+  topology domain(s).
+
 `podAntiAffinity`
 : repels Pods. If you set this to `requiredDuringSchedulingIgnoredDuringExecution` mode then
   only a single Pod can be scheduled into a single topology domain; if you choose
@@ -616,7 +615,6 @@ section of the enhancement proposal about Pod topology spread constraints.
   Pod topology spread constraints and is also aware of the overall set of topology
   domains.
 
-
 ## {{% heading "whatsnext" %}}
 
 - The blog article [Introducing PodTopologySpread](/blog/2020/05/introducing-podtopologyspread/)