New Crowdin updates

[elibosley]

Summary by CodeRabbit

• Documentation
  • Standardized heading anchors and emphasis markup across many localized release notes and MDX docs for consistent Docusaurus rendering.
  • Normalized package/version and configuration identifier display (removed unnecessary escaping) so version strings and keys render clearly.
  • Cleaned up a few procedural pages to remove duplicated instruction lines and adjusted headings to improve in-page linking and readability.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	unraid-docs	128154a	Commit Preview URL Branch Preview URL	May 24 2026, 08:41 PM

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Localization docs sweep standardizes heading anchors, emphasis/underscore rendering, and minor instruction/style lines across many DE/ES/FR/JA/ZH release notes and select docs pages.

Changes

Localization release-notes and docs normalization

Layer / File(s)	Summary
General formatting and anchors update i18n/*/unraid-os/release-notes/*.md, i18n/*/.../removing-disks-from-array.mdx, i18n/zh/.../secure-your-boot-drive.mdx	Escaped MDX anchors in headings, normalized italics/bold and underscore escaping, relocated/retouched a few bullets, fixed duplicate dd-replacement instruction lines, and reformatted one inline style block.

Sequence Diagram(s)

(none)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• unraid/docs#488: Similar normalization of MDX heading anchors and escaping in localized 7.2.0 release notes.

Suggested reviewers

• ljm42

Poem

A rabbit with a pen and patch,
hops through headings, neat to match.
Stars replace the underscores,
anchors dock on docu-shores.
One X to swap, not two—hooray!
The docs now sing in every way.
(✿◠‿◠)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch l10n_main

[coderabbitai]

Actionable comments posted: 47

Note

Due to the large number of review comments, Critical severity comments were prioritized as inline comments.

🟡 Minor comments (9)

i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md-3-3 (1)

3-3: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove duplicate anchor comments from headings.

Three headings have duplicate anchor comments that need to be reduced to a single instance:

• Line 3: {/* #upgrade-notes */} appears twice
• Line 14: {/* #known-issues */} appears twice
• Line 49: {/* #rolling-back */} appears twice

✂️ Proposed fix

-## アップグレードに関する注意事項 {/* `#upgrade-notes` */} {/* `#upgrade-notes` */}
+## アップグレードに関する注意事項 {/* `#upgrade-notes` */}

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines: "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}"

Also applies to: 14-14, 49-49

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md`
at line 3, Remove the duplicate MDX-style anchor comments so each heading has a
single anchor comment using the MDX-safe syntax; for the heading "##
アップグレードに関する注意事項" remove the extra `{/* `#upgrade-notes` */}` leaving one, and do
the same for the headings with `{/* `#known-issues` */}` and `{/* `#rolling-back`
*/}` so each appears only once immediately after its heading text.

i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md-3-3 (1)

3-3: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove duplicate anchor comments from all headings.

Five headings have duplicate anchor comments that need to be reduced to a single instance each:

• Line 3: {/* #upgrade-notes */}
• Line 5: {/* #known-issues */}
• Line 9: {/* #rolling-back */}
• Line 24: {/* #fix-for-macvlan-call-traces */}
• Line 68: {/* #system-drivers-page */}

✂️ Proposed fix

-## アップグレードに関する注意事項 {/* `#upgrade-notes` */} {/* `#upgrade-notes` */}
+## アップグレードに関する注意事項 {/* `#upgrade-notes` */}

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

-## macvlan のコールトレースの修正 {/* `#fix-for-macvlan-call-traces` */} {/* `#fix-for-macvlan-call-traces` */}
+## macvlan のコールトレースの修正 {/* `#fix-for-macvlan-call-traces` */}

-## システムドライバー ページ {/* `#system-drivers-page` */} {/* `#system-drivers-page` */}
+## システムドライバー ページ {/* `#system-drivers-page` */}

As per coding guidelines: "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}"

Also applies to: 5-5, 9-9, 24-24, 68-68

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md`
at line 3, Remove duplicate anchor comments so each heading has only one
MDX-safe anchor comment; for the headings "アップグレードに関する注意事項" (anchor {/*
`#upgrade-notes` */}), the heading with anchor {/* `#known-issues` */}, the heading
with anchor {/* `#rolling-back` */}, the heading with anchor {/*
`#fix-for-macvlan-call-traces` */}, and the heading with anchor {/*
`#system-drivers-page` */} keep a single instance of the comment next to the
heading (e.g., "### Heading {/* `#stable-anchor` */}") and delete the extra
duplicate {/* ... */} comments elsewhere in the same file.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md-45-45 (1)

45-45: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove duplicate anchor comment.

This heading has the anchor comment duplicated twice: {/* #ext234-ntfs-and-exfat-support*/} {/*#ext234-ntfs-and-exfat-support */}. Only one anchor comment should be present.

✂️ Proposed fix

-#### Soporte para Ext2/3/4, NTFS y exFAT {/* `#ext234-ntfs-and-exfat-support` */} {/* `#ext234-ntfs-and-exfat-support` */}
+#### Soporte para Ext2/3/4, NTFS y exFAT {/* `#ext234-ntfs-and-exfat-support` */}

As per coding guidelines: "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}"

🤖 Prompt for 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.

In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`
at line 45, The heading "Soporte para Ext2/3/4, NTFS y exFAT" currently contains
a duplicated MDX anchor comment (`{/* `#ext234-ntfs-and-exfat-support` */}`
twice); remove the duplicate so only one anchor comment remains (use the
MDX-safe comment format once: `{/* `#ext234-ntfs-and-exfat-support` */}`) next to
that heading to keep the explicit stable anchor for Docusaurus.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md-11-11 (1)

11-11: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove duplicate anchor comments.

Multiple headings have duplicated anchor comments. Each heading should have only one anchor comment.

🔧 Suggested fixes

-### Bekannte Probleme {/* `#known-issues` */}
+### Bekannte Probleme {/* `#known-issues` */}

