Update src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx

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

Author: securitypedant

src/content/docs/reference-architecture/design-guides/designing-ztna-access-policies.mdx

@@ -433,7 +433,7 @@ This level of protection and visibility would be significantly more complex and
 
 This final use case centers on securing remote access to devices via RDP in two ways — self-hosted or private IP. Both options offer unique benefits, but ultimately it comes down to your priorities: is it more important to simplify access, or to tightly monitor activity?
 
-We’ll start with the self-hosted option — proxying port 3389 over a tunnel, mapping it to a hostname.
+We'll start with the self-hosted option — proxying port 3389 over a tunnel, mapping it to a hostname.
 
 | Application Configuration |                                     |
 | :------------------------ | :---------------------------------- |