moved one line down

Author: tamilselvan1102

content/en/docs/concepts/services-networking/service.md

@@ -855,9 +855,7 @@ You can use a headless Service to interface with other service discovery mechani
 without being tied to Kubernetes' implementation.
 
 For headless Services, a cluster IP is not allocated, kube-proxy does not handle
-these Services, and there is no load balancing or proxying done by the platform
-for them. How DNS is automatically configured depends on whether the Service has
-selectors defined:
+these Services, and there is no load balancing or proxying done by the platform for them.
 
 A headless Service allows a client to connect to whichever Pod it prefers, directly. Services that are headless don't
 configure routes and packet forwarding using
@@ -869,6 +867,8 @@ and you additionally set `.spec.clusterIP` to None.
 
 The string value None is a special case and is not the same as leaving the `.spec.clusterIP` field unset.
 
+How DNS is automatically configured depends on whether the Service has selectors defined:
+
 ### With selectors
 
 For headless Services that define selectors, the endpoints controller creates