[SQUASH ME] Address feedback and adjust per style guide

content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md

@@ -197,20 +197,21 @@ Known issues:
 ## Load Balancer cleanup
 
 In usual case, the correlating load balancer resources in cloud provider should
-be cleaned up soon after a LoadBalancer type service is deleted. But it is known
+be cleaned up soon after a LoadBalancer type Service is deleted. But it is known
 that there are various corner cases where resources can be leaved orphaned after
-a service is deleted. Finalizer Protection for Service LoadBalancers was
+a Service is deleted. Finalizer Protection for Service LoadBalancers was
 introduced to prevent this from happening. By using finalizer, this feature
-makes sure service resource is not fully deleted until the correlating load
+makes sure Service resource is not fully deleted until the correlating load
 balancer resources are deleted.
 
-Specifically, a finalizer with name `"service.kubernetes.io/load-balancer-cleanup"`
-will be attached to the service if any load balancer resource is created for it.
-The finalizer will only be removed after load balancer resource is cleaned up.
+Specifically, if a Service has a load balancer resource created for it, service
+controller will attach a finalizer named "service.kubernetes.io/load-balancer-cleanup".
+The finalizer will only be removed after the load balancer resource is cleaned up.
 Above ensures resource won't be leaked even in corner cases.
 
-This feature was introduced as Alpha in kubernetes v1.15. It can be enabled via
-feature gate `ServiceLoadBalancerFinalizer=true`.
+This feature was introduced as alpha in Kubernetes v1.15. You can start using it by
+enabling the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+`ServiceLoadBalancerFinalizer`.
 
 ## External Load Balancer Providers