[SSL, Secrets Store, SaaS] Update limits (#22626)

* Update max secrets count to 100

* Update custom origin server as available to all

* Update max custom hostnames limit

Author: RebeccaTamachiro

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin.mdx

@@ -16,7 +16,6 @@ import { GlossaryTooltip, Render } from "~/components"
 
 To use a custom origin server, you need to meet the following requirements:
 
-* You have purchased the [Cloudflare for SaaS Enterprise plan](/cloudflare-for-platforms/cloudflare-for-saas/plans/) and the feature is properly entitled to your account.
 * Each custom origin needs to be a valid hostname with a proxied (orange-clouded) A, AAAA, or CNAME record in your account's DNS. You cannot use an IP address.
 * The DNS record for the custom origin server does not currently support wildcard values.
 

src/content/docs/secrets-store/manage-secrets/index.mdx

@@ -14,10 +14,10 @@ Once a secret is added to the Secrets Store, it can no longer be decrypted or ac
 
 ## Limits
 
-Customers who create a secrets store in the open beta can have up to 20 secrets per account. Also, there can only be one store per account.
+Customers who create a secrets store in the open beta can have up to 100 secrets per account. Also, there can only be one store per account.
 
 :::note[Production secrets]
-If you use [Wrangler](/secrets-store/manage-secrets/how-to/#manage-via-wrangler), there is a difference between production secrets and secrets that are only created locally (without the `--remote` flag). The limit of 20 secrets per account only considers production secrets.
+If you use [Wrangler](/secrets-store/manage-secrets/how-to/#manage-via-wrangler), there is a difference between production secrets and secrets that are only created locally (without the `--remote` flag). The limit of 100 secrets per account only considers production secrets.
 :::
 
 ## Resources

src/content/partials/cloudflare-for-platforms/get-started-fallback-origin.mdx

@@ -8,7 +8,7 @@ The fallback origin is where Cloudflare will route traffic sent to your custom h
 
 :::note
 
-If you are an Enterprise customer, you can route custom hostnames to distinct origins by using [custom origin server](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/).
+To route custom hostnames to distinct origins, refer to [custom origin server](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/).
 
 :::
 

src/content/plans/index.json

@@ -2720,10 +2720,10 @@
 				},
 				"c_max_hostnames": {
 					"title": "Max hostnames",
-					"free": "5,000",
-					"pro": "5,000",
-					"biz": "5,000",
-					"ent": "Unlimited, but contact sales if using over 5,000."
+					"free": "50,000",
+					"pro": "50,000",
+					"biz": "50,000",
+					"ent": "Unlimited, but contact sales if using over 50,000."
 				},
 				"d_cost_per_hostname": {
 					"title": "Price per additional hostname",
@@ -2741,9 +2741,9 @@
 				},
 				"custom_origin": {
 					"title": "[Custom origin](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/)",
-					"free": "No",
-					"pro": "No",
-					"biz": "No",
+					"free": "Yes",
+					"pro": "Yes",
+					"biz": "Yes",
 					"ent": "Yes"
 				},
 				"custom_certificates": {