Fix middleware docs wording

[BboyGT]

Type of change

• Documentation update

Summary

• Clarifies the middleware control flow when a middleware returns a regular Response.
• Uses consistent wording for NextResponse.next() by saying the request proceeds to the router.

How has this been tested?

• bun x prettier --check docs/content/docs/middleware.mdx

Checklist

• I have reviewed the changed documentation.
• This is a docs-only change, so no runtime tests were needed.
• The updated file passes Prettier.

Addresses #3

Summary by CodeRabbit

• Documentation
  • Clarified middleware control-flow: explicitly distinguishes between sending a response (which short-circuits and bypasses routing) and allowing the request to continue to normal routing/handler processing.

[netlify]

❌ Deploy Preview for polite-rabanadas-e7f4e1 failed.

Name	Link
🔨 Latest commit	2290c6b
🔍 Latest deploy log	https://app.netlify.com/projects/polite-rabanadas-e7f4e1/deploys/69fd8b765b820400083bd6a9

[vercel]

@BboyGT is attempting to deploy a commit to the kessud2021's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5130d1cd-78b8-4eae-b98a-158a8b8fd64c

📥 Commits

Reviewing files that changed from the base of the PR and between 971ffc5 and 2290c6b.

📒 Files selected for processing (1)

• docs/content/docs/middleware.mdx

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

• docs/content/docs/middleware.mdx

---

📝 Walkthrough

Walkthrough

The middleware documentation is clarified in the "How It Works" section to explicitly distinguish between two control flow paths: when middleware returns a generic Response object (request short-circuits and routing does not occur) versus when it returns NextResponse.next() (request proceeds normally). The IMPORTANT note block remains unchanged.

Changes

Middleware Control Flow Clarification

Layer / File(s)	Summary
Documentation Clarification docs/content/docs/middleware.mdx	The "How It Works" section is updated to explicitly separate and clarify the behavior when middleware returns a generic Response object (short-circuits routing) versus NextResponse.next() (proceeds normally).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hops through middleware's way,
"Short-circuit here, continue there," they say,
Response or Next—the paths now clear,
Control flow dancing without cheer. 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: improving the wording in the middleware documentation.
Description check	✅ Passed	The description covers the main change, testing approach, and a checklist, though it deviates from the template structure by providing a custom format instead of following all template sections.
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/content/docs/middleware.mdx`:
- Line 79: Replace the phrase "proceeds normally" in the sentence describing
NextResponse.next() with the consistent terminology "proceeds to the router" so
the line that reads "If middleware returns `NextResponse.next()`, the request
proceeds normally" becomes "If middleware returns `NextResponse.next()`, the
request proceeds to the router" to match other occurrences like "Continue to the
router" and maintain consistency around `NextResponse.next()`.

🪄 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: e4cbb623-b445-4db7-9f66-1829fe2656f7

📥 Commits

Reviewing files that changed from the base of the PR and between 4645f54 and 971ffc5.

📒 Files selected for processing (1)

• docs/content/docs/middleware.mdx