diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata.mdx
index d0b110ff7561a70..e8f884b48558d1a 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata.mdx
@@ -117,10 +117,8 @@ There are some limitations to the metadata that can be provided to Cloudflare:
- Any origin resolution — for example, directing requests for a given hostname to a specific backend — must be provided as a hostname that exists within Cloudflare's DNS (even for non-authoritative setups). Providing an IP address directly will cause requests to error.
- The total payload must not exceed 4 KB.
- It requires a Cloudflare Worker that knows how to process the schema and trigger logic based on the contents.
-- Custom metadata cannot be set on custom hostnames that contain wildcards.
:::note
-
Be careful when modifying the schema. Adding, removing, or changing keys and possible values may cause the Cloudflare Worker to either ignore the data or return an error for requests that trigger it.
:::
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
index 703044571626dc4..88b65c77d4d101c 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames.mdx
@@ -36,7 +36,7 @@ head:
| 400 | 1409 | Reserved top domain custom hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again. |
| 400 | 1410 | Unable to parse custom hostname - `:reason`. Check your input and try again.
**Reasons:**
publicsuffix: cannot derive eTLD+1 for domain `:domain`
publicsuffix: invalid public suffix `:suffix` for domain `:domain` |
| 400 | 1411 | Custom hostnames ending in example.com, example.net, or example.org are prohibited. Check your input and try again. |
-| 400 | 1412 | Custom metadata for wildcard custom hostnames is not supported. Check your input and try again. |
+| 400 | 1412 | Custom metadata for wildcard custom hostnames is not supported. Check your input and try again.
**Note:**
This message is only presented to customers who have opted out of wildcard support for custom metadata. |
| 400 | 1415 | Invalid custom origin hostname. Custom origin hostnames have to be smaller than 256 characters in length, cannot be IP addresses, cannot contain any special characters such as ~~\`\`~~\`!@#$%^&\*()=+{}\[]\\ |
| 400 | 1416 | Custom origin hostnames with non-ASCII characters are not supported. Check your input and try again. |
| 400 | 1417 | Reserved top domain custom origin hostnames, such as 'test', 'example', 'invalid' or 'localhost', is not supported. Check your input and try again. |