Summary

Corrects misleading examples in the Workers Routes documentation for hostnames beginning with *.

The previous documentation stated that *example.com/* would not match https://not-example.com/, which contradicts the definition that * matches zero or more of any character. This update fixes the example table and adds a note explaining that route patterns are evaluated within their associated zone, which means cross-domain hostnames like myexample.com or not-example.com would not reach the example.com zone in practice.

Additionally, this update adds subdomain wildcard examples (*sub.example.com/* vs *.sub.example.com/*) to illustrate the more common and relevant scenario where unintended matches can occur within a zone.

Fixes the feedback raised in the community regarding misleading/incorrect wildcard route pattern documentation.

Documentation checklist

• The change adheres to the documentation style guide.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.