-### Rückschritte {/* `#rolling-back` */}
+### Rückschritte {/* `#rolling-back` */}

-#### ZFS RAIDZ-Erweiterung {/* `#raidz-expansion` */} {/* `#raidz-expansion` */}
+#### ZFS RAIDZ-Erweiterung {/* `#raidz-expansion` */}

-#### Ext2/3/4-, NTFS- und exFAT-Unterstützung {/* `#ext234-ntfs-and-exfat-support` */} {/* `#ext234-ntfs-and-exfat-support` */}
+#### Ext2/3/4-, NTFS- und exFAT-Unterstützung {/* `#ext234-ntfs-and-exfat-support` */}

As per coding guidelines, for explicit heading anchors in MDX (especially translated docs), prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}.

Also applies to: 22-22, 30-30, 46-46

🤖 Prompt for 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.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`
at line 11, The heading "### Bekannte Probleme" contains duplicate MDX anchor
comments; remove the extra comment so the heading has a single MDX-safe anchor
comment (e.g. `### Bekannte Probleme {/* `#known-issues` */}`) and apply the same
change to the other duplicated headings referenced in the review (remove
duplicate `{/* ... */}` comments and leave only one stable anchor per heading).
Ensure the remaining comment uses the Docusaurus MDX-safe form (`{/*
`#stable-anchor` */}`) and keep the anchor identifier meaningful and unique.

i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md-39-39 (1)

39-39: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove duplicate anchor comments.

Multiple headings have duplicated anchor comments. Each heading should have only one anchor comment.

🔧 Suggested fixes

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

-### mover を使って array ディスクを空にする {/* `#using-mover-to-empty-an-array-disk` */} {/* `#using-mover-to-empty-an-array-disk` */}
+### mover を使って array ディスクを空にする {/* `#using-mover-to-empty-an-array-disk` */}

-### overlay2 ストレージドライバーのサポートを追加 {/* `#add-support-for-overlay2-storage-driver` */}
+### overlay2 ストレージドライバーのサポートを追加 {/* `#add-support-for-overlay2-storage-driver` */}

-### Tailscale 統合 {/* `#tailscale-integration` */}
+### Tailscale 統合 {/* `#tailscale-integration` */}

As per coding guidelines, for explicit heading anchors in MDX (especially translated docs), prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}.

Also applies to: 92-92, 131-131, 269-269, 291-291

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md`
at line 39, The heading "### 既知の問題" contains duplicated anchor comments; remove
the duplicate so the heading has a single MDX-safe anchor comment (e.g., use one
instance of {/* `#known-issues` */}) and ensure all other affected headings (the
ones with duplicated anchors noted in the review) are fixed the same way,
leaving exactly one {/* `#stable-anchor` */}-style comment per heading.

i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md-22-22 (1)

22-22: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove duplicate anchor comment.

The heading has a duplicated anchor comment {/* #rolling-back*/} {/*#rolling-back */}. Only one anchor comment is needed.

🔧 Suggested fix

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`
at line 22, The heading "### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}"
contains a duplicated anchor comment; edit the heading in the file to remove one
of the duplicate anchor comments so it reads with a single anchor comment (e.g.,
"### ロールバック {/* `#rolling-back` */}"), leaving the rest of the line unchanged.

i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md-46-46 (1)

46-46: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove duplicate anchor comment.

The heading has a duplicated anchor comment. Only one is needed.

🔧 Suggested fix

-#### Ext2/3/4、NTFS、exFAT のサポート {/* `#ext234-ntfs-and-exfat-support` */} {/* `#ext234-ntfs-and-exfat-support` */}
+#### Ext2/3/4、NTFS、exFAT のサポート {/* `#ext234-ntfs-and-exfat-support` */}

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`
at line 46, The heading line "#### Ext2/3/4、NTFS、exFAT のサポート" contains two
identical anchor comments {/* `#ext234-ntfs-and-exfat-support` */}; remove the
duplicate so only a single anchor comment {/* `#ext234-ntfs-and-exfat-support` */}
remains immediately after the heading to eliminate redundancy.

i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md-11-11 (1)

11-11: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove duplicate anchor comment.

The heading has a duplicated anchor comment {/* #known-issues*/} {/*#known-issues */}. Only one anchor comment is needed per heading.

🔧 Suggested fix

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

As per coding guidelines, for explicit heading anchors in MDX (especially translated docs), prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}.

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`
at line 11, The heading "### 既知の問題" currently contains a duplicated MDX anchor
comment `{/* `#known-issues` */} {/* `#known-issues` */}`; remove the extra comment
so only a single MDX-safe anchor remains (e.g., `### 既知の問題 {/* `#known-issues`
*/}`) ensuring you keep the MDX-safe comment syntax and nothing else in the
heading line.

i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md-46-46 (1)

46-46: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove duplicate anchor comment.

The heading has a duplicated anchor comment. Only one is needed.

🔧 Suggested fix

-#### Prise en charge des systèmes de fichiers Ext2/3/4, NTFS et exFAT {/* `#ext234-ntfs-and-exfat-support` */} {/* `#ext234-ntfs-and-exfat-support` */}
+#### Prise en charge des systèmes de fichiers Ext2/3/4, NTFS et exFAT {/* `#ext234-ntfs-and-exfat-support` */}

As per coding guidelines, for explicit heading anchors in MDX (especially translated docs), prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}.

🤖 Prompt for 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.

In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`
at line 46, The heading "Prise en charge des systèmes de fichiers Ext2/3/4, NTFS
et exFAT" contains a duplicated anchor comment ({/*
`#ext234-ntfs-and-exfat-support` */} repeated twice); remove the duplicate so only
a single MDX-safe anchor comment remains (e.g., leave one {/*
`#ext234-ntfs-and-exfat-support` */}) directly after the heading to fix the
duplication and follow the MDX/Docusaurus guideline.

