Conversation
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
View logs |
unraid-docs | 931c114 | May 27 2026, 04:15 PM |
📝 WalkthroughWalkthroughThis PR contains systematic updates to internationalized Docusaurus documentation across German, Spanish, French, Japanese, and Chinese translations. Changes include removing explicit anchor comment markers from section headings to allow auto-generation, escaping bracket characters in MDX admonition directives to fix parser syntax, adding clarity instructions, reorganizing document structure, and adjusting cross-reference link anchors. ChangesDocusaurus Heading Anchor Normalization
MDX Admonition Bracket Escaping Fixes
Documentation Content Clarifications and Structure Updates
🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 21
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md (1)
269-269:⚠️ Potential issue | 🔴 Critical | ⚡ Quick winFix internal anchor links to match the explicit heading ID
- The heading at line 269 already sets the stable anchor
add-support-for-overlay2-storage-driver(### overlay2 ストレージドライバーのサポートを追加 {/*#add-support-for-overlay2-storage-driver*/}).- Update the links at lines 50 and 102 that currently point to
#overlay2-ストレージドライバーのサポートを追加so they target#add-support-for-overlay2-storage-driverinstead, otherwise the cross-links will break.🤖 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 269, Update the two internal links that currently target the autogenerated Japanese anchor "`#overlay2-ストレージドライバーのサポートを追加`" so they instead use the explicit heading ID "`#add-support-for-overlay2-storage-driver`" defined on the heading "overlay2 ストレージドライバーのサポートを追加 {/* `#add-support-for-overlay2-storage-driver` */}"; locate and replace the incorrect anchor in the two link instances so cross-links point to "`#add-support-for-overlay2-storage-driver`".
🟠 Major comments (19)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-126-128 (1)
126-128:⚠️ Potential issue | 🟠 Major | ⚡ Quick winKeep localized FAQ answers in Spanish.
Lines 126-128 are fully in English, which is a regression for this Spanish page and hurts readability/consistency for Spanish users.
🤖 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/troubleshooting/faq.mdx` around lines 126 - 128, The paragraph currently in English (the two sentences referencing %%GUID|guid%% and the links to Create your bootable media and Selecting a replacement device) must be translated into Spanish while preserving all placeholders (%%GUID|guid%%), link targets, markdown structure, punctuation, and examples (TeamGroup, Transcend, PNY), and keeping the two link references unchanged; update the text so the meaning and warnings match the original English but read fluently in Spanish, and ensure the following sentence about preferring reputable retailers and avoiding generic/unbranded drives, SSDs, USB card readers, and SD card adapters is also translated into Spanish without altering the placeholders or link paths.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-62-62 (1)
62-62:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRevert mixed-language replacements in the Japanese FAQ.
These lines are now English inside a Japanese page, which is a localization regression and degrades UX consistency.
Also applies to: 126-128, 243-243
🤖 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/troubleshooting/faq.mdx` at line 62, The paragraph contains English text and mixed-language placeholder usage (e.g., "If your HASP key is a USB dongle", "%%VM|vm%%") inside a Japanese FAQ; revert these lines back to their proper Japanese translations and ensure localization placeholders are rendered in Japanese (use the localized term for VM instead of leaving "vm" or English phrases), and apply the same correction to the other occurrences with the same English fragments so the page is fully Japanese and consistent.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-126-128 (1)
126-128:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAvoid replacing French FAQ content with English text.
Lines 126-128 are in English, which introduces a clear localization regression in this French document.
🤖 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/troubleshooting/faq.mdx` around lines 126 - 128, The French FAQ contains English paragraphs about boot device GUIDs (the lines starting with "Unraid requires a boot device with a unique hardware %%GUID|guid%%" and the following sentence about brands and guidance links); replace these English sentences with an accurate French translation that preserves the placeholders (%%GUID|guid%%) and existing relative links to "Create your bootable media" and "Selecting a replacement device", and keep the recommended guidance about reputable retailers, second-tier brands (TeamGroup, Transcend, PNY) and avoiding generic/unbranded drives, SSDs, USB card readers and SD adapters; ensure punctuation and markdown links remain intact and that the French text reads naturally in the document's style.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-106-106 (1)
106-106:⚠️ Potential issue | 🟠 Major | ⚡ Quick winClose the danger admonition and remove the duplicated instruction line.
Line 106 repeats the same sentence and the
:::dangerblock opened at Line 92 is not closed in the shown final content. This can break rendering for the rest of the page.Suggested fix
:::danger[Critical: Operación Destructiva] @@ ```bash wipefs /dev/sdX
-Para cada unidad de datos, ejecuta:
+:::</details> <details> <summary>🤖 Prompt for AI Agents</summary>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/troubleshooting/faq.mdx
at line 106, Close the open danger admonition (the:::dangerblock opened
earlier) by inserting the closing:::before the duplicated sentence and
remove the repeated line "Para cada unidad de datos, ejecuta:" so the page
doesn't break; locate the admonition started around the:::dangerblock
(opened near the section containing thewipefs /dev/sdXcode fence) and add
the closing:::immediately after that block, deleting the extra duplicate
sentence that appears after it.</details> </blockquote></details> <details> <summary>i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-106-106 (1)</summary><blockquote> `106-106`: _⚠️ Potential issue_ | _🟠 Major_ | _⚡ Quick win_ **Close the `danger` admonition and drop the duplicate line.** The `:::danger` opened at Line 92 is not closed in the provided final content, and Line 106 duplicates the same instruction. This can break page structure/rendering. <details> <summary>Suggested fix</summary> ```diff :::danger[Critical: 破壊的操作] @@ ```bash wipefs /dev/sdX
-各データドライブについて、次を実行します:
+:::</details> <details> <summary>🤖 Prompt for AI Agents</summary>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/troubleshooting/faq.mdx
at line 106, Close the open danger admonition (the ':::danger' block started
earlier) by adding the closing marker ':::' immediately after the code block
containing "wipefs /dev/sdX", and remove the duplicate Japanese line
"各データドライブについて、次を実行します:" that appears after the code block so the admonition is
properly closed and the duplicate instruction is dropped.</details> </blockquote></details> <details> <summary>i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-106-106 (1)</summary><blockquote> `106-106`: _⚠️ Potential issue_ | _🟠 Major_ | _⚡ Quick win_ **Fix the malformed `danger` block around the wipe command.** Line 106 is duplicated, and the `:::danger` block opened at Line 92 is not closed in this final content. That can cause incorrect rendering scope for subsequent sections. <details> <summary>Suggested fix</summary> ```diff :::danger[Critical: Opération destructive] @@ ```bash wipefs /dev/sdX
-Pour chaque disque de données, exécutez :
+:::</details> <details> <summary>🤖 Prompt for AI Agents</summary>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/troubleshooting/faq.mdx
at line 106, The:::dangeradmonition opened earlier isn't closed and the line
"Pour chaque disque de données, exécutez :" is duplicated; close the danger
block immediately after the wipe command and remove the duplicated line so the
admonition ends with the closing token:::right after the fenced code block
(refer to the:::dangerstart and thewipefs /dev/sdXcode block to locate
where to insert the:::).</details> </blockquote></details> <details> <summary>i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx-218-218 (1)</summary><blockquote> `218-218`: _⚠️ Potential issue_ | _🟠 Major_ | _⚡ Quick win_ **Fix escaped admonition titles so Docusaurus can parse them** In `cache-pools.mdx`, multiple admonitions use escaped title brackets (e.g., `:::note\[Timing]`); update them to unescaped form (`:::note[Timing]`), including at lines 218 (`note[Timing]`), 247 (`note[Prerequisites]`), 265 (`important[Timing]`), 277 (`tip[Example]`), and 384 (`note[Remember]`). <details> <summary>🤖 Prompt for AI Agents</summary>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/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
at line 218, Replace the escaped admonition title brackets so Docusaurus can
parse them: find occurrences of the admonition markers written with escaped
brackets (e.g., ":::note\[Timing]", ":::note\[Prerequisites]",
":::important\[Timing]", ":::tip\[Example]", ":::note\[Remember]") and change
each to the unescaped form (":::note[Timing]", ":::note[Prerequisites]",
":::important[Timing]", ":::tip[Example]", ":::note[Remember]") preserving the
rest of the line and spacing.</details> </blockquote></details> <details> <summary>i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx-214-214 (1)</summary><blockquote> `214-214`: _⚠️ Potential issue_ | _🟠 Major_ | _⚡ Quick win_ **Fix escaped admonition titles in MDX** - In `i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx`, remove the backslash before `[` in the admonition titles: `::::important\[Prerequisites]` → `::::important[Prerequisites]` (line 214) and `::::warning\[Warnings]` → `::::warning[Warnings]` (line 222). <details> <summary>🤖 Prompt for AI Agents</summary>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/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx
at line 214, Remove the stray backslashes escaping the admonition titles so the
MDX admonitions render correctly: find the lines containing the escaped markers
":::important[Prerequisites]" and ":::warning[Warnings]" and change them to
":::important[Prerequisites]" and ":::warning[Warnings]" respectively (i.e.,
delete the backslash before the opening bracket in those admonition markers).</details> </blockquote></details> <details> <summary>i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx-217-217 (1)</summary><blockquote> `217-217`: _⚠️ Potential issue_ | _🟠 Major_ | _⚡ Quick win_ **Remove escaped `\[` from Docusaurus admonition titles in `cache-pools.mdx`.** Replace `:::note\[Timing]` with `:::note[Timing]` (unescape the `[` in the title). Same issue at lines 246, 264, 276, and 383 (e.g., `:::note\[Prerequisites]`, `:::important\[Timing]`, `:::tip\[Example]`, `:::note\[Remember]`). <details> <summary>🤖 Prompt for AI Agents</summary>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/using-unraid-to/manage-storage/cache-pools.mdx
at line 217, Replace the escaped bracket sequences in the Docusaurus
admonitions: find occurrences of ":::note[Timing]", ":::note[Prerequisites]",
":::important[Timing]", ":::tip[Example]", and ":::note[Remember]" and change
them to their unescaped forms ":::note[Timing]", ":::note[Prerequisites]",
":::important[Timing]", ":::tip[Example]", and ":::note[Remember]" respectively
so the admonition titles render correctly.</details> </blockquote></details> <details> <summary>i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx-214-214 (1)</summary><blockquote> `214-214`: _⚠️ Potential issue_ | _🟠 Major_ | _⚡ Quick win_ **Fix escaped admonition title brackets in MDX** - In `i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx`, change: - line 214 from `::::important\[Prerequisites]` to `::::important[Prerequisites]` - line 222 from `::::warning\[Warnings]` to `::::warning[Warnings]` <details> <summary>🤖 Prompt for AI Agents</summary>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/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx
at line 214, The MDX contains escaped brackets in admonition markers; locate the
admonition lines containing the literal strings "::::important[Prerequisites]"
and "::::warning[Warnings]" in the file and remove the backslash escape so they
read "::::important[Prerequisites]" and "::::warning[Warnings]" respectively,
preserving the rest of the MDX content and punctuation.</details> </blockquote></details> <details> <summary>i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx-218-218 (1)</summary><blockquote> `218-218`: _⚠️ Potential issue_ | _🟠 Major_ | _⚡ Quick win_ **Fix Docusaurus admonition titles: remove escaped `\[` in bracketed titles** Docusaurus expects the title delimiter to be a literal `[` right after `:::` (e.g., `:::note[Title]`). Escaping it as `\[` prevents the parser from treating it as the admonition title. <details> <summary>Suggested fix</summary> ```diff -:::note\[Timing] +:::note[Timing] ... -:::note\[Prerequisites] +:::note[Prerequisites] ... -:::important\[Timing] +:::important[Timing] ... -:::tip\[Example] +:::tip[Example] ... -:::note\[Remember] +:::note[Remember]Applies to lines 218, 247, 265, 277, and 384.
🤖 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/using-unraid-to/manage-storage/cache-pools.mdx` at line 218, The admonition titles are escaped (e.g., ":::note\[Timing]") so Docusaurus won't parse the title; find instances of the escaped pattern ":::note\[" (and any other admonition types using "\[") and remove the backslash so they read ":::note[Timing]" (or ":::note[...]" / ":::tip[...]" as appropriate) ensuring the bracket is a literal "[" immediately after the ":::type" token.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx-214-214 (1)
214-214:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix escaped admonition title brackets in translated MDX
Ini18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx(lines 214 and 222), remove the backslashes so Docusaurus can parse the titles:
:::important\[Prerequisites]→:::important[Prerequisites]:::warning\[Warnings]→:::warning[Warnings]🤖 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/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx` at line 214, Fix the escaped admonition titles by removing the backslashes so Docusaurus can parse them: replace the occurrences of :::important\[Prerequisites] and :::warning\[Warnings] with :::important[Prerequisites] and :::warning[Warnings] respectively (look for the exact tokens :::important\[Prerequisites] and :::warning\[Warnings] in the file and update them).i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx-218-218 (1)
218-218:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdmonition directive titles: remove escaped
\[charactersThe file uses
:::note\[Timing]/:::note\[Prerequisites]/:::important\[Timing]/:::tip\[Example]/:::note\[Remember]; switch to standard syntax:::note[Timing]/:::note[Prerequisites]/:::important[Timing]/:::tip[Example]/:::note[Remember]so Docusaurus/remark-directive parses the title.
- 218:
:::note[Timing]- 247:
:::note[Prerequisites]- 265:
:::important[Timing]- 277:
:::tip[Example]- 384:
:::note[Remember]🤖 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/using-unraid-to/manage-storage/cache-pools.mdx` at line 218, The admonition directives use escaped brackets (e.g., ":::note\[Timing]", ":::note\[Prerequisites]", ":::important\[Timing]", ":::tip\[Example]", ":::note\[Remember]") which prevents remark-directive parsing; edit those directive lines to remove the backslash before the opening bracket so they read ":::note[Timing]", ":::note[Prerequisites]", ":::important[Timing]", ":::tip[Example]", and ":::note[Remember]" respectively, leaving the rest of the line content unchanged and preserving existing capitalization and spacing.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx-68-68 (1)
68-68:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix Docusaurus caution admonition title parsing (remove escaped
[).
Ini18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx(line 68), change:::caution\[Critical]to:::caution[Critical]; escaping the title delimiter can prevent the admonition title from being parsed/rendered correctly.🤖 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/using-unraid-to/manage-storage/shares.mdx` at line 68, The admonition title is escaped and won't parse: replace the literal token ":::caution\\[Critical]" with the correct admonition syntax ":::caution[Critical]" so the Docusaurus admonition title is recognized and rendered; update that occurrence in the shares.mdx content where the string ":::caution\\[Critical]" appears.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx-214-214 (1)
214-214:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix Docusaurus admonition title syntax (
\[escapes)Lines 214 and 222 use escaped brackets (
:::important\[Prerequisites],:::warning\[Warnings]), but Docusaurus admonition titles use the standard unescaped form (:::type[Title]). Escaping[can break or degrade parsing/rendering.Suggested fix
-:::important\[Prerequisites] +:::important[Prerequisites] ... -:::warning\[Warnings] +:::warning[Warnings]🤖 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/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx` at line 214, The admonition titles use escaped brackets which break Docusaurus parsing; locate the admonitions using the strings ":::important\[Prerequisites]" and ":::warning\[Warnings]" and remove the backslash so they read ":::important[Prerequisites]" and ":::warning[Warnings]" respectively, ensuring standard Docusaurus admonition syntax is restored.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md-13-13 (1)
13-13:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix broken internal link anchors.
In
i18n/fr/.../release-notes/7.0.0.md, theTailscalesection heading is anchored as#tailscale-integration(### Intégration Tailscale {/*#tailscale-integration*/}on line 301), but the internal links on lines 13, 112, and 287 all point to#integration-tailscale, causing broken links.Update those link targets to
#tailscale-integration(instead of changing the heading 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.0.0.md` at line 13, Replace the incorrect internal link target "`#integration-tailscale`" with the correct anchor "`#tailscale-integration`" wherever it appears in this markdown (the links that currently point to the Tailscale section); ensure all instances of the link text `#integration-tailscale` are updated to `#tailscale-integration` so they match the heading anchor `### Intégration Tailscale {/* `#tailscale-integration` */}`.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md-39-39 (1)
39-39:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRemove duplicate anchor comment.
The heading contains two identical anchor comments
{/*#known-issues*/} {/*#known-issues*/}. Only one anchor comment is needed per heading.🔧 Proposed fix
-### 既知の問題 {/* `#known-issues` */} {/* `#known-issues` */} +### 既知の問題 {/* `#known-issues` */}🤖 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 two identical anchor comments `{/* `#known-issues` */} {/* `#known-issues` */}`; remove the duplicate so only a single `{/* `#known-issues` */}` remains immediately after the heading to avoid redundant anchors.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md-131-131 (1)
131-131:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRemove duplicate anchor comment.
The heading contains two identical anchor comments
{/*#using-mover-to-empty-an-array-disk*/} {/*#using-mover-to-empty-an-array-disk*/}. Only one anchor comment is needed per heading.🔧 Proposed fix
-### 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` */}🤖 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 131, The heading "### mover を使って array ディスクを空にする" contains a duplicated anchor comment `{/* `#using-mover-to-empty-an-array-disk` */}`; remove the extra occurrence so the heading only includes a single `{/* `#using-mover-to-empty-an-array-disk` */}` anchor comment (leave one intact and delete the duplicate).i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md-92-92 (1)
92-92:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRemove duplicate anchor comment.
The heading contains two identical anchor comments
{/*#rolling-back*/} {/*#rolling-back*/}. Only one anchor comment is needed per heading.🔧 Proposed 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.0.0.md` at line 92, The heading "### ロールバック" contains a duplicate anchor comment `{/* `#rolling-back` */} {/* `#rolling-back` */}`; remove the redundant comment so the heading only includes a single `{/* `#rolling-back` */}` anchor (locate the heading line with "### ロールバック" and delete one of the duplicate `{/* `#rolling-back` */}` tokens).
🟡 Minor comments (12)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx-78-78 (1)
78-78:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove duplicated Windows subsection heading.
Line 78 repeats the same heading already present on Line 76, so this renders duplicate content in the same section.
🤖 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/getting-started/set-up-unraid/create-your-bootable-media.mdx` at line 78, Remove the duplicated subsection heading "**Windows 7 oder höher:**" that appears a second time in the same section—keep the first occurrence and delete the redundant one (ensure surrounding spacing/newlines are cleaned up so the section renders correctly).i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx-77-77 (1)
77-77:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove duplicated Windows subsection heading.
Line 77 duplicates the heading already present on Line 75, so the section currently repeats the same label twice.
🤖 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/getting-started/set-up-unraid/create-your-bootable-media.mdx` at line 77, Remove the duplicated subsection heading "**Windows 7 以降:**" so the Windows heading appears only once; locate the repeated heading text in the create-your-bootable-media.mdx content and delete the second occurrence (the duplicate) to avoid repeating the same label.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx-160-160 (1)
160-160:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove duplicated/misplaced content introduced in this hunk.
Line 160 duplicates the
vfio-pciparagraph already present at Line 162 and is out of place inside the snapshot explainer; Line 248 and Line 436 also duplicate nearby content.Proposed edit
-在您可以将 GPU 或任何 PCI 设备分配给 %%虚拟机|vm%% 之前，重要的是要将该设备 "绑定" 到 **vfio-pci** 驱动程序。这个过程将设备从 Unraid 中隐藏，并完全供您的 %%VM|vm%% 使用。 @@ -以下是一些需要考虑的要点： @@ -注入ROM：Also applies to: 248-248, 436-436
🤖 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/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx` at line 160, Remove the duplicated/misplaced vfio-pci paragraph text ("在您可以将 GPU 或任何 PCI 设备分配给 %%虚拟机|vm%% 之前，重要的是要将该设备 "绑定" 到 **vfio-pci** 驱动程序。这个过程将设备从 Unraid 中隐藏，并完全供您的 %%VM|vm%% 使用。") from the snapshot explainer and the other occurrences; keep a single canonical vfio-pci paragraph located with the PCI/GPU passthrough instructions and delete the duplicates at the three locations referenced (the paragraph inside the snapshot section and the other two duplicate instances).i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx-35-41 (1)
35-41:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFix mixed-language title and remove duplicated instruction.
Line 35 uses a mixed-language title, and Line 41 repeats the same sentence already present in the callout. Please keep the title fully Spanish and remove the duplicate paragraph.
Proposed edit
-:::important[Before de cifrar] +:::important[Antes de cifrar] @@ -Mueva todos los datos del disco que desea cifrar a otra ubicación (otro disco en su %%array|array%%, un %%cache pool|cache-pool%%, o una copia de seguridad externa). Para obtener más detalles sobre cómo mover sus datos de manera segura, consulte [Convertir a un nuevo tipo de sistema de archivos](../../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type). - 1. Vaya a la pestaña **Principal** en el %%WebGUI|web-gui%%.🤖 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/system-administration/secure-your-server/securing-your-data.mdx` around lines 35 - 41, Change the mixed-language callout title ":::important[Before de cifrar]" to fully Spanish ":::important[Antes de cifrar]" and remove the duplicated paragraph that repeats the same instruction after the callout (the second occurrence of "Mueva todos los datos del disco..."). Keep the callout body as the single source of that instruction and ensure only one instance of that sentence remains in the document.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx-69-73 (1)
69-73:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove excessive repetition of placeholder instruction.
The instruction to replace
Xwith the disk number is repeated 5 consecutive times (lines 69-73). This is confusing and unprofessional. A single instruction is sufficient for clarity.📝 Proposed fix to remove duplicate lines
- Unraid 6.12 以降: `dd bs=1M if=/dev/zero of=/dev/mdXp1 status=progress` - Unraid 6.11 以前: `dd bs=1M if=/dev/zero of=/dev/mdX status=progress` - `X` は、削除するデータディスクの番号に置き換えてください。 - `X` は、削除するデータディスクの番号に置き換えてください。 - `X` は、削除するデータディスクの番号に置き換えてください。 - `X` は、削除するデータディスクの番号に置き換えてください。 `X` は、削除するデータディスクの番号に置き換えてください。 7. 消去が完了したらアレイを停止します。🤖 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/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx` around lines 69 - 73, The Japanese placeholder instruction string "X は、削除するデータディスクの番号に置き換えてください。" is repeated five times in the block; remove the duplicate lines so only one instance of that instruction remains (keep a single, correctly placed occurrence) to eliminate redundancy and improve clarity in the document.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx-69-73 (1)
69-73:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove excessive repetition of placeholder instruction.
The instruction to replace
Xwith the disk number is repeated 5 consecutive times (lines 69-73). This is confusing and unprofessional. A single instruction is sufficient for clarity.📝 Proposed fix to remove duplicate lines
- Para Unraid 6.12 o posterior: `dd bs=1M if=/dev/zero of=/dev/mdXp1 status=progress` - Para Unraid 6.11 y versiones anteriores: `dd bs=1M if=/dev/zero of=/dev/mdX status=progress` - Reemplace `X` con el número específico del disco de datos que está eliminando. - Reemplace `X` con el número específico del disco de datos que está eliminando. - Reemplace `X` con el número específico del disco de datos que está eliminando. - Reemplace `X` con el número específico del disco de datos que está eliminando. Reemplace `X` con el número específico del disco de datos que está eliminando. 7. Detenga el array una vez que el borrado esté completo.🤖 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/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx` around lines 69 - 73, Remove the duplicate placeholder line "Reemplace `X` con el número específico del disco de datos que está eliminando." so only a single instance remains (replace the five repeated occurrences shown in the diff with one clear line); keep the remaining sentence exactly as written and ensure surrounding paragraph/spacing remains correct in the document (file contains this repeated string to locate the occurrences).i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx-69-73 (1)
69-73:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove excessive repetition of placeholder instruction.
The instruction to replace
Xwith the disk number is repeated 5 consecutive times (lines 69-73). This is confusing and unprofessional. A single instruction is sufficient for clarity. As per coding guidelines, this affects user-facing text quality.📝 Proposed fix to remove duplicate line
- Für Unraid 6.12 oder später: `dd bs=1M if=/dev/zero of=/dev/mdXp1 status=progress` - Für Unraid 6.11 und früher: `dd bs=1M if=/dev/zero of=/dev/mdX status=progress` - Ersetzen Sie `X` durch die spezifische Nummer der Datenfestplatte, die Sie entfernen möchten. - Ersetzen Sie `X` durch die spezifische Nummer der Datenfestplatte, die Sie entfernen möchten. - Ersetzen Sie `X` durch die spezifische Nummer der Datenfestplatte, die Sie entfernen möchten. - Ersetzen Sie `X` durch die spezifische Nummer der Datenfestplatte, die Sie entfernen möchten. Ersetzen Sie `X` durch die spezifische Nummer der Datenfestplatte, die Sie entfernen möchten. 7. Stoppen Sie das Array, sobald das Nullsetzen abgeschlossen ist.🤖 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/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx` around lines 69 - 73, The content contains five identical lines instructing the reader to "Ersetzen Sie `X`..." — remove the four duplicate lines and keep a single clear instance of the placeholder instruction so the document only states the replacement once; update the section surrounding the instruction in the file where the repeated sentence occurs (the repeated "Ersetzen Sie `X` durch die spezifische Nummer der Datenfestplatte, die Sie entfernen möchten.") to a single line with appropriate spacing.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx-69-73 (1)
69-73:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove excessive repetition of placeholder instruction.
The instruction to replace
Xwith the disk number is repeated 5 consecutive times (lines 69-73). This is confusing and unprofessional. A single instruction is sufficient for clarity. As per coding guidelines, this affects user-facing text quality.📝 Proposed fix to remove duplicate lines
- Pour Unraid 6.12 ou version ultérieure : `dd bs=1M if=/dev/zero of=/dev/mdXp1 status=progress` - Pour Unraid 6.11 et antérieur : `dd bs=1M if=/dev/zero of=/dev/mdX status=progress` - Remplacez `X` par le numéro spécifique du disque de données que vous supprimez. - Remplacez `X` par le numéro spécifique du disque de données que vous supprimez. - Remplacez `X` par le numéro spécifique du disque de données que vous supprimez. - Remplacez `X` par le numéro spécifique du disque de données que vous supprimez. Remplacez `X` par le numéro spécifique du disque de données que vous supprimez. 7. Arrêtez le tableau une fois le nettoyage terminé.🤖 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/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx` around lines 69 - 73, The content contains five consecutive duplicate lines of the placeholder instruction "Remplacez `X` par le numéro spécifique du disque de données que vous supprimez."; edit the MDX so only a single instance of that sentence remains (remove the four extra duplicates), keeping the exact placeholder `X` notation and surrounding punctuation intact to preserve clarity for the user.i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx-124-124 (1)
124-124:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winKeep a stable anchor for the existing
#complete-workflow-examplelink.Line 17 points to
#complete-workflow-example, but this translated heading now uses an auto slug, so the hash link no longer resolves.Suggested fix
-## Ejemplo completo de flujo de trabajo +## Ejemplo completo de flujo de trabajo {/* `#complete-workflow-example` */}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/API/programmatic-api-key-management.mdx` at line 124, The translated heading "## Ejemplo completo de flujo de trabajo" no longer matches the explicit link "`#complete-workflow-example`"; update the heading to include a stable MDX-safe anchor so the existing `#complete-workflow-example` link resolves (add Docusaurus MDX comment-style anchor immediately after that heading text), ensuring the anchor name is exactly "complete-workflow-example" to match the existing link target.i18n/de/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx-124-124 (1)
124-124:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRestore the stable anchor used by existing in-page links.
Line 17 and Line 19 still link to
#complete-workflow-example, but this localized heading now auto-generates a different slug, so the jump target breaks.Suggested fix
-## Komplettes Workflow-Beispiel +## Komplettes Workflow-Beispiel {/* `#complete-workflow-example` */}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/de/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx` at line 124, Restore the stable in-page anchor by modifying the heading "## Komplettes Workflow-Beispiel" to include the Docusaurus MDX-safe comment anchor for "`#complete-workflow-example`" (i.e., add the MDX comment-style anchor next to that heading) so existing links to "`#complete-workflow-example`" continue to work; ensure the localized heading retains its text and only the MDX comment anchor is added.i18n/ja/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx-124-124 (1)
124-124:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winPreserve the stable
#complete-workflow-exampleanchor used above.Line 17 links to
#complete-workflow-example, but this localized heading now gets a different auto-generated slug, so the anchor link breaks.Suggested fix
-## 完全なワークフローの例 +## 完全なワークフローの例 {/* `#complete-workflow-example` */}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/API/programmatic-api-key-management.mdx` at line 124, The localized heading "## 完全なワークフローの例" generates a different slug and breaks existing links to "`#complete-workflow-example`"; update that heading to include an explicit MDX-safe stable anchor using Docusaurus comment syntax so the existing link keeps working (i.e., add the stable anchor comment tied to the known slug "`#complete-workflow-example`" right after the heading text); locate the heading string "## 完全なワークフローの例" in programmatic-api-key-management.mdx and append the MDX-safe anchor comment for "`#complete-workflow-example`".i18n/fr/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx-124-124 (1)
124-124:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRe-add the stable anchor expected by the existing hash links.
Line 17 and Line 19 still reference
#complete-workflow-example; without an explicit anchor on this translated heading, that target breaks.Suggested fix
-## Exemple de workflow complet +## Exemple de workflow complet {/* `#complete-workflow-example` */}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/API/programmatic-api-key-management.mdx` at line 124, The translated heading "## Exemple de workflow complet" lacks the explicit stable anchor referenced by other links (`#complete-workflow-example`); update that heading to include Docusaurus's MDX-safe comment anchor so the existing links resolve (e.g., add the stable anchor comment to the "Exemple de workflow complet" heading using the MDX-safe syntax shown in the guidelines).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: bc06bdfe-8b7f-49f8-9c01-3d65d3be863b
📒 Files selected for processing (51)
i18n/de/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/de/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdxi18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/fr/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/fr/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
| ### Unterstützung für overlay2 Speicher-Treiber hinzufügen | ||
|
|
||
| Verwenden Sie auf einem ZFS-Volume **Docker data-root=directory**, empfehlen wir, zu ***Einstellungen → Docker*** zu navigieren und den **Docker-Speicher-Treiber** auf **overlay2** umzuschalten, dann den Verzeichnisinhalt zu löschen und Docker die Image-Ebenen neu herunterladen zu lassen. | ||
| Die veraltete **native** Einstellung verursacht erhebliche Stabilitätsprobleme auf ZFS-Volumes. | ||
|
|
||
| Wenn die Beibehaltung der Möglichkeit zum Downgrade auf frühere Versionen wichtig ist, dann wechseln Sie stattdessen zu **Docker data-root=xfs vDisk**. | ||
|
|
There was a problem hiding this comment.
Remove duplicate content section.
Lines 274-280 duplicate the content that already exists at lines 281-286 with the proper anchor. This creates confusing duplicate instructions in the release notes where users see the same overlay2 storage driver guidance twice.
The anchored section at line 281 ({/* #add-support-for-overlay2-storage-driver */}) is the correct version to keep, as it maintains the stable anchor reference.
🔧 Proposed fix
Remove lines 274-280 entirely, keeping only the properly anchored section at line 281.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~274-~274: Uneinheitliche Verwendung von Bindestrichen. Der Text enthält sowohl ‚Speicher-Treiber‘ als auch ‚Speichertreiber‘.
Context: ... Docker ### Unterstützung für overlay2 Speicher-Treiber hinzufügen Verwenden Sie auf einem ZFS...
(DE_COMPOUND_COHERENCY)
🤖 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.0.0.md`
around lines 274 - 280, Remove the duplicated unanchored section titled "###
Unterstützung für overlay2 Speicher-Treiber hinzufügen" (the paragraph offering
Docker data-root/overlay2 guidance) and keep only the properly anchored version
identified by the anchor comment {/* `#add-support-for-overlay2-storage-driver`
*/}; ensure the duplicate lines are deleted so the release notes contain a
single, anchored instruction set.
| ### Speicher | ||
|
|
||
| #### ZFS RAIDZ-Erweiterung {/* #raidz-expansion */} | ||
| #### ZFS RAIDZ-Erweiterung {/* #raidz-expansion */} {/* #raidz-expansion */} |
There was a problem hiding this comment.
Remove duplicate anchor comment.
The heading has the anchor comment duplicated: {/* #raidz-expansion*/} {/*#raidz-expansion */}. Only one anchor comment is needed per heading. As per coding guidelines, prefer Docusaurus's MDX-safe comment syntax with a single anchor per heading.
🔧 Proposed fix
-#### ZFS RAIDZ-Erweiterung {/* `#raidz-expansion` */} {/* `#raidz-expansion` */}
+#### ZFS RAIDZ-Erweiterung {/* `#raidz-expansion` */}📝 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.
| #### ZFS RAIDZ-Erweiterung {/* #raidz-expansion */} {/* #raidz-expansion */} | |
| #### ZFS RAIDZ-Erweiterung {/* `#raidz-expansion` */} |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 30-30: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
[warning] 30-30: 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/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`
at line 30, The heading "#### ZFS RAIDZ-Erweiterung" currently contains a
duplicated anchor comment "{/* `#raidz-expansion` */} {/* `#raidz-expansion` */}";
remove the duplicate so only one MDX-safe anchor comment remains (i.e., leave a
single "{/* `#raidz-expansion` */}" immediately after the heading) to satisfy the
Docusaurus/MDX comment guideline.
| - Verbesserung: Bessere Voreinstellungen für ZFS RAIDZ VDEVs | ||
|
|
||
| #### Ext2/3/4-, NTFS- und exFAT-Unterstützung {/* #ext234-ntfs-and-exfat-support */} | ||
| #### Ext2/3/4-, NTFS- und exFAT-Unterstützung {/* #ext234-ntfs-and-exfat-support */} {/* #ext234-ntfs-and-exfat-support */} |
There was a problem hiding this comment.
Remove duplicate anchor comment.
The heading has the anchor comment duplicated: {/* #ext234-ntfs-and-exfat-support*/} {/*#ext234-ntfs-and-exfat-support */}. Only one anchor comment is needed per heading. As per coding guidelines, prefer Docusaurus's MDX-safe comment syntax with a single anchor per heading.
🔧 Proposed fix
-#### 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` */}📝 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.
| #### 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` */} |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 46-46: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
[warning] 46-46: 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/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`
at line 46, The heading "Ext2/3/4-, NTFS- und exFAT-Unterstützung" contains a
duplicated MDX-safe anchor comment ({/* `#ext234-ntfs-and-exfat-support` */}
twice); remove the duplicate so only a single anchor comment remains (keep one
{/* `#ext234-ntfs-and-exfat-support` */}) immediately after the heading to satisfy
the Docusaurus MDX comment guideline.
| - Mejora: mejores ajustes predeterminados para los vdevs ZFS RAIDZ | ||
|
|
||
| #### Soporte para Ext2/3/4, NTFS y exFAT {/* #ext234-ntfs-and-exfat-support */} | ||
| #### Soporte para Ext2/3/4, NTFS y exFAT {/* #ext234-ntfs-and-exfat-support */} {/* #ext234-ntfs-and-exfat-support */} |
There was a problem hiding this comment.
Remove duplicate anchor comment.
The heading has the anchor comment duplicated: {/* #ext234-ntfs-and-exfat-support*/} {/*#ext234-ntfs-and-exfat-support */}. Only one anchor comment is needed per heading. As per coding guidelines, prefer Docusaurus's MDX-safe comment syntax with a single anchor per heading.
🔧 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` */}📝 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.
| #### 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` */} |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 45-45: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
[warning] 45-45: 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/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`
at line 45, Remove the duplicated MDX anchor comment from the heading "Soporte
para Ext2/3/4, NTFS y exFAT" so only a single Docusaurus/MDX-safe anchor
remains; locate the duplicate `{/* `#ext234-ntfs-and-exfat-support` */} {/*
`#ext234-ntfs-and-exfat-support` */}` and leave just one `{/*
`#ext234-ntfs-and-exfat-support` */}` immediately after the heading text.
| ### Ajouter un support pour le pilote de stockage overlay2 | ||
|
|
||
| Si vous utilisez **Docker data-root=répertoire** sur un volume ZFS, nous vous recommandons de naviguer vers ***Paramètres → Docker*** et de passer le **pilote de stockage Docker** à **overlay2**, puis d'effacer le contenu du répertoire et de laisser Docker retélécharger les couches d'image. Le réglage hérité **native** provoque des problèmes de stabilité significatifs sur les volumes ZFS. | ||
|
|
||
| Si conserver la possibilité de rétrograder vers des versions antérieures est important, alors passez à **Docker data-root=xfs vDisk** à la place. | ||
|
|
||
| ### Autres changements | ||
| ### Autres changements {/* #add-support-for-overlay2-storage-driver */} | ||
|
|
||
| Si vous utilisez **Docker data-root=répertoire** sur un volume ZFS, nous vous recommandons de naviguer vers ***Paramètres → Docker*** et de passer le **pilote de stockage Docker** à **overlay2**, puis d'effacer le contenu du répertoire et de laisser Docker retélécharger les couches d'image. Le réglage hérité **native** provoque des problèmes de stabilité significatifs sur les volumes ZFS. | ||
|
|
||
| Si conserver la possibilité de rétrograder vers des versions antérieures est important, alors passez à **Docker data-root=xfs vDisk** à la place. |
There was a problem hiding this comment.
Remove duplicate content section and fix section structure.
Lines 273-278 create a duplicate "Ajouter un support pour le pilote de stockage overlay2" section without an anchor, which duplicates the content at lines 281-283. Additionally, line 279 has a mismatched heading structure with anchor comment.
The proper structure should have the "Autres changements" heading with the anchor at line 279, followed by the overlay2 content. The duplicate introductory overlay2 content at lines 273-278 should be removed.
🔧 Proposed fix
Remove lines 273-278 (the duplicate overlay2 section without anchor). Keep the properly structured "Autres changements" heading at line 279 with its anchor.
🧰 Tools
🪛 LanguageTool
[style] ~275-~275: Modifiez la focalisation vers le lecteur pour obtenir une phrase dynamique.
Context: ...ta-root=répertoire** sur un volume ZFS, nous vous recommandons de naviguer vers Paramètres → Docker et de pa...
(FOCALISATION_NOUS_VOUS)
[style] ~281-~281: Modifiez la focalisation vers le lecteur pour obtenir une phrase dynamique.
Context: ...ta-root=répertoire** sur un volume ZFS, nous vous recommandons de naviguer vers Paramètres → Docker et de pa...
(FOCALISATION_NOUS_VOUS)
[style] ~281-~281: Ce mot apparaît déjà dans l’une des phrases précédant immédiatement celle-ci. Utilisez un synonyme pour apporter plus de variété à votre texte, excepté si la répétition est intentionnelle.
Context: ...e** provoque des problèmes de stabilité significatifs sur les volumes ZFS. Si conserver la p...
(FR_REPEATEDWORDS_SIGNIFICATIF)
🪛 markdownlint-cli2 (0.22.1)
[warning] 279-279: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
[warning] 279-279: 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/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md`
around lines 273 - 283, Remove the duplicated "Ajouter un support pour le pilote
de stockage overlay2" block (the repeated paragraph explaining Docker data-root
on ZFS) and keep only the single instance under the "Autres changements {/*
`#add-support-for-overlay2-storage-driver` */}" heading; specifically delete the
earlier duplicate heading and its paragraphs so the document contains a single
"Autres changements" header with the overlay2 guidance beneath it and no
orphan/mismatched heading.
| Unraid 6.9 的另一个令人兴奋的新功能是可以下载语言包并以多种语言使用 Unraid OS。 | ||
|
|
||
| 由社区成员 [@bonienl](https://forums.unraid.net/profile/2736-bonienl/) 实施了大量工作和努力，为 Unraid OS 管理工具，也被称为 WebGUI，提供多语言支持。目前，_英语、西班牙语、法语、德语、荷兰语、阿拉伯语、简体中文、葡萄牙语和波兰语_可用，并且还有其他几种语言正在开发中。 | ||
| 由社区成员 [@bonienl]([https://forums.unraid.net/profile/2736-bonienl/](https://forums.unraid.net/profile/2736-bonienl/)) 实施了大量工作和努力，为 Unraid OS 管理工具，也被称为 WebGUI，提供多语言支持。目前，_英语、西班牙语、法语、德语、荷兰语、阿拉伯语、简体中文、葡萄牙语和波兰语_可用，并且还有其他几种语言正在开发中。 |
There was a problem hiding this comment.
Malformed Markdown link with nested brackets.
The link [@bonienl]([https://forums.unraid.net/profile/2736-bonienl/](https://forums.unraid.net/profile/2736-bonienl/)) has nested brackets and will not render correctly.
🔧 Proposed fix
-由社区成员 [`@bonienl`]([https://forums.unraid.net/profile/2736-bonienl/](https://forums.unraid.net/profile/2736-bonienl/)) 实施了大量工作和努力
+由社区成员 [`@bonienl`](https://forums.unraid.net/profile/2736-bonienl/) 实施了大量工作和努力📝 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.
| 由社区成员 [@bonienl]([https://forums.unraid.net/profile/2736-bonienl/](https://forums.unraid.net/profile/2736-bonienl/)) 实施了大量工作和努力，为 Unraid OS 管理工具，也被称为 WebGUI，提供多语言支持。目前，_英语、西班牙语、法语、德语、荷兰语、阿拉伯语、简体中文、葡萄牙语和波兰语_可用，并且还有其他几种语言正在开发中。 | |
| 由社区成员 [`@bonienl`](https://forums.unraid.net/profile/2736-bonienl/) 实施了大量工作和努力，为 Unraid OS 管理工具，也被称为 WebGUI，提供多语言支持。目前，_英语、西班牙语、法语、德语、荷兰语、阿拉伯语、简体中文、葡萄牙语和波兰语_可用，并且还有其他几种语言正在开发中。 |
🤖 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/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md`
at line 133, The markdown link in the string
"[`@bonienl`]([https://forums.unraid.net/profile/2736-bonienl/](https://forums.unraid.net/profile/2736-bonienl/))"
is malformed with nested brackets; fix it by replacing that token with a
standard markdown link like
"[`@bonienl`](https://forums.unraid.net/profile/2736-bonienl/)" wherever it
appears (e.g., in the release notes text for Unraid OS WebGUI multilingual
support) so the link renders correctly.
| 每个语言包在公共[Unraid组织github仓库](https://github.com/unraid)中可用。有兴趣的用户可以克隆并提交拉取请求以纠正翻译错误。语言翻译和PR合并由[@SpencerJ](https://forums.unraid.net/profile/88446-spencerj/)管理。 | ||
|
|
||
| *有关多语言支持的更多信息，请查看[我们的指南](https://unraid.net/blog/unraid-6-9-multi-language-support)。* | ||
| *有关多语言支持的更多信息，[请查看我们的指南。]([https://unraid.net/blog/unraid-6-9-multi-language-support](https://unraid.net/blog/unraid-6-9-multi-language-support))* |
There was a problem hiding this comment.
Malformed Markdown link with nested brackets.
The link [请查看我们的指南。]([https://unraid.net/blog/unraid-6-9-multi-language-support](https://unraid.net/blog/unraid-6-9-multi-language-support)) has nested brackets and will not render correctly.
🔧 Proposed fix
-*有关多语言支持的更多信息,[请查看我们的指南。]([https://unraid.net/blog/unraid-6-9-multi-language-support](https://unraid.net/blog/unraid-6-9-multi-language-support))*
+*有关多语言支持的更多信息,[请查看我们的指南。](https://unraid.net/blog/unraid-6-9-multi-language-support)*📝 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.
| *有关多语言支持的更多信息，[请查看我们的指南。]([https://unraid.net/blog/unraid-6-9-multi-language-support](https://unraid.net/blog/unraid-6-9-multi-language-support))* | |
| *有关多语言支持的更多信息,[请查看我们的指南。](https://unraid.net/blog/unraid-6-9-multi-language-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/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md`
at line 141, The Markdown link in the line containing
`[请查看我们的指南。]([https://unraid.net/blog/unraid-6-9-multi-language-support](https://unraid.net/blog/unraid-6-9-multi-language-support))`
is malformed due to nested brackets; replace it with a standard Markdown link by
removing the inner brackets so it reads like
`[请查看我们的指南。](https://unraid.net/blog/unraid-6-9-multi-language-support)` to
ensure it renders correctly.
| ### 添加对 overlay2 存储驱动程序的支持 | ||
|
|
||
| 如果您在 ZFS 卷上使用 **Docker data-root=目录**，我们建议您前往 | ||
| ***设置 → Docker*** 并将 **Docker 存储驱动** 切换到 **overlay2**， | ||
| 然后删除目录内容，让 Docker 重新下载图像层。 | ||
|
|
||
| 如果保留降级到早期版本的能力重要，那么请切换到 **Docker data-root=xfs vDisk**。 | ||
|
|
||
| ### 其他更改 | ||
| ### 其他更改 {/* #add-support-for-overlay2-storage-driver */} | ||
|
|
||
| 如果您在 ZFS 卷上使用 **Docker data-root=目录**，我们建议您前往 | ||
| ***设置 → Docker*** 并将 **Docker 存储驱动** 切换到 **overlay2**， | ||
| 然后删除目录内容，让 Docker 重新下载图像层。 | ||
|
|
||
| 如果保留降级到早期版本的能力重要，那么请切换到 **Docker data-root=xfs vDisk**。 |
There was a problem hiding this comment.
Duplicate content and misplaced anchor comment.
This section has multiple critical issues:
-
Duplicate content: The instructions about switching Docker storage driver to overlay2 (lines 263-267 and 271-275) are identical and should appear only once.
-
Misplaced anchor: Line 269 has heading "其他更改" (Other changes) but contains anchor comment
{/*#add-support-for-overlay2-storage-driver*/}which doesn't match the heading content. -
Structural confusion: There appear to be two headings related to overlay2 (line 261 and line 269), but line 269's heading text doesn't match its anchor.
This likely resulted from a merge or translation error where content was duplicated and anchors misapplied.
🔧 Recommended structure
The section should likely be:
### 添加对 overlay2 存储驱动程序的支持 {/* `#add-support-for-overlay2-storage-driver` */}
如果您在 ZFS 卷上使用 **Docker data-root=目录**,我们建议您前往
***设置 → Docker*** 并将 **Docker 存储驱动** 切换到 **overlay2**,
然后删除目录内容,让 Docker 重新下载图像层。
如果保留降级到早期版本的能力重要,那么请切换到 **Docker data-root=xfs vDisk**。
### 其他更改
- 参见 [Tailscale 集成](`#tailscale-integration`)
- 允许自定义注册表并指定端口
...🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 269-269: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
[warning] 269-269: 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/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md`
around lines 261 - 275, Remove the duplicated overlay2 instructions and fix the
misplaced anchor: keep a single "### 添加对 overlay2 存储驱动程序的支持" block (with the
anchor {/* `#add-support-for-overlay2-storage-driver` */} appended to that
heading), delete the repeated paragraph that begins "如果您在 ZFS 卷上使用 **Docker
data-root=目录**" appearing under the second heading, and change the second
heading "### 其他更改" to be a standalone section (remove the overlay2 anchor from
it) and populate it with the intended other-changes list (e.g., Tailscale
integration, registry customizations) instead of repeating content.
|
|
||
| 查看 [VM 管理器功能](#new-in-unraid-7x-vm-manager) 部分以了解更多详情。 | ||
|
|
||
| ::: |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE="i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx"
# Basic existence + total lines
echo "== File =="
ls -l "$FILE"
echo "== Total lines =="
wc -l "$FILE"
echo "== Lines 1-60 =="
sed -n '1,60p' "$FILE" | cat -n
echo "== Lines 80-140 =="
sed -n '80,140p' "$FILE" | cat -n
echo "== Lines 140-190 =="
sed -n '140,190p' "$FILE" | cat -n
echo "== Lines 220-280 =="
sed -n '220,280p' "$FILE" | cat -n
echo "== Lines 420-460 =="
sed -n '420,460p' "$FILE" | cat -n
echo "== Admonition delimiter balance check (rough) =="
# Count occurrences of ":::" and attempt to locate any line that's exactly ":::".
echo "Count of ':::' occurrences:"
rg -n ":::" "$FILE" || true
echo "Lines that are exactly ':::':"
awk 'NR>=1 && $0 ~ /^:::\s*$/ {print NR ":" $0}' "$FILE" || trueRepository: unraid/docs
Length of output: 10525
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE="i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx"
echo "== Confirm line 25 =="
nl -ba "$FILE" | sed -n '20,30p'
echo "== Confirm vfio-pci duplicate region (around 155-170) =="
nl -ba "$FILE" | sed -n '150,180p'
echo "== Confirm snapshot storage duplicate region (around 240-260) =="
nl -ba "$FILE" | sed -n '235,260p'
echo "== Confirm Advanced/Common admonition openers (around 255-275) =="
nl -ba "$FILE" | sed -n '255,290p'Repository: unraid/docs
Length of output: 138
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE="i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx"
echo "== Confirm line 25 =="
sed -n '20,30p' "$FILE" | cat -n
echo "== Confirm vfio-pci region (150-180) =="
sed -n '145,180p' "$FILE" | cat -n
echo "== Confirm snapshot storage region (240-265) =="
sed -n '235,270p' "$FILE" | cat -n
echo "== Confirm Advanced/Common admonitions (255-290) =="
sed -n '250,295p' "$FILE" | cat -nRepository: unraid/docs
Length of output: 4337
Fix MDX syntax errors and remove duplicated content in this MDX file
-
Line 25 contains a stray closing
:::with no matching opening admonition, which can break MDX parsing.Proposed edit
-:::
</details>
- The admonition titles are missing the closing `]`:
- Change `:::info[Advanced 快照概念` → `:::info[Advanced 快照概念]`
- Change `:::tip[Common 使用案例` → `:::tip[Common 使用案例]`
<details>
<summary>Proposed edit</summary>
```diff
-:::info[Advanced 快照概念
+:::info[Advanced 快照概念]
-:::tip[Common 使用案例
+:::tip[Common 使用案例]
- Remove duplicate paragraphs:
- The “绑定到 vfio-pci 驱动程序…” paragraph appears twice back-to-back.
- The sentence
以下是一些需要考虑的要点：appears twice in the “快照存储” section.
🤖 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/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx`
at line 25, Remove the stray closing admonition token ":::” (the lone line
containing only :::) and fix malformed admonition headers by adding the missing
closing bracket so `:::info[Advanced 快照概念` becomes `:::info[Advanced 快照概念]` and
`:::tip[Common 使用案例` becomes `:::tip[Common 使用案例]`; also deduplicate content by
removing the repeated paragraph that starts with “绑定到 **vfio-pci** 驱动程序…” and
the duplicated sentence “以下是一些需要考虑的要点：” in the 快照存储 section so each sentence
appears only once.
| - 实际快照数据与您的%%VM|vm%%文件一起存储在%%cache pools|cache-pool%%或%%array|array%%上。 | ||
|
|
||
| :::info[Advanced 快照概念] | ||
| :::info[Advanced 快照概念 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify malformed admonition directives in this file
rg -n ':::(info|tip|note|warning|caution)\[[^\]]*$' i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxRepository: unraid/docs
Length of output: 104
Fix malformed Docusaurus admonition titles (missing ]).
In i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx, the admonition openings at lines 260 (:::info[Advanced 快照概念) and 266 (:::tip[Common 使用案例) don’t close the title with a trailing ], producing invalid MDX directive syntax—add the missing ] on both lines.
🤖 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/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx`
at line 260, The MDX admonition titles are malformed: the opening directives
":::info[Advanced 快照概念" and ":::tip[Common 使用案例" are missing the closing ']'
which breaks Docusaurus MDX parsing; fix both by adding the trailing ']' so they
read ":::info[Advanced 快照概念]" and ":::tip[Common 使用案例]" and verify each
admonition still has a matching closing ":::".
1 participant
Summary by CodeRabbit