Apply suggestions from code review

Co-authored-by: Tim Bannister <tim@scalefactory.com>

content/en/docs/reference/networking/virtual-ips.md

@@ -131,10 +131,12 @@ iptables:
 {{< feature-state for_k8s_version="v1.27" state="beta" >}}
 
 In the past (before v1.27), kube-proxy updated all the rules for all
-services on every sync, which contributed to the slowness in very
-large clusters. In current releases, it is able to optimize its
+Services on every sync, which contributed to the slowness in very
+large clusters. For later releases - including Kubernetes {{< skew currentVersion >}} -
+the kube-proxy defaults to an approach that optimizes
 updates better to make smaller iptables updates when only a few
-services have changed. As a result, kube-proxy configuration changes
+Services (or their EndpointSlices) have changed. As a result, kube-proxy configuration
+changes
 that were made to improve performance in the past may no longer be
 necessary, and may actually have a negative effect on overall proxy
 performance.
@@ -164,7 +166,7 @@ The larger the value of `minSyncPeriod`, the more work that can be
 aggregated, but the downside is that each individual change may end up
 waiting up to the full `minSyncPeriod` before being processed, meaning
 that the iptables rules spend more time being out-of-sync with the
-current apiserver state.
+current API server state.
 
 The default value of `1s` should work well in most clusters, but in very
 large clusters it may be necessary to set it to a larger value.