🤖 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
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md`:
- Line 40: The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains a duplicated MDX-safe anchor comment; remove the second `{/*
`#known-issues` */}` so the heading uses a single Docusaurus MDX-safe anchor
(i.e., leave `### 既知の問題 {/* `#known-issues` */}`), ensuring spacing is preserved
and no other anchors are duplicated elsewhere in the document.
- Line 3: The heading "## アップグレードに関する注意事項" contains a duplicated MDX anchor
comment `{/* `#upgrade-notes` */}`; remove the extra comment so only a single
anchor comment remains immediately after the heading (use the MDX-safe syntax
`{/* `#upgrade-notes` */}` once) to satisfy Docusaurus requirements and avoid
duplicate anchors.
- Line 64: The duplicate MDX heading anchor for "ロールバック" is present as `{/*
`#rolling-back` */} {/* `#rolling-back` */}`; remove the redundant second anchor so
the heading reads with a single MDX-safe anchor (e.g., `### ロールバック {/*
`#rolling-back` */}`) to comply with the explicit heading anchor convention.
- Line 42: The heading "i915 ドライバに関連するクラッシュ" contains a duplicated MDX anchor
comment (`{/* `#crashes-related-to-i915-driver` */}`); remove the extra duplicate
so only a single MDX-safe anchor comment remains directly after the heading
(e.g., `i915 ドライバに関連するクラッシュ {/* `#crashes-related-to-i915-driver` */}`), ensuring
you do not change the visible heading text or add non-MDX comment styles.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md`:
- Line 5: Remove duplicate MDX anchor comments on headings in this file—e.g.,
the "## アップグレードに関する注意事項" heading and the other affected headings (the ones noted
in the review). For each heading keep a single MDX-safe anchor comment in the
form `/*# anchor */` as used elsewhere in the PR (e.g., `## アップグレードに関する注意事項 {/*
`#upgrade-notes` */}`) and delete the second duplicate `/* ... */` comment so each
heading has only one anchor comment.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md`:
- Line 44: The heading "### ロールバック" contains a duplicated MDX-safe anchor
comment `{/* `#rolling-back` */} {/* `#rolling-back` */}`; remove the redundant
comment so only a single anchor comment `{/* `#rolling-back` */}` remains directly
after the heading, ensuring the MDX-safe syntax is kept for the translated doc
and no other changes to the heading text are made.
- Line 9: The heading "### 既知の問題" contains a duplicated MDX-safe anchor comment
`{/* `#known-issues` */} {/* `#known-issues` */}`; remove the extra comment so only
a single `{/* `#known-issues` */}` anchor remains immediately after the heading
(keep the existing MDX-safe comment style and ensure the anchor is still present
exactly once).
- Line 3: Remove the duplicated MDX-safe anchor comment on the heading "##
アップグレードに関する注意事項" by keeping a single `{/* `#upgrade-notes` */}` and deleting the
extra `{/* `#upgrade-notes` */}` so the heading contains exactly one anchor
comment (ensure you edit the line containing that heading text and the duplicate
anchor comments).

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md`:
- Line 3: The heading "## アップグレードに関する注意事項 {/* `#upgrade-notes` */} {/*
`#upgrade-notes` */}" contains a duplicated anchor comment; remove the extra
comment so the heading reads with a single anchor comment (e.g., keep only {/*
`#upgrade-notes` */}). Repeat the same fix for any other headings in this file
that have duplicated anchor comments (the same duplicate pattern with {/* #...
*/} appearing twice).

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md`:
- Line 42: The heading "### ロールバック" contains a duplicated MDX-safe anchor
comment `{/* `#rolling-back` */} {/* `#rolling-back` */}`; remove the extra comment
so only a single `{/* `#rolling-back` */}` remains directly after the heading text
(keep the MDX-safe syntax and a single anchor comment to satisfy Docusaurus
translation guidelines).
- Line 3: The heading "## アップグレードに関する注意事項" currently includes a duplicated
MDX-safe anchor comment `{/* `#upgrade-notes` */} {/* `#upgrade-notes` */}`; remove
the duplicate so only a single `{/* `#upgrade-notes` */}` remains directly after
the heading to follow the MDX-safe anchor convention and coding guidelines.
- Line 7: The heading "### 既知の問題" contains a duplicated MDX-safe anchor comment
`{/* `#known-issues` */} {/* `#known-issues` */}`; remove the duplicate so only a
single anchor comment remains (use `{/* `#known-issues` */}`), leaving the heading
as `### 既知の問題 {/* `#known-issues` */}`; ensure you only edit that heading (in
i18n/ja/.../6.12.12.md) and do not alter other anchor comments or add non-MDX
comment syntax.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md`:
- Line 3: The heading "## アップグレードに関する注意事項" contains a duplicated anchor comment
`{/* `#upgrade-notes` */}`; remove the extra anchor so the heading uses a single
MDX-safe anchor comment, e.g. keep only `/*`#upgrade-notes`*/` in the form `{/*
`#upgrade-notes` */}` after the heading text.
- Line 17: The heading "### ロールバック" contains a duplicated anchor comment `{/*
`#rolling-back` */}`; remove the extra one so the heading uses a single MDX-safe
anchor comment (i.e., `### ロールバック {/* `#rolling-back` */}`) and ensure no other
duplicate anchor tokens remain on that line.
- Line 9: The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains a duplicated MDX anchor comment; remove the extra comment so the
heading uses a single Docusaurus-safe anchor like "### 既知の問題 {/* `#known-issues`
*/}" and ensure no other duplicate anchor comments remain on that heading.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md`:
- Line 3: The heading "## アップグレードに関する注意事項 {/* `#upgrade-notes` */} {/*
`#upgrade-notes` */}" contains a duplicated anchor comment; edit the heading so it
contains only one anchor comment (use a single {/* `#upgrade-notes` */}) and do
the same for the other duplicated headings identified (the lines containing the
same heading text and anchor comments).

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md`:
- Line 9: The heading "### 既知の問題" contains a duplicated MDX-safe anchor comment
`{/* `#known-issues` */}`; remove the extra duplicate so the heading uses a single
MDX-safe anchor comment (i.e., leave one `{/* `#known-issues` */}` next to the
"### 既知の問題" heading) to comply with the MDX anchor guideline and avoid the
duplicate anchor token.
- Line 3: The duplicate MDX anchor comment `{/* `#upgrade-notes` */}` next to the
heading "## アップグレードに関する注意事項" should be reduced to a single MDX-safe anchor;
remove the extra `{/* `#upgrade-notes` */}` so the heading reads with only one
anchor comment (e.g., keep `## アップグレードに関する注意事項 {/* `#upgrade-notes` */}`) to
comply with the MDX/docusaurus guideline.
- Line 26: The heading "### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}"
contains a duplicated MDX anchor comment; remove the extra `{/* `#rolling-back`
*/}` so only a single MDX-safe anchor comment remains (keep the pattern `###
ロールバック {/* `#rolling-back` */}`) to comply with the heading anchor guideline and
avoid duplicate anchors.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md`:
- Line 5: The heading "## アップグレードに関する注意事項 {/* `#upgrade-notes` */} {/*
`#upgrade-notes` */}" (and the other duplicated-anchor headings referenced)
contains duplicate anchor comment blocks; remove the extra comment so each
heading has exactly one anchor comment (e.g., convert to "## アップグレードに関する注意事項 {/*
`#upgrade-notes` */}") following the project convention `### Heading {/*
`#stable-anchor` */}`; update the other affected headings (the ones with duplicate
`{/* ... */} {/* ... */}`) to the same single-comment form.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md`:
- Line 5: The heading "## アップグレードに関する注意事項" contains duplicated MDX anchor
comments (`{/* `#upgrade-notes` */} {/* `#upgrade-notes` */}`); remove the duplicate
so only a single anchor comment remains (e.g., `{/* `#upgrade-notes` */}`) and
ensure the same fix is applied to the other affected headings that have
duplicated anchors (the ones showing duplicate `{/* #... */} {/* #... */}`
tokens); keep the MDX-safe single-anchor format for all headings.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md`:
- Line 3: The heading contains a duplicated MDX anchor comment `{/*
`#upgrade-notes` */}`; remove the extra duplicate so only a single anchor comment
remains immediately after the heading text (i.e., change `## アップグレードに関する注意事項 {/*
`#upgrade-notes` */} {/* `#upgrade-notes` */}` to a single `## アップグレードに関する注意事項 {/*
`#upgrade-notes` */}`), ensuring the MDX-safe comment syntax is preserved.
- Line 15: The heading "### ロールバック" currently contains a duplicated MDX anchor
comment `{/* `#rolling-back` */}`; edit the heading so it only includes a single
MDX-safe anchor comment (e.g., `### ロールバック {/* `#rolling-back` */}`) by removing
the extra `{/* `#rolling-back` */}` token to leave one stable anchor.
- Line 7: The heading "### 既知の問題" currently contains a duplicated MDX-safe
anchor comment `{/* `#known-issues` */} {/* `#known-issues` */}`; remove the
duplicate so the heading uses a single Docusaurus MDX-safe comment `{/*
`#known-issues` */}`, e.g. update the line containing the "### 既知の問題" heading to
only one `{/* `#known-issues` */}` anchor.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md`:
- Line 37: The heading "### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}"
contains a duplicated MDX anchor comment; remove the extra `{/* `#rolling-back`
*/}` so the heading uses a single MDX-safe anchor comment (i.e., leave exactly
one `{/* `#rolling-back` */}` adjacent to the "### ロールバック" heading) to comply with
the MDX/Docusaurus guideline.
- Line 7: The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains a duplicated MDX-safe anchor; remove the extra `{/* `#known-issues` */}`
so the heading uses a single Docusaurus MDX-safe anchor (i.e., leave "### 既知の問題
{/* `#known-issues` */}"), ensuring the anchor token `#known-issues` remains
exactly as shown.
- Line 3: Remove the duplicated MDX anchor comment so the heading "##
アップグレードに関する注意事項" only has a single MDX-safe anchor `{/* `#upgrade-notes` */}`
immediately after it; delete the extra `{/* `#upgrade-notes` */}` token and ensure
the remaining anchor uses the MDX-safe comment syntax shown.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md`:
- Line 43: The heading "### ロールバック" contains a duplicated MDX anchor comment
`{/* `#rolling-back` */} {/* `#rolling-back` */}`; remove the extra duplicate so the
anchor appears only once (i.e., leave a single `{/* `#rolling-back` */}` after the
heading) and ensure the MDX-safe Docusaurus anchor syntax is used for this
heading.
- Line 3: The heading "## アップグレードに関する注意事項" contains a duplicated anchor comment;
remove the extra `{/* `#upgrade-notes` */}` so only a single MDX-safe anchor
remains (e.g., `## アップグレードに関する注意事項 {/* `#upgrade-notes` */}`), ensuring the anchor
comment appears once and uses the Docusaurus MDX-safe syntax referenced by `{/*
`#upgrade-notes` */}`.
- Line 8: The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains a duplicated MDX-safe anchor comment; remove the extra comment so the
heading reads with a single anchor comment (e.g., "### 既知の問題 {/* `#known-issues`
*/}") and ensure the remaining `{/* `#known-issues` */}` is placed immediately
after the heading text using Docusaurus MDX-safe syntax.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md`:
- Line 3: Remove the duplicated MDX heading anchor comment after the heading "##
アップグレードに関する注意事項" so only a single `{/* `#upgrade-notes` */}` remains; update the
heading to use the MDX-safe explicit anchor syntax once (e.g., keep one `{/*
`#upgrade-notes` */}` immediately after the heading text) and delete the extra
duplicate comment to satisfy the guideline about explicit heading anchors.
- Line 13: The heading "### ロールバック" contains a duplicated MDX-safe anchor
comment `{/* `#rolling-back` */}`; remove the extra duplicate so only one MDX-safe
anchor remains (e.g., ensure the line reads `### ロールバック {/* `#rolling-back` */}`
with a single `{/* `#rolling-back` */}`), leaving the heading text and anchor name
"rolling-back" intact.
- Line 9: The heading "### 既知の問題" currently has the duplicate MDX comment token
`{/* `#known-issues` */}` twice; remove the extra comment so only a single
MDX-safe anchor remains (i.e., keep one `{/* `#known-issues` */}` after the "###
既知の問題" heading). Locate the heading line containing "### 既知の問題" and the repeated
`{/* `#known-issues` */}` tokens and leave exactly one instance of `{/*
`#known-issues` */}` immediately following the heading.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md`:
- Line 7: The heading "### 既知の問題" contains duplicate MDX anchor comments; remove
the extra comment so the heading uses a single MDX-safe anchor comment. Locate
the heading line with `### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}`
and change it to a single occurrence like `### 既知の問題 {/* `#known-issues` */}`
ensuring only one `{/* `#anchor` */}` remains.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md`:
- Line 9: The heading "### 既知の問題" contains duplicate MDX anchor comments; remove
the extra `{/* `#known-issues` */}` so the heading uses a single MDX-safe anchor
comment (i.e., leave one `/* `#known-issues` */`) and do the same for the other
duplicate occurrence referenced (the second heading at the other location) so
each heading has only one anchor comment.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md`:
- Line 9: The heading "### 既知の問題" contains duplicate MDX anchor comments; remove
the extra comment so the heading uses a single MDX-safe anchor comment (e.g.,
keep "### 既知の問題 {/* `#known-issues` */}") and ensure no other duplicate `{/*
`#known-issues` */}` remains for that heading or its translated equivalent.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md`:
- Line 7: The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains a duplicated MDX anchor comment; remove the duplicate so the heading
uses a single Docusaurus MDX-safe anchor comment like "### 既知の問題 {/*
`#known-issues` */}". Locate the other occurrence noted ("Also applies to: 12-12")
and apply the same change there to ensure each heading (e.g., the "### 既知の問題"
headings) has only one anchor comment.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md`:
- Line 7: The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains duplicate MDX anchor comments; remove the extra comment so the heading
uses a single MDX-safe anchor comment (e.g., "### 既知の問題 {/* `#known-issues` */}")
and apply the same fix to the other duplicate heading instance with the same
pattern elsewhere in the file.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md`:
- Line 9: The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains duplicate MDX anchor comments; remove the extra comment so the heading
uses a single MDX-safe anchor comment (e.g., keep one "/* `#known-issues` */") to
match the guideline for explicit heading anchors and eliminate the duplicated
anchor.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md`:
- Line 11: The heading "### 既知の問題" contains duplicate MDX anchor comments;
remove the extra `{/* `#known-issues` */}` so the heading uses a single MDX-safe
anchor comment (e.g., `### 既知の問題 {/* `#known-issues` */}`) and do the same for the
other duplicate occurrence of the same anchor in this file to ensure only one
`{/* `#anchor` */}` per heading.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md`:
- Line 9: The heading "### 既知の問題" contains a duplicated MDX-safe anchor comment
`{/* `#known-issues` */}`; remove the extra comment so only a single `{/*
`#known-issues` */}` remains next to the "### 既知の問題" heading (keep Docusaurus
MDX-safe syntax), ensuring there is exactly one anchor comment for that heading.
- Line 13: The heading "### ロールバック" currently includes the anchor comment "{/*
`#rolling-back` */}" twice; remove the duplicate so only a single MDX-safe anchor
comment remains (leave one "{/* `#rolling-back` */}" next to the "### ロールバック"
heading and delete the extra instance) to comply with Docusaurus MDX anchor
guidelines.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md`:
- Line 11: The heading "### 既知の問題" contains duplicate MDX anchor comments `{/*
`#known-issues` */}`; remove the extra comment so the heading uses a single
MDX-safe anchor comment (e.g., `### 既知の問題 {/* `#known-issues` */}`) and do the
same for the other duplicated occurrence referenced (the second `{/*
`#known-issues` */}` around the other heading instance) to ensure only one anchor
comment remains per heading.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md`:
- Line 15: The heading "### 既知の問題" contains a duplicated MDX-safe anchor comment
`{/* `#known-issues` */} {/* `#known-issues` */}`; remove the duplicate so the
heading includes only a single anchor comment using the MDX-safe syntax (e.g.,
leave `/* `#known-issues` */` once) to comply with the translation/docs guidelines
and avoid duplicate anchors.
- Line 19: Remove the duplicated anchor comment after the heading "### ロールバック"
by keeping only one MDX-safe anchor comment `{/* `#rolling-back` */}`; locate the
heading line with `### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}` and
edit it to `### ロールバック {/* `#rolling-back` */}` so there is a single anchor
comment.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.6.md`:
- Line 9: The heading "既知の問題" contains duplicate MDX anchor comments; remove the
extra comment so the heading uses a single MDX-safe anchor comment, e.g. change
the duplicated `### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}` to a
single `### 既知の問題 {/* `#known-issues` */}`; ensure no other duplicate anchor
remains for that heading (also check the identical duplicate at lines referenced
in the review).

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Line 9: The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains a duplicate MDX anchor; remove the extra comment so the heading uses a
single MDX-safe anchor (e.g., change to "### 既知の問題 {/* `#known-issues` */}").
Apply the same change to the other duplicated occurrence mentioned (the one
referenced as 30-30) so each heading has exactly one {/* `#stable-anchor`
*/}-style comment.

---

Minor comments:
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`:
- Line 11: The heading "### Bekannte Probleme" contains duplicate MDX anchor
comments; remove the extra comment so the heading has a single MDX-safe anchor
comment (e.g. `### Bekannte Probleme {/* `#known-issues` */}`) and apply the same
change to the other duplicated headings referenced in the review (remove
duplicate `{/* ... */}` comments and leave only one stable anchor per heading).
Ensure the remaining comment uses the Docusaurus MDX-safe form (`{/*
`#stable-anchor` */}`) and keep the anchor identifier meaningful and unique.

In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`:
- Line 45: The heading "Soporte para Ext2/3/4, NTFS y exFAT" currently contains
a duplicated MDX anchor comment (`{/* `#ext234-ntfs-and-exfat-support` */}`
twice); remove the duplicate so only one anchor comment remains (use the
MDX-safe comment format once: `{/* `#ext234-ntfs-and-exfat-support` */}`) next to
that heading to keep the explicit stable anchor for Docusaurus.

In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`:
- Line 46: The heading "Prise en charge des systèmes de fichiers Ext2/3/4, NTFS
et exFAT" contains a duplicated anchor comment ({/*
`#ext234-ntfs-and-exfat-support` */} repeated twice); remove the duplicate so only
a single MDX-safe anchor comment remains (e.g., leave one {/*
`#ext234-ntfs-and-exfat-support` */}) directly after the heading to fix the
duplication and follow the MDX/Docusaurus guideline.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md`:
- Line 3: Remove duplicate anchor comments so each heading has only one MDX-safe
anchor comment; for the headings "アップグレードに関する注意事項" (anchor {/* `#upgrade-notes`
*/}), the heading with anchor {/* `#known-issues` */}, the heading with anchor {/*
`#rolling-back` */}, the heading with anchor {/* `#fix-for-macvlan-call-traces` */},
and the heading with anchor {/* `#system-drivers-page` */} keep a single instance
of the comment next to the heading (e.g., "### Heading {/* `#stable-anchor` */}")
and delete the extra duplicate {/* ... */} comments elsewhere in the same file.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md`:
- Line 3: Remove the duplicate MDX-style anchor comments so each heading has a
single anchor comment using the MDX-safe syntax; for the heading "##
アップグレードに関する注意事項" remove the extra `{/* `#upgrade-notes` */}` leaving one, and do
the same for the headings with `{/* `#known-issues` */}` and `{/* `#rolling-back`
*/}` so each appears only once immediately after its heading text.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md`:
- Line 39: The heading "### 既知の問題" contains duplicated anchor comments; remove
the duplicate so the heading has a single MDX-safe anchor comment (e.g., use one
instance of {/* `#known-issues` */}) and ensure all other affected headings (the
ones with duplicated anchors noted in the review) are fixed the same way,
leaving exactly one {/* `#stable-anchor` */}-style comment per heading.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`:
- Line 22: The heading "### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}"
contains a duplicated anchor comment; edit the heading in the file to remove one
of the duplicate anchor comments so it reads with a single anchor comment (e.g.,
"### ロールバック {/* `#rolling-back` */}"), leaving the rest of the line unchanged.
- Line 46: The heading line "#### Ext2/3/4、NTFS、exFAT のサポート" contains two
identical anchor comments {/* `#ext234-ntfs-and-exfat-support` */}; remove the
duplicate so only a single anchor comment {/* `#ext234-ntfs-and-exfat-support` */}
remains immediately after the heading to eliminate redundancy.
- Line 11: The heading "### 既知の問題" currently contains a duplicated MDX anchor
comment `{/* `#known-issues` */} {/* `#known-issues` */}`; remove the extra comment
so only a single MDX-safe anchor remains (e.g., `### 既知の問題 {/* `#known-issues`
*/}`) ensuring you keep the MDX-safe comment syntax and nothing else in the
heading line.

🪄 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: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: ea5257ce-1e24-4c17-b3ea-c129e5b7fe95

📥 Commits

Reviewing files that changed from the base of the PR and between 7bdb721 and 8f058a1.

📒 Files selected for processing (220)

• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.5.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.6.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.0.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.0.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.5.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.6.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.0.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.0.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.5.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.6.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.0.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.1.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.2.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.3.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.0.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.1.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.2.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.3.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.4.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.5.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.2.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.6.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.0.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.0.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.5.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.6.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.7.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx

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

• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.5.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.5.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.1.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.5.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.5.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.3.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.2.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.1.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.5.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.3.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.0.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.2.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.0.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.0.md
• i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.10.0.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate heading anchor comment.

The heading anchor comment {/* #upgrade-notes */} is duplicated. Docusaurus MDX syntax requires a single anchor comment per heading.

🔧 Proposed fix

-## アップグレードに関する注意事項 {/* `#upgrade-notes` */} {/* `#upgrade-notes` */}
+## アップグレードに関する注意事項 {/* `#upgrade-notes` */}

