From 4baed8a88b13e0f17777da2b13ebb867e6defc6c Mon Sep 17 00:00:00 2001
From: Hiroki Okada <hirokio@tutanota.com>
Date: Sun, 26 Dec 2021 07:13:33 +0000
Subject: [PATCH] Fix broken DNS definitions anchor (#462)

Signed-off-by: Daniel Gray <dng@disroot.org>
---
 collections/_pages/providers/dns.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/collections/_pages/providers/dns.md b/collections/_pages/providers/dns.md
index ab6bf04f..04da2e50 100644
--- a/collections/_pages/providers/dns.md
+++ b/collections/_pages/providers/dns.md
@@ -6,7 +6,7 @@ breadcrumb: "DNS"
 ---
 
 <div class="alert alert-warning" role="alert">
-  DNS-over-HTTPS, DNS-over-TLS, and DNSCrypt resolvers will not make you anonymous. Using Anonymized DNSCrypt hides <em>only</em> your DNS traffic from your Internet Service Provider. However, using any of these protocols will prevent DNS hijacking, and make your DNS requests harder for third parties to eavesdrop on and tamper with. If you are currently using Google's DNS resolver, you should pick an alternative here. See the <a href="#dns-definitions">definitions</a> below.
+  DNS-over-HTTPS, DNS-over-TLS, and DNSCrypt resolvers will not make you anonymous. Using Anonymized DNSCrypt hides <em>only</em> your DNS traffic from your Internet Service Provider. However, using any of these protocols will prevent DNS hijacking, and make your DNS requests harder for third parties to eavesdrop on and tamper with. If you are currently using Google's DNS resolver, you should pick an alternative here. See the <a href="#definitions">definitions</a> below.
 </div>
 
 {% include recommendation-table.html data='dns' %}