Flesh out use cases and clarify documentation

[stephent]

Love Hono and using it in my Cloudflare Worker project. One challenge I've run into several times is that the documentation often doesn't give any context for a feature or capability.

For example, Including slashes: it's not immediately apparent what this is intended to solve for. A one sentence description should make it obvious without having to crack out the regex debugger to see what the example actually does.

There are other examples, where, even if it seems obvious what something does, it's not obvious why you might ever want to use it.

There there are cases such as Routing with hostname, where there is a brief description, but the writing is unclear. The first 'it' presumably refers to Hono, but what about the second? And what is the Regex in this example demonstrating?

Yes, I could probably puzzle it out, but I think clearer explanations up front would save a lot of time and likely help a bunch of people in adopting Hono.