Update hostname-routing.mdx

Author: dinasaur404

src/content/docs/cloudflare-for-platforms/workers-for-platforms/get-started/hostname-routing.mdx

@@ -8,7 +8,7 @@ sidebar:
 
 import { Render, PackageManagers, WranglerConfig } from "~/components";
 
-You can use [dynamic dispatch](/cloudflare-for-platforms/workers-for-platforms/get-started/dynamic-dispatch/) Workers to route millions of vanity domains or subdomains to Workers without hitting traditional route limits. These hostnames can be subdomains under your managed domain (e.g. `customer1.saas.com`) or vanity domains controlled by your end customers (e.g. `mystore.com`), which can be managed through [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/). 
+You can use [dynamic dispatch](/cloudflare-for-platforms/workers-for-platforms/get-started/dynamic-dispatch/) Workers to route millions of vanity domains or subdomains to Workers without hitting traditional [route limits](/workers/platform/limits/#number-of-routes-per-zone). These hostnames can be subdomains under your managed domain (e.g. `customer1.saas.com`) or vanity domains controlled by your end customers (e.g. `mystore.com`), which can be managed through [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/). 
 
 ## (Recommended) Wildcard route with a dispatch Worker
 
@@ -109,4 +109,4 @@ The table below shows when Workers are invoked based on your route pattern and t
 |-----------------------|--------------|------------|
 | `*/*` (Recommended)   | ✅           | ✅         | 
 | Target hostname route | ✅           | ❌         |
-| Custom hostname route | ❌           | ✅         |
+| Custom hostname route | ❌           | ✅         |