Update src/content/docs/reference-architecture/diagrams/network/bring-your-own-ip-space-to-cloudflare.mdx

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>

Author: securitypedant

src/content/docs/reference-architecture/diagrams/network/bring-your-own-ip-space-to-cloudflare.mdx

@@ -12,7 +12,7 @@ updated: 2024-10-24
 
 ## Introduction
 
-Cloudflare brings security and performance to our customers' digital estates. However, one of the challenges with proxying services is that interactions on the web (e.g. DNS queries, web requests to Internet or SaaS services, etc.) that go to Cloudflare will appear to the world as coming from Cloudflare IP space. This can create challenges for some enterprises.
+Cloudflare brings security and performance to our customers' digital estates. However, one of the challenges with proxying services is that interactions on the web (for example, DNS queries, web requests to Internet or SaaS services, etc.) that go to Cloudflare will appear to the world as coming from Cloudflare IP space. This can create challenges for some enterprises.
 
 For example, partners or other B2B relationships may use public IP space owned by a customer for attestation and attribution in various transactions. They may look at the resolved address for a public hostname (eg. [www.example.com](http://www.example.com)) and expect that IP to match a specific range or address known to be owned by the customer.