Apply suggestions from code review

Co-authored-by: Pedro Sousa <[email protected]>

Author: angelampcosta

src/content/docs/load-balancing/load-balancers/index.mdx

@@ -24,9 +24,9 @@ For suggestions, refer to [Common load balancer configurations](/load-balancing/
 
 ## Public vs. Private Load Balancers
 
-Public Load Balancers are designed to handle traffic from the public internet. When deployed, they automatically receive a hostname, making them immediately accessible. These load balancers can direct traffic to a range of destinations, including public hostnames, public IP addresses, and private IP addresses.
+Public Load Balancers are designed to handle traffic from the public Internet. When deployed, they automatically receive a hostname, making them immediately accessible. These load balancers can direct traffic to a range of destinations, including public hostnames, public IP addresses, and private IP addresses.
 
-Private Load Balancers, in contrast, are meant for internal use within private networks. They do not automatically receive a hostname, but one can be assigned via Gateway Firewall Policies or through an internal DNS system. Private Load Balancers only accept traffic over a private network on-ramp, such as [Cloudflare WARP ](/warp-client/) or [Magic WAN](/magic-wan/). They are capable of forwarding traffic exclusively to private IP addresses.
+Private Load Balancers, in contrast, are meant for internal use within private networks. They do not automatically receive a hostname, but one can be assigned via Gateway Firewall Policies or through an internal DNS system. Private Load Balancers only accept traffic over a private network on-ramp, such as [Cloudflare WARP](/warp-client/) or [Magic WAN](/magic-wan/). They are capable of forwarding traffic exclusively to private IP addresses.
 
 ## Load balancing and existing DNS records
 

src/content/docs/load-balancing/private-network/index.mdx

@@ -55,4 +55,4 @@ Private Network Load Balancing on-ramps, on the other hand, refer to secure path
 
 * **Host applications on non-standard ports**: Easily specify and route traffic to applications hosted on private IP addresses using non-standard ports, allowing greater flexibility in service configuration without requiring changes to existing infrastructure.
 
-* **Public and Private Load Balancers**: Public LBs can direct internet traffic to private IP addresses, supporting all L7 products like WAF and API Shield. Private LBs direct traffic originating from private networks to private IP addresses and require an on-ramp like WARP or Magic WAN.
+* **Public and Private Load Balancers**: Public LBs can direct Internet traffic to private IP addresses, supporting all L7 products like WAF and API Shield. Private LBs direct traffic originating from private networks to private IP addresses and require an on-ramp like WARP or Magic WAN.

src/content/partials/load-balancing/layer-7-load-balancing-benefits.mdx

@@ -11,4 +11,4 @@ In comparison to DNS-only load balancing, layer 7 load balancing:
 * Reduces authoritative queries against Cloudflare, which can potentially save money for customers with usage-based billing.
 * Supports customized [session affinity](/load-balancing/understand-basics/session-affinity/) and [endpoint drain](/load-balancing/understand-basics/session-affinity/#endpoint-drain).
 * More accurately geo-locates traffic, using the data center associated with the user making the request instead of the data center associated with a user's recursive resolver.
-* Supports Private IP addresses with [Private Network Load Balancing](/load-balancing/private-network/).
+* Supports private IP addresses with [Private Network Load Balancing](/load-balancing/private-network/).