fix: fix typo in jit compiler docs

[Willem-Jaap]

Fix small typo

Summary by CodeRabbit

• Documentation
  • Clarified how Elysia achieves speed, including the role of runtime-specific optimizations and request/route handling.
  • Fixed spelling and wording issues in the JIT compiler documentation to improve readability.
  • Refined phrasing in the overhead description while preserving the original meaning.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0bbd5574-4d8f-4d10-ba67-e6f24297dc78

📥 Commits

Reviewing files that changed from the base of the PR and between 862a2fb and 8129b37.

📒 Files selected for processing (1)

• docs/internal/jit-compiler.md

✅ Files skipped from review due to trivial changes (1)

• docs/internal/jit-compiler.md

---

Walkthrough

The JIT compiler docs were edited in three places to fix typos and tighten wording, without changing any technical meaning. Tiny little cleanup work, how dazzlingly unexciting ♡

Changes

Documentation Cleanup

Layer / File(s)	Summary
Text corrections and wording cleanup docs/internal/jit-compiler.md	Fixes “acheived” to “achieved,” “happend” to “happens,” and “overkills” to “overkill,” with a small wording tweak in the opening sentence.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• elysiajs/documentation#806: Another documentation-only PR with typo-level markdown edits, so it’s closely aligned in scope.

Poem

Three typos fell down, one by one~ ♡
“Acheived” got corrected, the drama’s done (´～｀)
“Happend” and “overkills” couldn’t stay
Just tiny doc fixes stealing the day, nyahaha~ (╯✧▽✧)╯

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the documentation typo fixes in the JIT compiler docs.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/internal/jit-compiler.md`:
- Line 30: Rewrite the sentence to use the correct "not only ... but also ..."
construction and fix possessive and pluralization: replace the two fragmented
sentences with a single sentence such as "Elysia's speed is not only achieved by
optimization for specific runtimes (e.g., Bun native features like
`Bun.serve.routes`) but also by the way Elysia handles route registration and
request handling," ensuring "Elysia's" is possessive and "runtimes" and the
parenthetical example use correct punctuation.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 03f8ecae-df31-43d9-949d-eccaf9bbf8c4

📥 Commits

Reviewing files that changed from the base of the PR and between 121d058 and 862a2fb.

📒 Files selected for processing (1)

• docs/internal/jit-compiler.md