Clarify note about churned customer and move under #domains-using-cf

Author: RebeccaTamachiro

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/remove-custom-hostnames.mdx

@@ -22,12 +22,12 @@ If they update their [`CNAME` record](/cloudflare-for-platforms/cloudflare-for-s
 
 If the custom hostname is in a **Moved** state for seven days, it will transition into a **Deleted** state.
 
+You should remove a customer's custom hostname from your zone if they decide to churn. This is especially important if your end customers are using Cloudflare because if the churned customer changes the DNS target to point away from your SaaS zone but you have not removed it, the custom hostname will continue to route to your service. This is a result of the [custom hostname priority logic](/ssl/reference/certificate-and-hostname-priority/#hostname-priority).
+
 ## Domains not using Cloudflare
 
 If your customer's domain is not using Cloudflare, you must remove a customer's custom hostname from your zone if they decide to churn.
 
-This is especially important if your end customers are using Cloudflare because if the custom hostname changes the DNS target to point away from your SaaS zone, the custom hostname will continue to route to your service. This is a result of the [custom hostname priority logic](/ssl/reference/certificate-and-hostname-priority/#hostname-priority).
-
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
 <Render file="delete-custom-hostname-dash" product="cloudflare-for-platforms" />