docs: Minor grammatical/rephrasing changes to Express migration doc

[OwenJRJones]

Minor grammatical/rephrasing changes throughout the doc for better clarity and readability

Summary by CodeRabbit

• Documentation
  • Improved the Express migration guide with editorial updates: fixed grammar, spelling, hyphenation, plurality, and terminology (e.g., "form data"), and corrected typos to enhance clarity and reading flow.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR makes editorial corrections to the Express migration guide documentation, adjusting grammar, spelling, hyphenation, and terminology without changing code or behavior.

Changes

Cohort / File(s)	Summary
Documentation corrections docs/migrate/from-express.md	Minor editorial edits: grammar and plurality adjustments, typo fixes (e.g., "simliar" → "similar"), terminology spacing ("formdata" → "form data"), and hyphenation consistency ("sub-router" / "subrouter"). No code or API changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Review focus: ensure wording preserves original meaning and no unintended content changes.

Possibly related PRs

• Fix Hono description & Express name in migration guides #644 — overlapping editorial fixes to docs/migrate/from-express.md, clarifying Express references and wording.

Poem

🐰 Ink on the page, a careful hop,
I nibble typos till they stop,
I tidy hyphens, space the sway,
A migration guide, polite and spry,
Hooray for clear docs — hop, hop, hooray!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: minor grammatical and rephrasing improvements to the Express migration documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4fa8eca and 58b32b7.

📒 Files selected for processing (1)

• docs/migrate/from-express.md (25 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/migrate/from-express.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (2)

docs/migrate/from-express.md (2)

848-848: Hyphenate "route-specific" as a compound adjective.

Line 848 uses "route specific error handler" which should use a hyphen since it's a compound adjective modifying "error handler".

Apply this diff:

-2. Shorthand for mapping HTTP status and `toResponse` for mapping error to a response
-3. Custom error code for each error
+2. Shorthand for mapping HTTP status and `toResponse` for mapping error to a response
+3. Custom error code for each error

More specifically, the text "route specific error handler" should be "route-specific error handler":

-1. Both global and route specific error handler
+1. Both global and route-specific error handler

---

1153-1154: Reduce repetition of "Elysia" at the start of consecutive sentences.

Lines 1153–1154 contain three consecutive sentences that each begin with "Elysia", creating repetitive phrasing. This detracts from readability.

Consider rewording to vary sentence openers:

-Elysia will generate an OpenAPI specification based on the schema you provided, and validate the request and response based on the schema, and infer types automatically.
+Elysia generates an OpenAPI specification based on the schema you provided, validates the request and response, and infers types automatically.

 Elysia also appends the schema registered in `model` to the OpenAPI spec, allowing you to reference the model in a dedicated section in Swagger or Scalar UI.

Alternatively:

-Elysia will generate an OpenAPI specification based on the schema you provided, and validate the request and response based on the schema, and infer types automatically.
+Based on the schema you provided, Elysia generates an OpenAPI specification, validates requests and responses, and infers types automatically.

 Additionally, Elysia appends the schema registered in `model` to the OpenAPI spec, allowing you to reference the model in a dedicated section in Swagger or Scalar UI.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5e5da8b and 4fa8eca.

📒 Files selected for processing (1)

• docs/migrate/from-express.md (25 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/migrate/from-express.md

[grammar] ~114-~114: Ensure spelling is correct
Context: ...Handler Both Express and Elysia have a simliar property for accessing input parameters...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[grammar] ~848-~848: Use a hyphen to join words.
Context: ...ysia provides: 1. Both global and route specific error handler 2. Shorthand for ...

(QB_NEW_EN_HYPHEN)

---

[style] ~1154-~1154: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...schema, and infer types automatically. Elysia also appends the schema registered in `...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🔇 Additional comments (1)

docs/migrate/from-express.md (1)

1-1310: Overall: Strong editorial improvements for clarity and readability.

The PR successfully addresses numerous grammar, spelling, and wording issues throughout the Express migration guide. Changes like correcting "use" to "uses," improving hyphenation ("sub-router"), and refining technical descriptions enhance the document's professionalism and clarity. The amendments align well with the stated objective of improving grammar and readability.