docs: correct terminology from 'tasks' to 'modes' in sticky models se…

[hannesrudolph]

…ction for consistency

---

Important

Corrects terminology from 'tasks' to 'modes' in using-modes.md for consistency.

• Documentation:
  • Corrects terminology from 'tasks' to 'modes' in using-modes.md for consistency in the Sticky Models section.

^{This description was created by for 6b7fb14. You can customize this summary. It will automatically update as commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
roo-code-docs	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Apr 19, 2025 0:23am

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 6b7fb14 in 51 seconds

More details

• Looked at 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. docs/basic-usage/using-modes.md:6

• Draft comment:
  Good update: changing 'tasks' to 'modes' clearly aligns the terminology across documentation. Ensure all related docs use the same consistent terminology.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 20% <= threshold 50%
  This comment is asking the author to ensure consistency in terminology across documentation. It doesn't provide a specific code suggestion or point out a specific issue in the code itself. It seems to be more of a general request for consistency, which doesn't align with the rules provided.

2. docs/basic-usage/using-modes.md:6

• Draft comment:
  Renamed 'tasks' to 'modes' for consistency with the rest of the documentation. Please ensure that all similar references are updated accordingly.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to ensure that all similar references are updated, which violates the rule against asking the author to double-check things. The comment is not making a specific code suggestion or pointing out a specific issue, but rather giving a general instruction.

3. docs/basic-usage/using-modes.md:5

• Draft comment:
  There's a typographical error in the admonition block declaration on line 5. The markdown syntax for an info block typically requires three colons (:::info Sticky Models) instead of four (::::info Sticky Models). Please correct it.
• Reason this comment was not posted:
  Comment was on unchanged code.

Workflow ID: wflow_SPvNiPnv7goHG70F

---

You can teach Ellipsis what to look for with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.