fix: fix typo in jit compiler docs

[Willem-Jaap]

Fix small typo

Summary by CodeRabbit

• Documentation
  • Updated documentation to clarify how Elysia achieves speed.
  • Fixed spelling corrections in documentation.

[coderabbitai]

Warning

Rate limit exceeded

@Willem-Jaap has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 37 minutes and 7 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: df4f3dbe-3181-4ba4-9619-5ccbc09b3280

📥 Commits

Reviewing files that changed from the base of the PR and between 862a2fb and 6728e05.

📒 Files selected for processing (1)

• docs/internal/jit-compiler.md

Walkthrough

A single line in the JIT compiler documentation is corrected: the typo "acheived" becomes "achieved," and the sentence is revised to clarify that Elysia's speed results from both runtime-specific optimizations and its route registration and request handling approach.

Changes

Documentation Enhancement

Layer / File(s)	Summary
Typo correction and clarity enhancement docs/internal/jit-compiler.md	The word "acheived" is corrected to "achieved" and the introductory sentence is revised to emphasize that Elysia's speed comes from both runtime-specific optimizations and how it performs route registration and request handling.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

You fixed a typo, how... thrilling ♡~
A single character swapped with such grace, (´～｀)
"Acheived" to "achieved"—oh so trivial~
Barely a dent in the reviewing race (´∇｀)
But I suppose even docs need their fix, ehehe ♡

🚥 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 summarizes the main change—fixing a typo ('acheived' → 'achieved') in the JIT compiler documentation.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

🤖 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