As per coding guidelines: "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	## アップグレードに関する注意事項 {/* #upgrade-notes */} {/* #upgrade-notes */}
	## アップグレードに関する注意事項 {/* `#upgrade-notes` */}

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 3-3: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 3-3: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md`
at line 3, The heading "## アップグレードに関する注意事項" contains a duplicated MDX anchor
comment `{/* `#upgrade-notes` */}`; remove the extra comment so only a single
anchor comment remains immediately after the heading (use the MDX-safe syntax
`{/* `#upgrade-notes` */}` once) to satisfy Docusaurus requirements and avoid
duplicate anchors.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate heading anchor comment.

The heading anchor comment {/* #known-issues */} is duplicated.

🔧 Proposed fix

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

As per coding guidelines: "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	### 既知の問題 {/* #known-issues */} {/* #known-issues */}
	### 既知の問題 {/* `#known-issues` */}

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 40-40: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 40-40: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md`
at line 40, The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains a duplicated MDX-safe anchor comment; remove the second `{/*
`#known-issues` */}` so the heading uses a single Docusaurus MDX-safe anchor
(i.e., leave `### 既知の問題 {/* `#known-issues` */}`), ensuring spacing is preserved
and no other anchors are duplicated elsewhere in the document.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate heading anchor comment.

