Update src/content/docs/privacy-gateway/privacy-proxy-onboarding.mdx

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>

Author: ToriLindsay

src/content/docs/privacy-gateway/privacy-proxy-onboarding.mdx

@@ -144,7 +144,7 @@ The following section describes how these tunnels and subsequent CONNECT request
 The first CONNECT request in a newly established tunnel must provide a PAT. Until a PAT has been presented, each CONNECT request fails with a HTTP `401` error. Details about authenticating with a PAT are in [client authentication](#client-authentication).
 
 - Each CONNECT request can identify a target either by name or IP address.
-- In the case of a name, Cloudflare’s DNS Resolver service will be queried to map the name to an IP address.
+- In the case of a name, Cloudflare's DNS Resolver service will be queried to map the name to an IP address.
 - In the case of an IP address, the IP address provided will be used to establish the upstream transport connection.
 
 It is recommended that only CONNECT requests be sent over HTTP/1.1 or HTTP/2 connections to the Privacy Proxy. Requests for other HTTP methods may be rejected with a HTTP `405 (Method Not Allowed)` response by the Privacy Proxy. Specifically, CONNECT-UDP requests are not supported and will be rejected with a HTTP `405 (Method Not Allowed)` response by the proxy.