Apply style guide

Author: maxvp

src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx

@@ -209,7 +209,7 @@ The [Application](#application), [Content Categories](#content-categories), [Dom
 
 When you use these selectors in an egress policy for traffic from a supported on-ramp, Gateway will assign initial resolved IPs in the `100.80.0.0/16` range to the DNS queries, then apply the correct egress IP according to the egress policy. Unsupported traffic will be resolved with your default Gateway settings. Gateway will only overwrite the DNS response when the query matches a condition in the egress policy. If you use [DNS locations](/cloudflare-one/connections/connect-devices/agentless/dns/locations/) to send a DNS query to Gateway with IPv4, IPv6, DoT, or DoH, Gateway will not return the initial resolved IP for supported traffic nor resolve unsupported traffic.
 
-Gateway will overwrite the DNS response for all supported traffic, even if identity or device posture selectors are used to limit which users or devices should be affected by the policy. In these cases, while the DNS response is overwritten, the correct egress policy will still be applied.
+Gateway will overwrite the DNS response for all supported traffic, even if you use identity or device posture selectors to limit which users or devices are affected by the policy. In these cases, while the DNS response is overwritten, Gateway will still apply the correct egress policy.
 
 To turn on the selectors for your account:
 
@@ -271,4 +271,4 @@ Additionally, to use these selectors to filter traffic onboarded with WARP, you
 
    </TabItem> </Tabs>
 
-The WARP client must be set to **Gateway with WARP** mode in order for traffic affected by these selectors to route correctly.
+The WARP client must be set to _Gateway with WARP_ mode for traffic affected by these selectors to route correctly.