Hyperlint Automation Fix

Author: hyperlint-ai[bot]

src/content/docs/fundamentals/setup/troubleshooting.mdx

@@ -44,14 +44,14 @@ When you [set up Cloudflare](/fundamentals/setup/), you may experience the follo
 * [DNS FAQ](/dns/troubleshooting/faq/)
 * [SSL/TLS FAQ](/ssl/troubleshooting/faq/)
 
-## Is Cloudflare attacking me?
+## Is Cloudflare attacking me
 
-There are two common scenarios where Cloudflare is falsely perceived to attack your site:
+Two common scenarios falsely lead to the perception that Cloudflare is attacking your site:
 
 * Unless you [restore the original visitor IP addresses](/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/), Cloudflare IP addresses appear in your server logs for all proxied requests.
 * The attacker is spoofing Cloudflare's IPs. Cloudflare only [sends traffic to your origin web server over a few specific ports](/fundamentals/reference/network-ports/) unless you use [Cloudflare Spectrum](/spectrum/).
 
-Ideally, because Cloudflare is a reverse proxy, your hosting provider observes attack traffic connecting from [Cloudflare IP addresses](https://www.cloudflare.com/ips/). In contrast, if you notice connections from IP addresses that do not belong to Cloudflare, the attack is direct to your origin web server. Cloudflare cannot stop attacks directly to your origin IP address because the traffic bypasses Cloudflare’s network.
+Ideally, because Cloudflare is a reverse proxy, your hosting provider observes attack traffic connecting from [Cloudflare IP addresses](https://www.cloudflare.com/ips/). In contrast, if you notice connections from IP addresses that do not belong to Cloudflare, the attack is direct to your origin web server. Cloudflare cannot stop attacks directly to your origin IP address because the traffic bypasses Cloudflare's network.
 
 :::note