[SQUASH ME] Review feedback 2

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

@@ -194,18 +194,17 @@ Known issues:
 
 {{% capture discussion %}}
 
-## Load Balancer cleanup
+## Garbage Collecting Load Balancers
 
 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
-that there are various corner cases where resources can be leaved orphaned after
-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
-balancer resources are deleted.
-
-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".
+that there are various corner cases where cloud resources are orphaned after the
+associated Service is deleted. Finalizer Protection for Service LoadBalancers was
+introduced to prevent this from happening. By using finalizers, a Service resource
+will never be deleted until the correlating load balancer resources are also deleted.
+
+Specifically, if a Service has Type=LoadBalancer, the 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.