Add CNAME record example to how-it-works

Author: RebeccaTamachiro

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

@@ -9,6 +9,8 @@ head:
 
 ---
 
+import { Example } from "~/components";
+
 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.
@@ -18,7 +20,17 @@ To give the SaaS provider permission to route traffic through their zone, any cu
 
 ## 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 have your own Cloudflare zone (`example.com`) and your zone contains a [proxied DNS record](/dns/manage-dns-records/reference/proxied-dns-records/) matching the custom hostname (`mystore.example.com`) with a **CNAME** target defined by the SaaS Provider, then O2O will be enabled.
+
+<Example>
+
+DNS management for **example.com**
+
+| **Type** | **Name**     | **Target**                  | **Proxy status** |
+| -------- | ------------ | --------------------------------- | ---------------- |
+| `CNAME`  | `mystore`    | `customers.saasprovider.com` | Proxied          |
+
+</Example>
 
 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.
 

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx

@@ -32,7 +32,7 @@ The `CNAME` target — optional, but highly encouraged — provides a friendly a
 
 <Example>
 
-| **Type** | **Name**     | **IPv4 address**                  | **Proxy status** |
+| **Type** | **Name**     | **Target**                  | **Proxy status** |
 | -------- | ------------ | --------------------------------- | ---------------- |
 | `CNAME`  | `.customers` | `proxy-fallback.saasprovider.com` | Proxied          |