Text adjustments and consolidate info from create-ch content

Author: RebeccaTamachiro

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls.mdx

@@ -50,7 +50,7 @@ TO-DO: Add APIRequest example
 
 </Details>
 
-- Whenever you make changes to a custom hostname via Dashboard, the value that is set for Minimum TLS version will apply. Meaning it will override a zone-level configuration applied as in the scenario above.
+- Whenever you make changes to a custom hostname via dashboard, the value that is set for Minimum TLS version will apply. If you have a scenario as explained in the bullet above, the dashboard change will override the zone-level configuration that was being applied.
 
 - For custom hostnames with wildcards enabled, the direct custom hostname you create (`saas-customer.test`) will use the hostname-specific setting, while the others (`sub1.saas-customer.test`, `sub2.saas-customer.test`, etc) will default to the zone-level setting.
 

src/content/partials/cloudflare-for-platforms/create-custom-hostname-limitations.mdx

@@ -9,7 +9,7 @@
 When you create a custom hostname:
 
 * If you issue a custom hostname certificate with wildcards enabled, you cannot customize TLS settings for these wildcard hostnames.
-* If you do not specify the **Minimum TLS Version**, it defaults to 1.0, not the zone's Minimum TLS Version. You can still edit this setting after creation.
+* If you do not specify the **Minimum TLS Version**, it defaults to the zone's Minimum TLS Version. You can still [edit this setting](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#minimum-tls-version) after creation.
 
 
 :::