diff --git a/docs/advanced/dns-overview.md b/docs/advanced/dns-overview.md
index 489e3343..d672104f 100644
--- a/docs/advanced/dns-overview.md
+++ b/docs/advanced/dns-overview.md
@@ -126,7 +126,7 @@ In this example we will record what happens when we make a DoH request:
 
 We can see the [connection establishment](https://en.wikipedia.org/wiki/Transmission_Control_Protocol#Connection_establishment) and [TLS handshake](https://cloudflare.com/learning/ssl/what-happens-in-a-tls-handshake) that occurs with any encrypted connection. When looking at the "application data" packets that follow, none of them contain the domain we requested or the IP address returned.
 
-## Why **shouldn't** I use encrypted DNS?
+## Encrypted DNS Limitations
 
 In locations where there is internet filtering (or censorship), visiting forbidden resources may have its own consequences which you should consider in your [threat model](../basics/threat-modeling.md). We do **not** suggest the use of encrypted DNS for this purpose. Use [Tor](../advanced/tor-overview.md) or a [VPN](../vpn.md) instead. If you're using a VPN, you should use your VPN's DNS servers. When using a VPN, you are already trusting them with all your network activity.