docs: Rename section to 'Inline as'

[PatrykKuniczak]

Unify title of "inline" section, with others.

Summary by CodeRabbit

• Documentation
  • Updated plugin documentation for clarity regarding event listener parameters and scope casting behavior.

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

[coderabbitai]

Walkthrough

Documentation update to the plugin guide clarifying scope casting behavior. The subsection heading "Inline" was renamed to "Inline as" and a descriptive sentence was added explaining that event listeners accept an as parameter for scope specification.

Changes

Cohort / File(s)	Summary
Documentation updates docs/essential/plugin.md	Updated subsection heading from "Inline" to "Inline as" and added clarification that event listeners accept the as parameter to specify hook scope

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

No logic or functional changes—purely documentation wording and heading refinement.

Poem

🐰 A heading hops from old to new,
"Inline as" shines, the docs ring true!
The as parameter, once unclear,
Now whispers softly: "Scope is here!"
Small words, big clarity—hop, hop, cheer! 🎉

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 describes the main change: renaming a section heading from 'Inline' to 'Inline as' in the 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 70f8a0f and 5464860.

📒 Files selected for processing (1)

• docs/essential/plugin.md (1 hunks)

🔇 Additional comments (1)

docs/essential/plugin.md (1)

586-587: Approve: Clear and consistent heading and introductory sentence.

The heading change from "Inline" to "Inline as" unifies the naming scheme with the adjacent subsections ("Guard as" and "Instance as"), improving consistency and parallel structure. The new introductory sentence establishes the general principle before the code examples, providing helpful context for readers.

The heading anchor will auto-generate as #inline-as, which aligns correctly with the reference link at line 582.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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