The heading anchor comment {/* #crashes-related-to-i915-driver */} is duplicated.

🔧 Proposed fix

-#### i915 ドライバに関連するクラッシュ {/* `#crashes-related-to-i915-driver` */} {/* `#crashes-related-to-i915-driver` */}
+#### i915 ドライバに関連するクラッシュ {/* `#crashes-related-to-i915-driver` */}

As per coding guidelines: "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	#### i915 ドライバに関連するクラッシュ {/* #crashes-related-to-i915-driver */} {/* #crashes-related-to-i915-driver */}
	#### i915 ドライバに関連するクラッシュ {/* `#crashes-related-to-i915-driver` */}

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 42-42: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 42-42: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md`
at line 42, The heading "i915 ドライバに関連するクラッシュ" contains a duplicated MDX anchor
comment (`{/* `#crashes-related-to-i915-driver` */}`); remove the extra duplicate
so only a single MDX-safe anchor comment remains directly after the heading
(e.g., `i915 ドライバに関連するクラッシュ {/* `#crashes-related-to-i915-driver` */}`), ensuring
you do not change the visible heading text or add non-MDX comment styles.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate heading anchor comment.

The heading anchor comment {/* #rolling-back */} is duplicated.

🔧 Proposed fix

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines: "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	### ロールバック {/* #rolling-back */} {/* #rolling-back */}
	### ロールバック {/* `#rolling-back` */}

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 64-64: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 64-64: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md`
at line 64, The duplicate MDX heading anchor for "ロールバック" is present as `{/*
`#rolling-back` */} {/* `#rolling-back` */}`; remove the redundant second anchor so
the heading reads with a single MDX-safe anchor (e.g., `### ロールバック {/*
`#rolling-back` */}`) to comply with the explicit heading anchor convention.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate anchor comments.

Each heading has duplicate {/* #... */} anchor comments. Only one anchor comment per heading is needed, consistent with all other files in this PR.

🔧 Proposed fix

-## アップグレードに関する注意事項 {/* `#upgrade-notes` */} {/* `#upgrade-notes` */}
+## アップグレードに関する注意事項 {/* `#upgrade-notes` */}

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */} with a single anchor comment.

