Bring 'With O2O' higher and provide intro to the CNAME record

Author: RebeccaTamachiro

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx

@@ -11,50 +11,52 @@ head:
 
 Orange-to-Orange (O2O) is a specific traffic routing configuration where traffic routes through two Cloudflare zones: the first Cloudflare zone is owned by customer 1 and the second Cloudflare zone is owned by customer 2, who is considered a SaaS provider.
 
-If one or more hostnames are onboarded to a SaaS Provider that uses Cloudflare products as part of their platform, specifically the [Cloudflare for SaaS product](/cloudflare-for-platforms/cloudflare-for-saas/), those hostnames will be created as [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) in the SaaS Provider's zone. The custom hostnames must be activated by the SaaS customer to give the SaaS provider permission to route traffic for the hostname through their zone.
+If one or more hostnames are onboarded to a SaaS Provider that uses Cloudflare products as part of their platform - specifically the [Cloudflare for SaaS product](/cloudflare-for-platforms/cloudflare-for-saas/) - those hostnames will be created as [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) in the SaaS Provider's zone.
 
-## Without O2O
+To give the SaaS provider permission to route traffic through their zone, any custom hostname must be activated by you (the SaaS customer) by placing a [CNAME record](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/#3-have-customer-create-cname-record) on your authoritative DNS. If your authoritative DNS is Cloudflare, you have the option to [proxy](/fundamentals/concepts/how-cloudflare-works/#application-services) your CNAME record, achieving an Orange-to-Orange setup.
 
-If you do not have your own Cloudflare zone and have only onboarded one or more of your hostnames to a SaaS Provider, then O2O will not be enabled.
 
-Without O2O enabled, the settings configured in the SaaS Provider's zone will be applied to the traffic.
+## With O2O
+
+If you have your own Cloudflare zone and your zone contains a **proxied** DNS record matching the custom hostname with a **CNAME** target provided by the SaaS Provider, then O2O will be enabled.
+
+With O2O enabled, the settings configured in your Cloudflare zone will be applied to the traffic first, and then the settings configured in the SaaS provider's zone will be applied to the traffic second.
 
 ```mermaid
 flowchart TD
-accTitle: Your zone using a SaaS provider, but without O2O
+accTitle: O2O-enabled traffic flow diagram
 
 A[Website visitor]
 
 subgraph Cloudflare
-    B[SaaS Provider-owned zone]
+  B[Customer-owned zone]
+  C[SaaS Provider-owned zone]
 end
 
-C[SaaS Provider Origin]
+D[SaaS Provider Origin]
 
 A --> B
 B --> C
+C --> D
 ```
+## Without O2O
 
-## With O2O
-
-If you have your own Cloudflare zone and your zone contains a **proxied** DNS record matching the custom hostname with a **CNAME** target provided by the SaaS Provider, then O2O will be enabled.
+If you do not have your own Cloudflare zone and have only onboarded one or more of your hostnames to a SaaS Provider, then O2O will not be enabled.
 
-With O2O enabled, the settings configured in your Cloudflare zone will be applied to the traffic first, and then the settings configured in the SaaS provider's zone will be applied to the traffic second.
+Without O2O enabled, the settings configured in the SaaS Provider's zone will be applied to the traffic.
 
 ```mermaid
 flowchart TD
-accTitle: O2O-enabled traffic flow diagram
+accTitle: Your zone using a SaaS provider, but without O2O
 
 A[Website visitor]
 
 subgraph Cloudflare
-  B[Customer-owned zone]
-  C[SaaS Provider-owned zone]
+    B[SaaS Provider-owned zone]
 end
 
-D[SaaS Provider Origin]
+C[SaaS Provider Origin]
 
 A --> B
 B --> C
-C --> D
 ```