docs: use correct line highlight for 0.9.x api changes

[steveb05]

This PR fixes an error introduced in commit 3d700ea where the wrong line highlight was used in code blocks. This resulted in incorrect styling.

Summary by CodeRabbit

• Documentation
  • Updated documentation to reflect changes in sound handling and threading for version 0.9.X.
  • Clarified new requirements for wrapping sound values and accessing sound properties with player and context parameters.
  • Revised code examples and explanations to match updated API signatures and usage.
  • Added guidance on obtaining interaction context and updated threading usage instructions.

[coderabbitai]

Walkthrough

The documentation for version 0.9.X has been updated to reflect API changes concerning sound handling and threading. This includes modifications to method signatures, property types, and usage patterns, as well as updated code snippets and clarifications regarding context handling and coroutine dispatchers.

Changes

Cohort / File(s)	Change Summary
API Documentation Updates documentation/docs/develop/02-extensions/09-api-changes/0.9.mdx	Updated documentation to describe changes in sound and threading APIs, including new method signatures, property types, code snippets, and usage of coroutine dispatchers.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~6 minutes

Suggested labels

codex

Poem

A sound now wrapped in Var’s embrace,
With context passed from place to place.
Threads dispatched with coroutines new,
The docs refreshed for every crew.
So let’s all cheer this tidy tune—
Hoppity hop, improvements soon!
🐇🎶

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ 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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

documentation/docs/develop/02-extensions/09-api-changes/0.9.mdx (2)

74-88: Prefer separate blocks or start/end markers for clearer diffs

The snippet embeds two full CustomEntityDefinition declarations in the same ```kotlin block and relies on single-line // highlight-red|green comments to indicate changes.
Readers (and some syntax-highlight plug-ins) can misinterpret this as duplicated code rather than an old/new diff. Either:

1. Wrap the old & new versions in two distinct code blocks, or
2. Keep them in one block but switch to // highlight-red-start / // highlight-red-end (and the green equivalents) so the entire “old” and “new” fragments are visually grouped.

This small tweak makes the change more obvious and prevents accidental copy-pastes of the obsolete version.

---

146-153: Align highlight style across the page for consistency

Earlier sections use single-line // highlight-red / // highlight-green, while this block adopts the start/end pair. Mixing the two styles works but feels inconsistent. Adopting the start/end form everywhere (or documenting when each variant should be used) will make future maintenance easier.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3d700ea and a16c17d.

📒 Files selected for processing (1)

• documentation/docs/develop/02-extensions/09-api-changes/0.9.mdx (3 hunks)

🔇 Additional comments (1)

documentation/docs/develop/02-extensions/09-api-changes/0.9.mdx (1)

122-130: LGTM – correct multi-line highlight syntax

Good move using highlight-red-start/end and highlight-green-start/end here; it cleanly brackets the before/after lines and fixes the previous mis-highlight.