Also applies to: 7-7, 11-11

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 5-5: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 5-5: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md`
at line 5, Remove duplicate MDX anchor comments on headings in this file—e.g.,
the "## アップグレードに関する注意事項" heading and the other affected headings (the ones noted
in the review). For each heading keep a single MDX-safe anchor comment in the
form `/*# anchor */` as used elsewhere in the PR (e.g., `## アップグレードに関する注意事項 {/*
`#upgrade-notes` */}`) and delete the second duplicate `/* ... */` comment so each
heading has only one anchor comment.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Duplicate anchor comment detected.

The heading has the anchor comment {/* #known-issues */} specified twice. Each heading should have only one anchor comment.

🐛 Proposed fix

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

As per coding guidelines, use Docusaurus's MDX-safe comment syntax {/* #anchor */} (singular) for heading anchors in translated docs.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	### 既知の問題 {/* #known-issues */} {/* #known-issues */}
	### 既知の問題 {/* `#known-issues` */}

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 9-9: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 9-9: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md`
at line 9, The heading "### 既知の問題" contains a duplicated MDX-safe anchor comment
`{/* `#known-issues` */}`; remove the extra comment so only a single `{/*
`#known-issues` */}` remains next to the "### 既知の問題" heading (keep Docusaurus
MDX-safe syntax), ensuring there is exactly one anchor comment for that heading.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Duplicate anchor comment detected.

The heading has the anchor comment {/* #rolling-back */} specified twice. Each heading should have only one anchor comment.

🐛 Proposed fix

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines, use Docusaurus's MDX-safe comment syntax {/* #anchor */} (singular) for heading anchors in translated docs.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	### ロールバック {/* #rolling-back */} {/* #rolling-back */}
	### ロールバック {/* `#rolling-back` */}

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 13-13: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 13-13: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md`
at line 13, The heading "### ロールバック" currently includes the anchor comment "{/*
`#rolling-back` */}" twice; remove the duplicate so only a single MDX-safe anchor
comment remains (leave one "{/* `#rolling-back` */}" next to the "### ロールバック"
heading and delete the extra instance) to comply with Docusaurus MDX anchor
guidelines.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicated anchor comment.

