docs: improve grammar in blog/elysia-02.md

[DaxServer]

Summary by CodeRabbit

• Documentation
  • Polished blog post with grammar, pluralization, and wording improvements.
  • Clarified feature descriptions (lazy loading, deferred modules, plugin/app lifecycle).
  • Refined OpenAPI/Schema explanations, including field descriptions, union types, validation, and multiple responses.
  • Standardized capitalization, pluralization, and list formatting; updated examples for consistency.
  • Improved phrasing for capability announcements and community updates.
  • No structural or functional changes; content clarity and consistency only.

[coderabbitai]

Walkthrough

Edits are limited to a single blog post file, applying copy and grammar fixes, pluralization and consistency adjustments, and refined descriptions in OpenAPI/Schema sections. No structural, feature, or code/API changes were made.

Changes

Cohort / File(s)	Summary
Docs editorial updates docs/blog/elysia-02.md	Copyedits: grammar, pluralization, and consistency; revised phrasing around lazy loading, deferred modules, plugin/app lifecycle sequencing; clarified OpenAPI/Schema field descriptions; standardized capitalization and list wording. No functional changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I twitch my ears at polished prose,
Hopping through commas where clarity grows.
Plurals aligned, the schemas now rhyme,
Deferred delights arrive right on time.
In docs we nibble, refine, and preen—
A tidy burrow, crisp and clean. 🐇✨

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 "docs: improve grammar in blog/elysia-02.md" succinctly and accurately summarizes the main change—editorial grammar improvements to that specific blog post. It is concise, specific, and directly aligned with the changes in the diff and PR objectives, so a reviewer can quickly understand the intent.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

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

---

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: 0

🧹 Nitpick comments (7)

docs/blog/elysia-02.md (7)

75-78: Prefer lowercase “schema” for consistency.
Use “schema fields” unless referring to a proper API object.

Apply this diff:

-Now Elysia can memorize schemas and reference them directly in Schema fields, without creating an import file via `Elysia.setModel`.
+Now Elysia can memorize schemas and reference them directly in schema fields, without creating an import file via `Elysia.setModel`.

---

109-116: OpenAPI terminology may be inaccurate; suggest standard phrasing.
Consider aligning with “OpenAPI Specification v2.0 (Swagger 2.0)”.

-Introducing a new field, `schema.detail`, for customizing details for the route, following the standard of OpenAPI Schema V2 with auto-completion.
+Introducing a new field, `schema.detail`, for customizing route details, following the OpenAPI Specification v2.0 (Swagger) with auto-completion.

---

118-121: Union types wording nits.
Minor clarity/consistency tweaks.

-The previous version of Elysia sometimes had problems with distinct Union types, as Elysia tried to catch the response to create a full type reference for Eden.
+The previous version of Elysia sometimes had problems with distinct union types, as Elysia tried to capture the response to create a full type reference for Eden.
-This resulted in invalidation of possible types.
+This sometimes invalidated the set of possible types.

---

123-124: Simplify “Union Response” sentence.
Streamline and lowercase “union types”.

-Made possible by Union Type, returning multiple response statuses for `schema` is now available using `schema.response[statusCode]`.
+Enabled by union types, multiple response statuses are now supported via `schema.response[statusCode]`.

---

164-167: Ecosystem bullets: minor wording tweaks.
Tighten phrasing and hyphenation.

-- Eden with union-type inference for multiple responses
+- Eden with union type inference for multiple responses
-- New Elysia Apollo Plugin for Elysia
+- New Apollo plugin for Elysia

---

169-172: Capitalize HTTP header and fix example formatting.
Use canonical “Content-Type” and parameter spacing.

-- Body parser now parses `content-type` with extra attributes, e.g., `application/json;charset=utf-8`
+- Body parser now parses the `Content-Type` header with extra attributes, e.g., `application/json; charset=utf-8`

---

176-179: Fix nested list indentation (markdownlint MD007).
Indent nested bullet with 2 spaces (not 4).

-    - To migrate, add `.request` to context to access `Request`
+  - To migrate, add `.request` to context to access `Request`

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5e971d8 and f30e3da.

📒 Files selected for processing (1)

• docs/blog/elysia-02.md (4 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

docs/blog/elysia-02.md

178-178: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

🔇 Additional comments (7)

docs/blog/elysia-02.md (7)

41-42: Good copy edit; reads clearly.
Improved flow and pluralization look correct.

---

47-51: Defers/lazy‑loading phrasing looks correct.
Grammar and clarity improvements are accurate.

---

72-72: Type inference sentence: LGTM.
Clear and correct.

---

96-107: Reference model section copy: LGTM.
Concise and consistent.

---

151-154: Union response validation and Swagger note: LGTM.
Accurate and clear.

---

156-159: Type inference performance note: LGTM.
Concise and informative.

---

181-188: Closing section edits: LGTM.
Reads naturally and consistently.