Updated topology spread constraints.md

Author: vaibhav2107

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

@@ -480,8 +480,9 @@ There are some implicit conventions worth noting here:
 - The scheduler bypasses any nodes that don't have any `topologySpreadConstraints[*].topologyKey`
   present. This implies that:
 
-  1. any Pods located on those bypassed nodes do not impact `maxSkew` calculation - [in the
-     above example](#example-conflicting-topologyspreadconstraints), suppose the node `node1` does not have a label "zone", then the 2 Pods will
+  1. any Pods located on those bypassed nodes do not impact `maxSkew` calculation - in the
+     above [example](#example-conflicting-topologyspreadconstraints), suppose the node `node1`
+     does not have a label "zone", then the 2 Pods will
      be disregarded, hence the incoming Pod will be scheduled into zone `A`.
   2. the incoming Pod has no chances to be scheduled onto this kind of nodes -
      in the above example, suppose a node `node5` has the **mistyped** label `zone-typo: zoneC`