From db40cc31fe655b1cd3daad71adb85872bcd434e7 Mon Sep 17 00:00:00 2001
From: Timothy Stewart <timothystewart6@gmail.com>
Date: Mon, 4 Jan 2021 17:34:25 -0600
Subject: [PATCH] fix(cname_records): Fixed gammar

Signed-off-by: Timothy Stewart <timothystewart6@gmail.com>
---
 cname_records.php | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cname_records.php b/cname_records.php
index 0e4e7e16..53dcdab5 100644
--- a/cname_records.php
+++ b/cname_records.php
@@ -40,7 +40,7 @@
             </div>
             <div class="box-footer clearfix">
               <strong>Note:</strong>
-              <p>The target of a <code>CNAME</code> must be a domain that the Pi-hole already has in its cache or is authoritative for. This is an universal limitation of <code>CNAME</code> records.</p>
+              <p>The target of a <code>CNAME</code> must be a domain that the Pi-hole already has in its cache or is authoritative for. This is a universal limitation of <code>CNAME</code> records.</p>
               <p>The reason for this is that Pi-hole will not send additional queries upstream when serving <code>CNAME</code> replies. As consequence, if you set a target that isn't already known, the reply to the client may be incomplete. Pi-hole just returns the information it knows at the time of the query. This results in certain limitations for <code>CNAME</code> targets,
                 for instance, only <i>active</i> DHCP leases work as targets - mere DHCP <i>leases</i> aren't sufficient as they aren't (yet) valid DNS records.</p>
                 <p>Additionally, you can't <code>CNAME</code> external domains (<code>bing.com</code> to <code>google.com</code>) successfully as this could result in invalid SSL certificate errors when the target server does not serve content for the requested domain.</p>