docs: fix warning syntax

[mendonk]

This pull request makes a minor documentation fix by correcting the markdown syntax for a warning callout in the release notes. This change improves the formatting and visibility of an important security warning for users

[coderabbitai]

Walkthrough

Updated documentation admonition casing in release notes by changing two instances of :::Warning to :::warning. No content or behavioral changes.

Changes

Cohort / File(s)	Summary
Docs admonition casing docs/docs/Support/release-notes.mdx	Replaced two occurrences of the admonition directive from :::Warning to :::warning in known-issues sections.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• docs: revert desktop warning #10040 — Also modifies the same release-notes file, removing the Windows Desktop warning block.
• docs: windows desktop update issue #10041 — Updates/introduces Windows Desktop 1.6.0 known-issue warnings in the same file edited here.
• docs: windows desktop update issue #10029 — Adds a Windows update warning near the 1.6.0 known-issue blocks changed in this PR.

Suggested labels

documentation, lgtm

Suggested reviewers

• aimurphy
• italojohnny
• Cristhianzl

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Test File Naming And Structure	⚠️ Warning	I found numerous backend tests named test_*.py under backend/tests with standard pytest structures, some frontend Playwright specs named *.spec.ts instead of *.test.ts(x), and integration-like suites inside tests/integration without explicit identification; while individual tests are descriptive and include positive and negative scenarios, the presence of *.spec.ts violates the required naming convention for frontend tests.	Please rename frontend Playwright suites from *.spec.ts to *.test.ts so they match the mandated pattern, and document or restructure integration suites to ensure they are clearly marked in appropriate directories.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly reflects the primary change of correcting the warning callout syntax in documentation, aligns with conventional commit prefixes, and clearly communicates the modification without extraneous detail.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Test Coverage For New Implementations	✅ Passed	The PR only updates documentation formatting in docs/docs/Support/release-notes.mdx without introducing new functionality or bug fixes, so no corresponding tests are required and none are expected; hence the test coverage requirement is satisfied.
Test Quality And Coverage	✅ Passed	This pull request only adjusts markdown casing in documentation without modifying backend or frontend logic, so there is no new functionality that requires test coverage; consequently, existing test expectations remain unaffected and the absence of additional tests is appropriate.
Excessive Mock Usage Warning	✅ Passed	No test files were added or modified in this pull request; the only change adjusts callout casing within documentation, so there is no new or altered mock usage to evaluate and the existing test suite is unaffected by the update.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs-fix-note

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft