[Fundamentals] Revised adding a site to CF

public/__redirects

@@ -625,6 +625,7 @@
 /fundamentals/concepts/what-is-cloudflare/ https://www.cloudflare.com/learning/what-is-cloudflare/ 301
 /fundamentals/concepts/the-internet/ https://www.cloudflare.com/learning/network-layer/how-does-the-internet-work/ 301
 /fundamentals/concepts/free-plan/ /fundamentals/subscriptions-and-billing/free-plan/ 301
+/fundamentals/setup/manage-domains/connect-your-domain/ /fundamentals/setup/manage-domains/add-site/ 301
 
 # gateway
 /gateway/about/ /cloudflare-one/policies/gateway/ 301

src/content/docs/fundamentals/setup/manage-domains/add-site.mdx

@@ -6,25 +6,17 @@ pcx_content_type: tutorial
 
 import { Render } from "~/components"
 
-Follow these steps to onboard your website or application to Cloudflare. Once your domain is [active](/dns/zone-setups/reference/domain-status/#active), your web traffic will [proxy through Cloudflare](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy), which speeds up and protects websites and services on your domain.
+If you purchased your domain from a different provider, you can still connect the domain to Cloudflare. After you connect your domain to Cloudflare, Cloudflare will act as the [reverse proxy](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy) and [DNS provider](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) for your site.
 
-Cloudflare will become the primary [DNS provider](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-dns-provider) for your domain, meaning your [DNS records](/dns/concepts/#dns-records) are managed at Cloudflare, and we authoritatively answer all DNS queries.
+The information below applies to a [full DNS setup](/dns/zone-setups/full-setup) which is the most common configuration.
 
 :::note
-
-
-These instructions are tailored to customers using a [full DNS setup](/dns/zone-setups/full-setup) (the most common configuration). If you are using a [partial setup](/dns/zone-setups/partial-setup/) or [secondary setup](/dns/zone-setups/zone-transfers/), your onboarding process will be different.
-
-
+To use Cloudflare as a reverse proxy but maintain your DNS provider, refer to [partial setup](/dns/zone-setups/partial-setup/). To use one more DNS providers, refer to or [DNS Zone transfers](/dns/zone-setups/zone-transfers/).
 :::
 
 ## Prerequisites
 
-To onboard a website or application to Cloudflare, you need to own the domain name (`example.com`).
-
-If you do not already own a domain and plan to use Cloudflare for your [authoritative DNS](/dns/zone-setups/full-setup/), we highly recommend purchasing your domain name through [Cloudflare Registrar](/registrar/get-started/register-domain/). This simplifies your setup process by automatically using Cloudflare for authoritative DNS.
-
-<Render file="disable_dnssec" product="dns" />
+[Disable DNSSEC](/dns/dnssec/#disable-dnssec) at the registrar where you purchased your domain name to avoid connectivity errors when you change your nameservers.
 
 ## 1. Add site in Cloudflare
 
@@ -36,8 +28,6 @@ If you do not already own a domain and plan to use Cloudflare for your [authorit
 
 ## 3. Complete SSL/TLS setup
 
-To prevent insecure connections and visitor browser errors, [make sure you have SSL/TLS protection](/ssl/get-started/).
-
-Many Cloudflare services will automatically protect and speed up your web traffic once your nameservers are updated.
+To prevent insecure connections and visitor browser errors, [enable SSL/TLS protection](/ssl/get-started/). Many Cloudflare services will automatically protect and speed up your web traffic after your nameservers are updated.
 
-To get more out of Cloudflare, refer to the [Security](/fundamentals/security/) and [Performance](/fundamentals/performance/) tasks.
+If you encounter unexpected results when changing your nameservers, refer to the [DNS Full Setup troubleshooting](/dns/zone-setups/full-setup/troubleshooting/).

src/content/partials/fundamentals/add-site.mdx

@@ -14,7 +14,7 @@ import { GlossaryTooltip, Render } from "~/components";
    :::
 
 4. Select a [plan](https://www.cloudflare.com/plans/#compare-features).
-5. Make sure we have all of your [DNS records](/dns/manage-dns-records/).
+5. [Review your DNS records](/dns/zone-setups/full-setup/setup/#review-dns-records) to ensure none are missing. Your DNS records must accurate for your domain to work properly.
 
    <Render file="dns-scan-intro" product="dns" /> <br />
 

src/content/partials/fundamentals/update-nameservers.mdx

@@ -7,6 +7,6 @@ import { Render } from "~/components"
 
 <Render file="nameserver-preamble" product="dns" /> <br/>
 
-Before your domain can begin using Cloudflare for DNS resolution, you need to [add these nameservers](/dns/zone-setups/full-setup/setup/#update-your-nameservers) at your registrar. Make sure DNSSEC **is disabled** at this point.
+Before your domain can begin using Cloudflare for DNS resolution, you need to [add these nameservers](/dns/zone-setups/full-setup/setup/#update-your-nameservers) at your registrar. DNSSEC should still be **disabled** at this point.
 
 <Render file="minimize-downtime-tip" product="dns" />