The heading has a duplicated anchor comment {/* #known-issues*/} {/*#known-issues */}. Only one anchor comment should be present.

🐛 Proposed fix

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

As per coding guidelines, prefer Docusaurus's MDX-safe comment syntax {/* #stable-anchor */} for heading anchors in translated docs, but each heading should have only one anchor.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	### 既知の問題 {/* #known-issues */} {/* #known-issues */}
	### 既知の問題 {/* `#known-issues` */}

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 15-15: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 15-15: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md`
at line 15, The heading "### 既知の問題" contains a duplicated MDX-safe anchor
comment `{/* `#known-issues` */} {/* `#known-issues` */}`; remove the duplicate so
the heading includes only a single anchor comment using the MDX-safe syntax
(e.g., leave `/* `#known-issues` */` once) to comply with the translation/docs
guidelines and avoid duplicate anchors.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicated anchor comment.

The heading has a duplicated anchor comment {/* #rolling-back*/} {/*#rolling-back */}. Only one anchor comment should be present.

🐛 Proposed fix

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines, prefer Docusaurus's MDX-safe comment syntax {/* #stable-anchor */} for heading anchors in translated docs, but each heading should have only one anchor.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	### ロールバック {/* #rolling-back */} {/* #rolling-back */}
	### ロールバック {/* `#rolling-back` */}

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 19-19: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 19-19: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md`
at line 19, Remove the duplicated anchor comment after the heading "### ロールバック"
by keeping only one MDX-safe anchor comment `{/* `#rolling-back` */}`; locate the
heading line with `### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}` and
edit it to `### ロールバック {/* `#rolling-back` */}` so there is a single anchor
comment.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate anchor comments in heading syntax.

Both headings have duplicate {/* #anchor */} comments. Per coding guidelines, each heading should have only one anchor comment using the MDX-safe syntax.

🔧 Proposed fix

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */} (single occurrence).

