Further disambiguate Customer1 is not a SaaS provider

Author: RebeccaTamachiro

src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx

@@ -79,7 +79,7 @@ Customer1 uses Cloudflare as authoritative DNS for the zone `shop.example.com`.
 
 * If Customer1 wants to regain control of their zone, Customer1 contacts Customer2 and requests them to delete the custom hostname record. Customer1 should make sure to have their record target updated to something other than the SaaS provider target, otherwise Customer1 would get a [`1014` error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1014-cname-cross-user-banned).
 * If Customer1 already has a proxied record for `www.example.com` when Customer2 creates and verifies `www.example.com`,  [Orange-to-Orange](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) applies.
-* If Customer1 already has a proxied record for `www.example.com` in a legacy custom hostname setup and Customer2 creates and verifies a new wildcard custom hostname for `*.example.com`, traffic is routed to Customer1's due to exact hostname match taking precedence.
+* If Customer1 already has a proxied record for `www.example.com` in a legacy custom hostname setup and Customer2 creates and verifies a new wildcard custom hostname for `*.example.com`, legacy custom hostname takes precedence due to exact hostname match.
 
 #### Scenario 2