Update GitHub pages

_sources/index.rst.txt

@@ -596,7 +596,8 @@ have them set up DKIM.
     Yahoo! This occurs when customers have mailbox rules in place that forward
     emails from an old account to a new account, which is why DKIM
     authentication is so important, as mentioned earlier. Similar patterns may
-    be observed with business customers who rebrand.
+    be observed with businesses who send from reverse DNS addressees of
+    parent, subsidiary, and outdated brands.
 
 
 Any other filters work the same way. Further down the dashboard, you can filter
@@ -663,9 +664,9 @@ What if a sender won't support DKIM/DMARC?
 #. Do they really need to spoof your domain? Why not use the display
    name instead?
 #. Worst case, have that vendor send email as a specific subdomain of
-   your domain (e.g. ``noreply@marketing.example.com``), and then create
-   separate SPF and DMARC records on ``marketing.example.com``, and set
-   ``p=none`` in that DMARC record
+   your domain (e.g. ``noreply@news.example.com``), and then create
+   separate SPF and DMARC records on ``news.example.com``, and set
+   ``p=none`` in that DMARC record.
 
  .. warning ::
 

index.html

@@ -650,7 +650,8 @@ your domains coming from consumer email services, such as Google/Gmail and
 Yahoo! This occurs when customers have mailbox rules in place that forward
 emails from an old account to a new account, which is why DKIM
 authentication is so important, as mentioned earlier. Similar patterns may
-be observed with business customers who rebrand.</p>
+be observed with businesses who send from reverse DNS addressees of
+parent, subsidiary, and outdated brands.</p>
 </div>
 <p>Any other filters work the same way. Further down the dashboard, you can filter
 by source country or source IP address. You can also add your own custom
@@ -732,9 +733,9 @@ authentication.</li>
 <li>Do they really need to spoof your domain? Why not use the display
 name instead?</li>
 <li>Worst case, have that vendor send email as a specific subdomain of
-your domain (e.g. <code class="docutils literal notranslate"><span class="pre">noreply&#64;marketing.example.com</span></code>), and then create
-separate SPF and DMARC records on <code class="docutils literal notranslate"><span class="pre">marketing.example.com</span></code>, and set
-<code class="docutils literal notranslate"><span class="pre">p=none</span></code> in that DMARC record</li>
+your domain (e.g. <code class="docutils literal notranslate"><span class="pre">noreply&#64;news.example.com</span></code>), and then create
+separate SPF and DMARC records on <code class="docutils literal notranslate"><span class="pre">news.example.com</span></code>, and set
+<code class="docutils literal notranslate"><span class="pre">p=none</span></code> in that DMARC record.</li>
 </ol>
 <blockquote>
 <div><div class="admonition warning">