Also applies to: 13-13

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 9-9: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 9-9: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.6.md`
at line 9, The heading "既知の問題" contains duplicate MDX anchor comments; remove
the extra comment so the heading uses a single MDX-safe anchor comment, e.g.
change the duplicated `### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}` to
a single `### 既知の問題 {/* `#known-issues` */}`; ensure no other duplicate anchor
remains for that heading (also check the identical duplicate at lines referenced
in the review).

[coderabbitai]

Review continued from previous batch...

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate anchor comments from headings.

Each heading has a duplicated MDX anchor comment (e.g., {/* #upgrade-notes*/} {/*#upgrade-notes */}). The correct Docusaurus syntax requires only a single anchor comment per heading. Duplicate anchors violate the MDX specification and may cause rendering issues.

🔧 Proposed fix

-## アップグレードに関する注意事項 {/* `#upgrade-notes` */} {/* `#upgrade-notes` */}
+## アップグレードに関する注意事項 {/* `#upgrade-notes` */}

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */} (not duplicated).

Also applies to: 7-7, 11-11

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 5-5: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 5-5: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md`
at line 5, The heading "## アップグレードに関する注意事項" contains duplicated MDX anchor
comments (`{/* `#upgrade-notes` */} {/* `#upgrade-notes` */}`); remove the duplicate
so only a single anchor comment remains (e.g., `{/* `#upgrade-notes` */}`) and
ensure the same fix is applied to the other affected headings that have
duplicated anchors (the ones showing duplicate `{/* #... */} {/* #... */}`
tokens); keep the MDX-safe single-anchor format for all headings.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate anchor comments in heading syntax.

Both headings have duplicate {/* #anchor */} comments. Per coding guidelines, each heading should have only one anchor comment using the MDX-safe syntax.

🔧 Proposed fix

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */} (single occurrence).

Also applies to: 17-17

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 7-7: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 7-7: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md`
at line 7, The heading "### 既知の問題" contains duplicate MDX anchor comments;
remove the extra comment so the heading uses a single MDX-safe anchor comment.
Locate the heading line with `### 既知の問題 {/* `#known-issues` */} {/* `#known-issues`
*/}` and change it to a single occurrence like `### 既知の問題 {/* `#known-issues` */}`
ensuring only one `{/* `#anchor` */}` remains.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate anchor comments in heading syntax.

Both headings have duplicate {/* #anchor */} comments. Per coding guidelines, each heading should have only one anchor comment using the MDX-safe syntax.

🔧 Proposed fix

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */} (single occurrence).

Also applies to: 15-15

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 9-9: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 9-9: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md`
at line 9, The heading "### 既知の問題" contains duplicate MDX anchor comments;
remove the extra `{/* `#known-issues` */}` so the heading uses a single MDX-safe
anchor comment (i.e., leave one `/* `#known-issues` */`) and do the same for the
other duplicate occurrence referenced (the second heading at the other location)
so each heading has only one anchor comment.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate anchor comments from headings.

Each heading has a duplicated MDX anchor comment (e.g., {/* #known-issues*/} {/*#known-issues */}). The correct Docusaurus syntax requires only a single anchor comment per heading. Duplicate anchors violate the MDX specification and may cause rendering issues.

🔧 Proposed fix

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */} (not duplicated).

Also applies to: 12-12

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 7-7: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 7-7: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md`
at line 7, The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains a duplicated MDX anchor comment; remove the duplicate so the heading
uses a single Docusaurus MDX-safe anchor comment like "### 既知の問題 {/*
`#known-issues` */}". Locate the other occurrence noted ("Also applies to: 12-12")
and apply the same change there to ensure each heading (e.g., the "### 既知の問題"
headings) has only one anchor comment.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate anchor comments in heading syntax.

Both headings have duplicate {/* #anchor */} comments. Per coding guidelines, each heading should have only one anchor comment using the MDX-safe syntax.

🔧 Proposed fix

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */} (single occurrence).

Also applies to: 11-11

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 7-7: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 7-7: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md`
at line 7, The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains duplicate MDX anchor comments; remove the extra comment so the heading
uses a single MDX-safe anchor comment (e.g., "### 既知の問題 {/* `#known-issues` */}")
and apply the same fix to the other duplicate heading instance with the same
pattern elsewhere in the file.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate anchor comments in heading syntax.

Both headings have duplicate {/* #anchor */} comments. Per coding guidelines, each heading should have only one anchor comment using the MDX-safe syntax.

🔧 Proposed fix

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */} (single occurrence).

Also applies to: 15-15

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 11-11: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 11-11: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md`
at line 11, The heading "### 既知の問題" contains duplicate MDX anchor comments `{/*
`#known-issues` */}`; remove the extra comment so the heading uses a single
MDX-safe anchor comment (e.g., `### 既知の問題 {/* `#known-issues` */}`) and do the
same for the other duplicated occurrence referenced (the second `{/*
`#known-issues` */}` around the other heading instance) to ensure only one anchor
comment remains per heading.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Remove duplicate heading anchors.

Both heading lines contain duplicated MDX comment anchors. Each heading should have only one anchor comment.

🔧 Proposed fix

-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}
+### 既知の問題 {/* `#known-issues` */}

-### ロールバック {/* `#rolling-back` */} {/* `#rolling-back` */}
+### ロールバック {/* `#rolling-back` */}

As per coding guidelines: "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}"

Also applies to: 30-30

🧰 Tools

🪛 markdownlint-cli2 (0.22.1)

[warning] 9-9: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

---

[warning] 9-9: Spaces inside emphasis markers

(MD037, no-space-in-emphasis)

🤖 Prompt for 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.

In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`
at line 9, The heading "### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */}"
contains a duplicate MDX anchor; remove the extra comment so the heading uses a
single MDX-safe anchor (e.g., change to "### 既知の問題 {/* `#known-issues` */}").
Apply the same change to the other duplicated occurrence mentioned (the one
referenced as 30-30) so each heading has exactly one {/* `#stable-anchor`
*/}-style comment.