anchor.diff:  link:http://kubernetes.io/docs/user-guide/services/#external-ips[ExternalIPs]
   to the service. The supplied list of IP addresses are used for load balancing
   incoming requests. The service port is opened on all nodes running kube-proxy.
  -Doing this requires elevated permissions to assign, and manual tracking of the
  +ExternalIPs require elevated permissions to assign, and manual tracking of the
   IP:ports that are in use.
   
   An externally visible IP can be configured in one of several ways:
   
  -- manually configure the ExternalIP with a known external IP address.
  -- configure ExternalIP to a
  +- Manually configure the ExternalIP with a known external IP address.
  +- Configure ExternalIP to a
   xref:../admin_guide/high_availability.adoc#admin-guide-high-availability[VIP]
  -that is generated from (VRRP)
  +that is generated from (VRRP).
   - In a cloud (xref:../install_config/configuring_aws.adoc#install-config-configuring-aws[AWS] or
   xref:../install_config/configuring_gce.adoc#install-config-configuring-gce[GCE])
  -use type=LoadBalancer
  +use `type=LoadBalancer`
   - In a non-cloud environment, configure an ingressIP range (IngressIPNetworkCIDR),
  -service.type=LoadBalancer and service.port.ingressIP
  +`service.type=LoadBalancer` and `service.port.ingressIP`.
   
  -The admin must make sure the external IPs are routed to the nodes and local
  +The administrator must ensure the external IPs are routed to the nodes and local
   firewall rules on all nodes allow access to the open port.
   
  -Use the same nodes as the router but advertise them with VRRP and use
  +Use the same nodes as the router, but advertise them with VRRP and use
   the DNS address of the router nodes.
  -
   
   [[using-nodeport]]
   == Using a Service NodePort
   
   Use NodePorts to expose the service nodePort on all nodes in the cluster.
   NodePorts are in the 30-60k range by default, which means a NodePort is
  -unlikely to match a service's intended port (e.g., 8080 might be exposed
  -as 31020).  This use of ports is wasteful of scarce port resources.
  -However, it is a little easier to set up. Again, this requires more privilege.
  +unlikely to match a service's intended port (for example, 8080 may be exposed
  +as 31020). This use of ports is wasteful of scarce port resources.
  +However, it is slightly easier to set up. Again, this requires more privileges.
   
  -The admin must make sure the external IPs are routed to the nodes and local
  +The administrator must ensure the external IPs are routed to the nodes and local
   firewall rules on all nodes allow access to the open port.
   
   NodePorts and externalIP are independent and both can be used concurrently.
  
positive.code: [[getting-traffic-into-cluster]]
  = Getting Traffic Into The Cluster
  {product-author}
  {product-version]
  :data-uri:
  
negative.code: == Using Virtual IPs
  
  All of the approaches can expose
  xref:../admin_guide/high_availability.adoc#admin-guide-high-availability[VIPs].
  The VIPs are generated from the VRRP protocol.
  
  
  [[edge-load-balancer]]
  == Edge Load Balancer
  
  An edge xref:../install_config/routing_from_edge_lb.adoc#install-config-routing-from-edge-lb[load balancer]
  can be used to accept traffic from outside networks and proxy the traffic
  to pods inside the cluster.
  
  In this configuration, the internal pod network is visible to the outside.
  