Conversation
📝 WalkthroughWalkthroughThis pull request comprises extensive documentation updates across multiple language variants (German, Spanish, French, Japanese, and Chinese). Key changes include: addition of Unraid 7.2.5-rc.1 release notes in four languages; translation of instructional text from German to English; MDX structural adjustments (heading anchors, blank-line spacing); and documentation reorganizations with minor content revisions throughout the localized docs. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes The review scope spans 60+ documentation files across 5 language variants with predominantly repetitive changes (heading anchor standardization, blank-line spacing, text translations). While the volume is large, the patterns are consistent and low-complexity; most changes involve whitespace, formatting conventions, and straightforward translations. However, notable attention points include VM setup reorganization logic, content duplications in FAQ sections, and admonition label mixing that requires verification of intended phrasing. Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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: 13
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 (2)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx (1)
148-148:⚠️ Potential issue | 🟠 MajorUse MDX-safe comment syntax for heading anchor.
This heading uses the classic ID syntax
{#persistent-logs-syslog-server}, which should be avoided in translated MDX files as Crowdin's MDX import parser can reject them.🔧 Proposed fix using MDX-safe comment syntax
-## Registros persistentes (servidor syslog) {`#persistent-logs-syslog-server`} +## Registros persistentes (servidor syslog) {/* `#persistent-logs-syslog-server` */}As per coding guidelines: "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}. Do not use classic heading IDs like### Heading {#stable-anchor}in translated MDX files; Crowdin's MDX import parser can reject them."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx` at line 148, The heading "## Registros persistentes (servidor syslog) {`#persistent-logs-syslog-server`}" uses the classic {`#id`} anchor which Crowdin's MDX import rejects; replace that classic ID with Docusaurus MDX-safe comment syntax by converting the heading to use a trailing MDX comment anchor (e.g., change the heading text "## Registros persistentes (servidor syslog) {`#persistent-logs-syslog-server`}" to use the MDX-safe form with a comment `/* `#persistent-logs-syslog-server` */`) so the explicit anchor is preserved but in a Crowdin-safe format.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx (1)
46-46:⚠️ Potential issue | 🟡 MinorFix escaped list marker so step 7 renders as an ordered-list item.
Line 46 uses
\+7.instead of7., which will render as literal text instead of a numbered step. Items 1–6 above it use plain numeric markers; item 7 should match that pattern.Proposed fix
- \+7.（任意）**Include Tailscale peers in /etc/hosts** を有効にし（[ホスト名解決の強化](`#enhanced-hostname-resolution`) を参照）、Tailscale デバイスをサーバーのホスト名解決に自動的に追加して、%%Tailnet|tailnet%% 上の他のデバイスへアクセスしやすくします。 + 7.（任意）**Include Tailscale peers in /etc/hosts** を有効にし（[ホスト名解決の強化](`#enhanced-hostname-resolution`) を参照）、Tailscale デバイスをサーバーのホスト名解決に自動的に追加して、%%Tailnet|tailnet%% 上の他のデバイスへアクセスしやすくします。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx` at line 46, The ordered list item for step 7 is escaped as "\+7." so it renders as literal text; update the list marker for the "Include Tailscale peers in /etc/hosts" step to use a plain numeric marker ("7.") instead of "\+7." so it matches items 1–6 and renders as a numbered list entry.
♻️ Duplicate comments (19)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md (3)
26-26:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#rolling-back\*/}will not create a functional anchor. Use{/*#rolling-back*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md` at line 26, The heading "### ロールバック" uses a malformed anchor token `{/\* `#rolling-back` \*/}` which breaks cross-references; open the "ロールバック" heading and replace the incorrect escape with the correct JSX comment anchor `{/* `#rolling-back` */}` so the anchor becomes functional and cross-references resolve properly.
9-9:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#known-issues\*/}will not create a functional anchor. Use{/*#known-issues*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md` at line 9, The heading "### 既知の問題 {/* `#known-issues` */}" currently uses the incorrect escaped form "{/\* `#known-issues` \*/}" which prevents a functional anchor; update the heading in this file to use the correct JSX comment anchor "{/* `#known-issues` */}" so cross-references work (locate the heading line "### 既知の問題 {/\* `#known-issues` \*/}" and replace the escaped form with "{/* `#known-issues` */}").
3-3:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#upgrade-notes\*/}will not create a functional anchor. Use{/*#upgrade-notes*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md` at line 3, The heading uses an incorrect escaped anchor token "{/\* `#upgrade-notes` \*/}" which doesn't create a functional anchor; replace it with the correct JSX-style comment anchor "{/* `#upgrade-notes` */}" in the heading line "## アップグレードに関する注意事項" so cross-references to the `#upgrade-notes` anchor resolve properly.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md (3)
11-12:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#known-issues\*/}will not create a functional anchor. Use{/*#known-issues*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md` around lines 11 - 12, The heading "### 既知の問題 {/\* `#known-issues` \*/}" uses incorrect escaped anchor syntax; replace the broken token with the correct JSX comment-style anchor "/* `#known-issues` */" so the line reads "### 既知の問題 {/* `#known-issues` */}" to restore functional cross-reference anchors.
46-47:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#ext234-ntfs-and-exfat-support\*/}will not create a functional anchor. Use{/*#ext234-ntfs-and-exfat-support*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md` around lines 46 - 47, The heading "#### Ext2/3/4、NTFS、exFAT のサポート" contains an incorrect anchor token `{/\* `#ext234-ntfs-and-exfat-support` \*/}`; replace that token with the correct JSX comment-style anchor `{/* `#ext234-ntfs-and-exfat-support` */}` so the anchor is generated properly for cross-references.
22-23:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#rolling-back\*/}will not create a functional anchor. Use{/*#rolling-back*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md` around lines 22 - 23, The heading "### ロールバック {/\* `#rolling-back` \*/}" uses incorrect escaped anchor syntax; replace the malformed token with the correct JSX-style comment anchor "{/* `#rolling-back` */}" so the anchor becomes functional for cross-references (update the heading line containing "### ロールバック" to use "{/* `#rolling-back` */}").i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md (2)
15-16:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#rolling-back\*/}will not create a functional anchor. Use{/*#rolling-back*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md` around lines 15 - 16, The heading "### ロールバック {/\* `#rolling-back` \*/}" uses incorrect escaped anchor syntax; replace the sequence "{/\* `#rolling-back` \*/}" with the correct JSX-style comment anchor "{/* `#rolling-back` */}" so the anchor name "#rolling-back" is actually recognized for cross-references in the document (locate the Markdown heading line containing "ロールバック" and update the comment syntax).
11-12:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#known-issues\*/}will not create a functional anchor. Use{/*#known-issues*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md` around lines 11 - 12, The heading currently uses an incorrect escaped anchor `{/\* `#known-issues` \*/}` which won't produce a usable anchor; update the anchor in the heading `### 既知の問題 {/\* `#known-issues` \*/}` to the correct JSX-style comment anchor `{/* `#known-issues` */}` so cross-references to `#known-issues` work properly.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md (2)
11-12:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#rolling-back\*/}will not create a functional anchor. Use{/*#rolling-back*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md` around lines 11 - 12, The heading "### ロールバック" contains an incorrect anchor comment `{/\* `#rolling-back` \*/}`; replace that token with the correct MDX-style comment anchor `{/* `#rolling-back` */}` so the cross-reference anchor is created properly (look for the string `{/\* `#rolling-back` \*/}` next to the "### ロールバック" heading and update it to `{/* `#rolling-back` */}`).
7-8:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#known-issues\*/}will not create a functional anchor. Use{/*#known-issues*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md` around lines 7 - 8, Replace the incorrect escaped anchor token in the heading "### 既知の問題 {/\* `#known-issues` \*/}" with the proper JSX-style comment anchor "{/* `#known-issues` */}" so the anchor works for cross-references; update the heading text to "### 既知の問題 {/* `#known-issues` */}" by changing the token in that line.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md (2)
12-12:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#rolling-back\*/}will not create a functional anchor. Use{/*#rolling-back*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md` at line 12, The heading "### ロールバック" contains an incorrect anchor token `{/\* `#rolling-back` \*/}`; replace that exact token with the correct JSX-style comment anchor `{/* `#rolling-back` */}` so the anchor becomes functional and cross-references resolve properly.
7-7:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#known-issues\*/}will not create a functional anchor. Use{/*#known-issues*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md` at line 7, The heading "### 既知の問題 {/\* `#known-issues` \*/}" uses incorrect escaped braces and will not create an anchor; update that heading to use the proper JSX comment anchor syntax "{/* `#known-issues` */}" (i.e., replace "{/\* `#known-issues` \*/}" with "{/* `#known-issues` */}") so cross-references resolve correctly.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md (2)
9-9:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
Same issue as line 3 - the escaped syntax
{/\*#known-issues\*/}will not create a functional anchor. Use{/*#known-issues*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md` at line 9, The heading "### 既知の問題 {/\* `#known-issues` \*/}" uses an incorrect escaped comment syntax that breaks the anchor; update the heading in this file so the JSX-style anchor comment is written as {/* `#known-issues` */} (i.e., change {/\* `#known-issues` \*/} to {/* `#known-issues` */}) to restore the functional anchor for cross-references.
26-27:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
Same issue - the escaped syntax
{/\*#rolling-back\*/}will not create a functional anchor. Use{/*#rolling-back*/}instead.The blank line addition on line 27 is fine.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md` around lines 26 - 27, The heading "### ロールバック" uses an incorrect anchor token `{/\* `#rolling-back` \*/}` which prevents cross-references from working; update the token to the correct JSX-style comment anchor `{/* `#rolling-back` */}` so the anchor is recognized and links resolve properly.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md (2)
17-18:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#rolling-back\*/}will not create a functional anchor. Use{/*#rolling-back*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md` around lines 17 - 18, The heading "ロールバック" currently uses an incorrect escaped anchor token "{/\* `#rolling-back` \*/}" which won't produce a functional anchor; locate the heading line containing "ロールバック" and replace the incorrect token with the correct JSX comment anchor "{/* `#rolling-back` */}" so the cross-reference anchor works as intended.
7-8:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#known-issues\*/}will not create a functional anchor. Use{/*#known-issues*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md` around lines 7 - 8, The heading "既知の問題" uses an incorrect escaped anchor `{/\* `#known-issues` \*/}` which doesn't produce a usable anchor; update the heading to use the correct JSX-style comment anchor `{/* `#known-issues` */}` so cross-references work (locate the "既知の問題" heading and replace `{/\* `#known-issues` \*/}` with `{/* `#known-issues` */}`).i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md (3)
50-51:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#rolling-back\*/}will not create a functional anchor. Use{/*#rolling-back*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md` around lines 50 - 51, The heading "### ロールバック {/\* `#rolling-back` \*/}" contains an incorrectly escaped anchor token; replace the malformed `{/\* `#rolling-back` \*/}` with the correct JSX-style comment anchor `{/* `#rolling-back` */}` so the anchor works for cross-references in the "ロールバック" heading.
3-3:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#upgrade-notes\*/}will not create a functional anchor. Use{/*#upgrade-notes*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md` at line 3, The heading "## アップグレードに関する注意事項" contains an incorrect escaped anchor `{/\* `#upgrade-notes` \*/}`; replace that fragment with the correct JSX-style anchor `{/* `#upgrade-notes` */}` so the anchor token is parsed and cross-references work (look for the heading text or the incorrect `{/\* `#upgrade-notes` \*/}` string to locate the change).
8-8:⚠️ Potential issue | 🔴 CriticalCritical: Incorrect heading anchor syntax will break cross-references.
The escaped syntax
{/\*#known-issues\*/}will not create a functional anchor. Use{/*#known-issues*/}instead.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md` at line 8, The heading uses an incorrect escaped JSX comment anchor syntax "### 既知の問題 {/\* `#known-issues` \*/}"; replace that fragment with the correct JSX comment form "/*#known-issues*/" wrapped as a JSX comment like {/* `#known-issues` */} in the "### 既知の問題" heading so the anchor works for cross-references (locate the heading line starting with "### 既知の問題" and update the comment syntax).
🟡 Minor comments (26)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx-54-54 (1)
54-54:⚠️ Potential issue | 🟡 MinorUntranslated English paragraph in Japanese locale doc.
Line 54 is fully English in a Japanese page, which creates a localization break for end users. Please translate this paragraph to Japanese (keeping the same technical terms/placeholders).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx` at line 54, Translate the English paragraph into Japanese while preserving all technical placeholders and formatting: keep %%Mover|mover%% and %%syslog|syslog%% exactly as-is, retain the bold/italic path "***Settings → Scheduler → Mover Settings***", and preserve the warning about enabling mover logging only for troubleshooting because it may reveal file paths and names; replace the English sentence with an equivalent concise Japanese sentence that conveys the same meaning.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx-64-68 (1)
64-68:⚠️ Potential issue | 🟡 MinorMixed-language heading/list text should be fully Japanese.
Line 64 and Line 68 include English text (
When...,Extremely slow...) in the JA doc. Please localize both strings to Japanese for consistency and readability.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx` around lines 64 - 68, The heading and list contain mixed English and Japanese; replace the English fragments so the entire heading "When およびドライブ速度をテストする理由" and the list item "Extremely slow %%parity|parity%% builds or %%parity check|parity-check%%s" are fully Japanese: localize the heading's leading "When" and the list item's "Extremely slow ... builds or ... check(s)" into natural Japanese while preserving the special placeholders/shortcodes (%%parity|parity%% and %%parity check|parity-check%%) and surrounding punctuation/formatting; ensure the resulting strings read fluently in Japanese and keep the MDX markup unchanged.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx-69-72 (1)
69-72:⚠️ Potential issue | 🟡 MinorCollapse repeated
Xreplacement guidance to a single line.This instruction is duplicated multiple times in the same step. Please keep just one occurrence.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx` around lines 69 - 72, The step contains multiple duplicate lines of the sentence "Ersetzen Sie `X` durch die spezifische Nummer der Datenfestplatte, die Sie entfernen möchten."; remove the duplicates and leave a single occurrence of that sentence in the step so the replacement guidance appears only once (search for the repeated string to locate the block to edit).i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx-69-70 (1)
69-70:⚠️ Potential issue | 🟡 MinorRemove the duplicated
Xplaceholder instruction in Step 6.The same replacement note appears twice in a row here. Keep only one instance to avoid redundant guidance.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx` around lines 69 - 70, In Step 6 remove the duplicated sentence "`X` は、削除するデータディスクの番号に置き換えてください。" so only a single instance remains; keep one copy of that placeholder instruction and delete the consecutive duplicate to avoid redundant guidance.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx-69-72 (1)
69-72:⚠️ Potential issue | 🟡 MinorRemove repeated
Remplacez \X` ...` lines in this step.The placeholder note is duplicated in sequence; keep a single instance to avoid clutter.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx` around lines 69 - 72, The same placeholder sentence "Remplacez `X` par le numéro spécifique du disque de données que vous supprimez." is duplicated four times; keep a single instance of that sentence in the step and remove the extra repeated lines so the instruction appears only once and retains the surrounding paragraph formatting in the document (update the block in removing-disks-from-array.mdx where the repeated sentence occurs).i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx-69-72 (1)
69-72:⚠️ Potential issue | 🟡 MinorDeduplicate the
Xplaceholder instruction under theddcommand.The same sentence is repeated several times in this block; retaining one line is clearer and easier to maintain.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx` around lines 69 - 72, Under the dd command block remove the duplicate repeated sentence "Reemplace `X` con el número específico del disco de datos que está eliminando." so only one instance remains; locate the repeated placeholder text under the dd instruction in the "removing-disks-from-array.mdx" content and keep a single occurrence to avoid duplication and improve maintainability.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/unraid-net.mdx-12-12 (1)
12-12:⚠️ Potential issue | 🟡 MinorLocalize this bullet to Japanese for locale consistency.
Line 12 is in English inside a Japanese doc, so the rendered page becomes mixed-language. Please translate this bullet to Japanese to match the rest of the file.
Suggested fix
-- **%%Single Sign-On (SSO)|sso%%:** Access Unraid's systems with one set of credentials. +- **%%Single Sign-On (SSO)|sso%%:** 1組の認証情報で Unraid のシステムにアクセスできます。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/unraid-net.mdx` at line 12, Replace the English bullet "**%%Single Sign-On (SSO)|sso%%:** Access Unraid's systems with one set of credentials." with a Japanese-localized version while preserving the markup and the sso token; e.g., change the label token "**%%Single Sign-On (SSO)|sso%%:**" to "**%%シングルサインオン (SSO)|sso%%:**" and translate the description to Japanese such as "1組の資格情報でUnraidのシステムにアクセスします。", keeping the same bold/markdown and token structure.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx-84-84 (1)
84-84:⚠️ Potential issue | 🟡 MinorUntranslated English sentence in JA locale doc.
Line 84 should be localized to Japanese to match the rest of this page and avoid mixed-language UX.
💡 Proposed fix
-- For non-%%array|array%% drives (like %%cache|cache%%-only devices), use the direct partition path, e.g., `/dev/sdj1`. +- %%array|array%% 以外のドライブ（%%cache|cache%% 専用デバイスなど）では、`/dev/sdj1` のような直接パーティションパスを使用してください。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx` at line 84, Replace the untranslated English sentence "For non-%%array|array%% drives (like %%cache|cache%%-only devices), use the direct partition path, e.g., `/dev/sdj1`." with a Japanese translation that preserves the placeholders %%array|array%% and %%cache|cache%% and the example path `/dev/sdj1` (e.g., "%%array|array%%でないドライブ（%%cache|cache%%専用デバイスなど）の場合は、直接パーティションパス（例: `/dev/sdj1`）を使用してください。").i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx-68-70 (1)
68-70:⚠️ Potential issue | 🟡 MinorLocalize image
altand captions for JA accessibility consistency.The updated
alttext andfigcaptionstrings are now English in a Japanese doc. Please translate these strings back to Japanese so screen readers and visual labels stay locale-consistent.Also applies to: 74-76
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx` around lines 68 - 70, Replace the English accessibility strings with Japanese translations: update the img tag alt attribute value ("User shares distribution example") to a concise Japanese alt like "ユーザー共有の分布の例" and change the figcaption text ("User shares - Distribution") to "ユーザー共有 - 分布"; apply the same replacements for the second occurrence of the same img/figcaption pair in the file so both alt and caption are locale-consistent.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx-103-104 (1)
103-104:⚠️ Potential issue | 🟡 MinorRestore the stable anchor for this heading to avoid a broken intra-page link.
Line 84 links to
#adding-disks-to-a-pool, but Line 103 no longer defines that anchor, so this jump can fail in the Japanese page.🔧 Proposed fix
-## プールへのディスク追加 +## プールへのディスク追加 {/* `#adding-disks-to-a-pool` */}As per coding guidelines, explicit heading anchors in translated MDX should use Docusaurus’s MDX-safe comment syntax (
### Heading {/*#stable-anchor*/}).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx` around lines 103 - 104, The translated heading "## プールへのディスク追加" is missing the stable anchor referenced by links to "#adding-disks-to-a-pool"; update that heading to include an explicit MDX-safe anchor using Docusaurus comment syntax (e.g., add {/* `#adding-disks-to-a-pool` */} immediately after the heading text) so intra-page links resolve correctly; modify the "## プールへのディスク追加" heading accordingly to restore the stable anchor.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx-92-92 (1)
92-92:⚠️ Potential issue | 🟡 MinorRevert mixed-language admonition titles in this Japanese locale file.
Line 92, Line 394, and Line 404 introduce English/mixed labels, which reads as an accidental localization regression in
i18n/ja.💡 Suggested text fix
-:::important[Initial setup requirements] +:::important[初期セットアップ要件] -:::tip[Default の既定設定] +:::tip[Gmail の既定設定] -:::warning[Security 推奨] +:::warning[セキュリティ推奨事項]Also applies to: 394-394, 404-404
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx` at line 92, Replace the mixed-language admonition titles introduced by the token ":::important[Initial setup requirements]" with a proper Japanese title across the locale file; locate each occurrence of the admonition token (the instances that currently contain English/mixed text) and change the bracketed title to the appropriate Japanese text (e.g., "初期セットアップの要件" or your established Japanese translation for "Initial setup requirements") so all admonition headings in this MDX file are fully localized.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-37-38 (1)
37-38:⚠️ Potential issue | 🟡 MinorRemove duplicate paragraph.
Lines 37-38 are an exact duplicate of the paragraph at lines 35-36. This appears to be an accidental duplication and should be removed.
Proposed fix
Überprüfen Sie stets auf Firmware-Updates und stellen Sie sicher, dass der Controller auf HBA/IT-Modus und nicht auf %%RAID|raid%%-Modus eingestellt ist. Sie können den [Empfohlene Controller-Thread](https://forums.unraid.net/topic/102010-recommended-controllers-for-unraid/) aufrufen, um Modelle zu finden, die von der Community erfolgreich getestet wurden. -Überprüfen Sie stets auf Firmware-Updates und stellen Sie sicher, dass der Controller auf HBA/IT-Modus und nicht auf %%RAID|raid%%-Modus eingestellt ist. Sie können den [Empfohlene Controller-Thread](https://forums.unraid.net/topic/102010-recommended-controllers-for-unraid/) aufrufen, um Modelle zu finden, die von der Community erfolgreich getestet wurden. -🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx` around lines 37 - 38, Remove the duplicated paragraph that repeats the firmware/controller guidance (the second copy of "Überprüfen Sie stets auf Firmware-Updates..." which is identical to the previous paragraph); keep only one instance of that paragraph in the FAQ content (the block referencing HBA/IT vs %%RAID|raid%% and the Recommended Controller thread) and ensure surrounding paragraphs and links remain intact and properly spaced.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-169-169 (1)
169-169:⚠️ Potential issue | 🟡 MinorLocalization regression at Line 169 (English text in JA doc)
This paragraph should be Japanese to match the rest of the page and locale expectations.
Suggested fix
-Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible. +多くのマザーボードでは、起動デバイスとして選択できるハードドライブ数が 12 台までに制限されています。USB フラッシュドライブがハードドライブとして認識される場合、物理ドライブを 12 台接続した後はその USB から起動できなくなる可能性があります。可能な限り、BIOS でフラッシュドライブをリムーバブルデバイスとして扱うように設定してください。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 169, The paragraph in deploy-and-configure-unraid-os.mdx that currently reads "Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible." should be replaced with an appropriate Japanese translation while preserving the original intent and punctuation; locate that exact string and swap it for a natural Japanese version (e.g., 「多くのマザーボードは起動デバイスの選択を12台のハードドライブに制限しています。USBフラッシュドライブがハードドライブとして認識される場合、物理ハードドライブを12台取り付けた後にそこから起動できないことがあります。可能であればBIOSでフラッシュドライブをリムーバブルデバイスとして扱うよう設定してください。」), keeping encoding and surrounding formatting unchanged.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx-77-79 (1)
77-79:⚠️ Potential issue | 🟡 MinorRemove the duplicated Windows label.
Line 77 and Line 79 contain the same label (
**Windows 7 以降:**). Keep one to avoid duplicated localized content.Proposed fix
**Windows 7 以降:** - -**Windows 7 以降:**🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx` around lines 77 - 79, Remove the duplicated localized label "**Windows 7 以降:**" so it appears only once; locate both occurrences of the exact string "**Windows 7 以降:**" in create-your-bootable-media.mdx (the duplicated header at lines shown in the diff) and delete one of them, ensuring surrounding section structure and spacing remain correct after removal.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx-135-143 (1)
135-143:⚠️ Potential issue | 🟡 MinorUse fully Japanese admonition labels for consistency.
Line 135 (
General ヒント) and Line 143 (Always 変更) look like partial-English artifacts and reduce localization quality. Please normalize these labels to natural Japanese (same for Line 110 after syntax fix).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx` around lines 135 - 143, The admonition labels contain mixed English/Japanese; replace the mixed labels so they are fully Japanese: change "General ヒント" to "一般的なヒント" (or simply "ヒント") and change "Always 変更" to a natural Japanese label such as "常に" or "変更についての注意" as appropriate; also scan for the similar partial-English admonition referenced near line 110 and normalize it to fully Japanese wording so all admonition headers (e.g., the "tip" and "info" blocks) are consistently localized.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx-36-36 (1)
36-36:⚠️ Potential issue | 🟡 MinorStep numbering skips “1” and starts at “2”.
Line 36 and Line 72 currently begin at steps 2 and 3, which breaks the procedure flow. Please renumber sequentially after deduplicating the extra step block.
Proposed fix
- <summary><strong>2. ホスト上で VM をセットアップする</strong> - クリックして展開/折りたたみ</summary> + <summary><strong>1. ホスト上で VM をセットアップする</strong> - クリックして展開/折りたたみ</summary> ... - <summary><strong>3. VM を作成して起動する</strong> - クリックして展開/折りたたみ</summary> + <summary><strong>2. VM を作成して起動する</strong> - クリックして展開/折りたたみ</summary>Then renumber the remaining “VM を設定する” section summary to
3..Also applies to: 72-72
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx` at line 36, The step list in the collapsible summary "2. ホスト上で VM をセットアップする" is misnumbered (starts at 2) and there is a duplicate extra step block causing the sequence to skip 1 and mislabel the following section; remove the duplicated step block, renumber the first collapsible summary to start at "1." and then update the subsequent "VM を設定する" summary (currently labeled "2." or "3.") to "2." and any following summaries to sequential numbers (e.g., update the summary text "2. ホスト上で VM をセットアップする" and the later "VM を設定する" summary so the visible step numbers read 1., 2., 3. in order).i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx-77-77 (1)
77-77:⚠️ Potential issue | 🟡 MinorKeep localized copy fully German in the DE doc.
Line [77] and Line [79] introduce English/mixed text in a German page.
Suggested wording fix
-%%Tailscale|tailscale%% exit nodes offer a secure and modern way to route your Unraid server's outgoing traffic through another device on your %%Tailnet|tailnet%%. This setup provides the security of a %%VPN|vpn-tunnel%% while leveraging %%Tailscale|tailscale%%'s easy-to-use mesh networking, making it ideal for users who want encrypted outgoing traffic without the complexity of traditional %%VPN|vpn-tunnel%%s. +%%Tailscale|tailscale%%-Exit-Nodes bieten eine sichere und moderne Möglichkeit, den ausgehenden Datenverkehr Ihres Unraid-Servers über ein anderes Gerät in Ihrem %%Tailnet|tailnet%% zu leiten. Dieses Setup bietet die Sicherheit eines %%VPN|vpn-tunnel%% und nutzt gleichzeitig das einfach zu verwendende Mesh-Netzwerk von %%Tailscale|tailscale%%. Es ist ideal für Benutzer, die verschlüsselten ausgehenden Verkehr ohne die Komplexität klassischer %%VPN|vpn-tunnel%%s möchten. -:::tip[When Sie Tailscale Exit-Nodes verwenden sollten] +:::tip[Wann Sie Tailscale Exit-Nodes verwenden sollten]Also applies to: 79-79
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx` at line 77, The paragraph contains mixed English/German and must be fully localized to German: replace the English words in the sentence that uses the tokens %%Tailscale|tailscale%%, %%Tailnet|tailnet%% and %%VPN|vpn-tunnel%% with German wording (e.g., translate the whole sentence to German while keeping the token markers intact), and apply the same change to the similar occurrence later in the file; ensure tokens remain unchanged (%%Tailscale|tailscale%%, %%Tailnet|tailnet%%, %%VPN|vpn-tunnel%%) but the surrounding copy is fully German and idiomatic.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx-64-64 (1)
64-64:⚠️ Potential issue | 🟡 MinorThese updated strings should stay in German for the DE locale.
Line [64] and Line [139] are now mixed/English in a German translation file.
Suggested wording fix
-:::note[Benefits des Ruhezustands] +:::note[Vorteile des Ruhezustands] -Windows Search indexing continuously scans your %%virtual machine|vm%%'s storage to catalog files for faster search results. However, on a %%virtual machine|vm%%, this can cause unnecessary disk I/O, slow down performance, and increase wear on your physical storage, especially SSDs in your [%%cache pool|cache-pool%%](../manage-storage/cache-pools.mdx). +Die Windows-Suchindizierung durchsucht kontinuierlich den Speicher Ihrer %%virtual machine|vm%%, um Dateien für schnellere Suchergebnisse zu katalogisieren. In einer %%virtual machine|vm%% kann dies jedoch unnötige Festplatten-I/O verursachen, die Leistung verringern und den Verschleiß Ihres physischen Speichers erhöhen – insbesondere von SSDs in Ihrem [%%cache pool|cache-pool%%](../manage-storage/cache-pools.mdx).Also applies to: 139-139
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx` at line 64, The file contains English text in a German locale; replace the mixed English strings at the note block and the other occurrence with proper German translations so the DE locale remains fully German. Locate the inline admonition starting with ":::note[Benefits des Ruhezustands]" and the other mixed string near the second occurrence (around line 139), update the bracketed title and any English body text to the correct German phrasing, and verify the surrounding nodes use German as well so no English remains in these admonitions.i18n/ja/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx-58-58 (1)
58-58:⚠️ Potential issue | 🟡 MinorFix the note title text; current bracketing reads broken in Japanese.
Server [コンテキストが必要]is awkward for JP localization and appears partially bracketed. Prefer a clear localized label.Proposed fix
-:::note[Server [コンテキストが必要] +:::note[サーバーコンテキストが必要]🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx` at line 58, The note title token ":::note[Server [コンテキストが必要]" is malformed and awkward in Japanese; update the note header in redeem-activation-code.mdx by replacing the English + bracketed fragment "Server [コンテキストが必要]" with a proper localized label such as "サーバー（要コンテキスト）" (or another natural JP phrasing) so the note reads like ":::note[サーバー（要コンテキスト）]" and uses full-width parentheses for Japanese typography.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx-33-33 (1)
33-33:⚠️ Potential issue | 🟡 MinorKeep localized prose in Japanese in this JA file.
Line 33 is fully English, which creates mixed-language UX in a Japanese doc section.
Suggested fix
-Unraid supports %%ZFS|zfs%% for any storage pool. You can create a new %%ZFS|zfs%% pool, import one from another system, or use Unraid’s unique hybrid %%ZFS|zfs%% setup: add a %%ZFS|zfs%%-formatted disk directly to the Unraid %%array|array%% (not a pool) and combine %%ZFS|zfs%% features with Unraid’s %%parity|parity%% protection. +Unraid は任意のストレージプールで %%ZFS|zfs%% をサポートします。新しい %%ZFS|zfs%% プールを作成することも、別システムからインポートすることもできます。また、Unraid 独自のハイブリッド %%ZFS|zfs%% 構成として、%%ZFS|zfs%% 形式のディスクを Unraid の %%array|array%%（プールではありません）へ直接追加し、%%ZFS|zfs%% の機能と Unraid の %%parity|parity%% 保護を組み合わせることもできます。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx` at line 33, Translate the fully-English sentence that contains the tokens %%ZFS|zfs%%, %%array|array%%, and %%parity|parity%% into natural Japanese while preserving all inline tokens and punctuation exactly as-is; replace the sentence in the MDX content that currently reads "Unraid supports %%ZFS|zfs%% for any storage pool. You can create a new %%ZFS|zfs%% pool, import one from another system, or use Unraid’s unique hybrid %%ZFS|zfs%% setup: add a %%ZFS|zfs%%-formatted disk directly to the Unraid %%array|array%% (not a pool) and combine %%ZFS|zfs%% features with Unraid’s %%parity|parity%% protection." with its Japanese equivalent, ensuring tokens like %%ZFS|zfs%%, %%array|array%%, and %%parity|parity%% remain unchanged.i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx-94-104 (1)
94-104:⚠️ Potential issue | 🟡 MinorRemove duplicated transition and link lines in this recovery block.
This section currently repeats
Dann:and the internal-boot FAQ sentence back-to-back.Suggested fix
-Dann: - Dann: @@ -Weitere Details zum internen Boot finden Sie in den [FAQ zum internen Boot (7.3+)](/unraid-os/getting-started/set-up-unraid/internal-boot-faq/). - Weitere Details zum internen Boot finden Sie in den [FAQ zum internen Boot (7.3+)](/unraid-os/getting-started/set-up-unraid/internal-boot-faq/).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx` around lines 94 - 104, Remove the duplicated transitional line "Dann:" and the repeated FAQ sentence linking to /unraid-os/getting-started/set-up-unraid/internal-boot-faq/ from the recovery block so the section reads once with a single "Dann:" followed by the numbered steps and a single FAQ link; edit the block containing the duplicated "Dann:" and the repeated internal-boot FAQ sentence to leave one instance of each.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md-33-33 (1)
33-33:⚠️ Potential issue | 🟡 MinorSpanish wording appears mistranslated.
“modelo de mayúsculas y minúsculas” does not fit the intended “case/chassis model images” meaning in this context. Please revise this phrase for clarity.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md` at line 33, The Spanish line contains a mistranslation: replace the incorrect phrase "modelo de mayúsculas y minúsculas" with a clear term meaning case/chassis model images (e.g., "imágenes del modelo del chasis" or "imágenes del modelo de la carcasa") so the sentence reads "Corrección: Restaura las imágenes personalizadas del modelo del chasis en la página de inicio de sesión" (or similar wording) to accurately convey "case/chassis model images."i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md-9-9 (1)
9-9:⚠️ Potential issue | 🟡 MinorTranslate line 9 to French.
Line 9 contains English text in a French translation file. The entire content should be localized to French for consistency with the rest of the document.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md` at line 9, Replace the English sentence "For step-by-step instructions, see [Upgrading Unraid]... Questions about your [license]...?" with a French translation that preserves the same links; e.g. change it to: "Pour des instructions pas à pas, voir [Mise à niveau d'Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Des questions concernant votre [licence](/unraid-os/troubleshooting/licensing-faq/) ?" and save in the same file so the French translation is consistent with the rest of the document.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md-9-9 (1)
9-9:⚠️ Potential issue | 🟡 MinorLine 9 is still English in a Spanish localization file.
This sentence must be localized to Spanish. All surrounding content in the file is properly translated.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md` at line 9, Replace the English sentence "For step-by-step instructions, see [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)?" with a Spanish translation, preserving both markdown links and punctuation; for example use "Para instrucciones paso a paso, consulte [Actualizar Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). ¿Preguntas sobre su [licencia](/unraid-os/troubleshooting/licensing-faq/)?" and ensure the surrounding content remains unchanged.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md-9-9 (1)
9-9:⚠️ Potential issue | 🟡 MinorTranslate line 9 to Chinese.
Line 9 contains only English text and should be localized. The rest of the file is properly translated to Chinese, making this untranslated sentence inconsistent. For reference, the Japanese translation shows this line successfully localized: "手順については、Unraid のアップグレード をご覧ください。ライセンス に関するご質問がありますか?"
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md` at line 9, Translate the English sentence "For step-by-step instructions, see [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)?" (the text at line 9 in the diff) into Chinese; replace it with a localized version such as "手順については、[Unraid のアップグレード]… " but in Chinese: "有关逐步说明，请参阅[升级 Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/)。关于您的[许可证](/unraid-os/troubleshooting/licensing-faq/)有疑问吗？" and ensure the links remain unchanged.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md-9-9 (1)
9-9:⚠️ Potential issue | 🟡 MinorUntranslated English sentence in German locale page.
Line 9 is still English in a German translation file. Please localize it (or confirm this line is intentionally left in English across locales).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md` at line 9, The sentence "For step-by-step instructions, see [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)?" is still in English in the German release-notes file; replace it with a German translation (preserving the same markdown links and targets) such as "Für Schritt-für-Schritt-Anleitungen siehe [Unraid aktualisieren](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Fragen zu Ihrer [Lizenz](/unraid-os/troubleshooting/licensing-faq/)?" or confirm that the English sentence is intentionally left untranslated across locales.
🧹 Nitpick comments (2)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx (1)
16-16: Consider applying consistent blank line formatting to all numbered sections.Blank lines were added after the headings for sections 1 and 2, but sections 3 through 13 do not have similar blank lines after their headings. For better consistency and readability throughout the document, consider either:
- Adding blank lines after all numbered section headings (lines 27, 33, 39, 50, 62, 72, 82, 90, 96, 113, 119), or
- Removing the blank lines after sections 1 and 2 to match the rest of the document
Also applies to: 22-22
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx` at line 16, The document has inconsistent blank-line formatting after numbered section headings: headings for sections 1 and 2 have a blank line but sections 3–13 do not; make this consistent by adding a single blank line after each numbered section heading (i.e., after headings 1 through 13) so all numbered sections match, updating the headings around sections 3–13 to include the same blank line as sections 1 and 2.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx (1)
17-17: Use a fully localized caution title for Japanese docs.Line 17 mixes English and Japanese (
Important 考慮事項). Consider using a fully Japanese title for consistency.Proposed tweak
-:::caution[Important 考慮事項] +:::caution[重要な考慮事項]🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx` at line 17, Replace the mixed-language caution title ":::caution[Important 考慮事項]" with a fully Japanese title (e.g., ":::caution[重要な考慮事項]" or another appropriate Japanese phrase) in the MDX file so the caution block title is entirely localized; update the string inside the caution shortcode (the ":::caution[...]" token) accordingly to maintain consistency across Japanese docs.
| ### Pruebas de rendimiento de lectura del disco | ||
|
|
||
| De forma predeterminada, los diagnósticos se anonimizan automáticamente. Si habilitas el registro de %%Mover|mover%% en ***Settings → Scheduler → Mover Settings***, el %%syslog|syslog%% incluirá detalles sobre los archivos que procesa %%Mover|mover%%. Es mejor habilitar el registro de %%Mover|mover%% solo al solucionar problemas específicos relacionados con %%Mover|mover%%, ya que puede revelar rutas y nombres de archivos. | ||
| By default, diagnostics are automatically anonymized. If you enable %%Mover|mover%% logging under ***Settings → Scheduler → Mover Settings***, the %%syslog|syslog%% will include details about files the %%Mover|mover%% processes. It's best to allow %%Mover|mover%% logging only when troubleshooting specific %%Mover|mover%%-related issues, as it may reveal file paths and names. |
There was a problem hiding this comment.
Critical localization error: English content in Spanish translation file.
This paragraph is in English but should be in Spanish since this is a Spanish translation file (i18n/es/). The surrounding content and headings are all in Spanish, making this English paragraph inconsistent and breaking the user experience for Spanish-speaking users.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx`
at line 62, Replace the English paragraph with a Spanish translation in this
Spanish locale file: keep the placeholders %%Mover|mover%% and %%syslog|syslog%%
exactly as-is, preserve the emphasis markup (***), and translate the UI path to
Spanish (e.g., "Ajustes → Programador → Configuración de Mover") so the
paragraph reads fully in Spanish and retains the same meaning about
anonymization and when to enable mover logging.
| # バージョン 6.12.13 2024-08-22 | ||
|
|
||
| ## アップグレードに関する注意事項 | ||
| ## アップグレードに関する注意事項 {/\* #upgrade-notes \*/} |
There was a problem hiding this comment.
Critical: Incorrect MDX anchor syntax - backslashes will break anchor functionality.
The heading anchors use escaped syntax {/\* #anchor \*/} which is incorrect for MDX. The backslashes prevent these from being parsed as MDX comments, causing the text to render literally instead of creating functional anchors.
As per coding guidelines, use the correct MDX comment syntax: {/* #anchor */} (without backslashes).
🐛 Correct anchor syntax
-## アップグレードに関する注意事項 {/\* `#upgrade-notes` \*/}
+## アップグレードに関する注意事項 {/* `#upgrade-notes` */}
-### 既知の問題 {/\* `#known-issues` \*/}
+### 既知の問題 {/* `#known-issues` */}
-### ロールバック {/\* `#rolling-back` \*/}
+### ロールバック {/* `#rolling-back` */}Also applies to: 9-9, 17-17
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md`
at line 3, The MDX heading anchor uses incorrect escaped comment syntax "{/\*
`#upgrade-notes` \*/}" which renders literally; update the anchor comment for the
heading "## アップグレードに関する注意事項" (and the other occurrences referenced at lines 9
and 17) to the proper MDX comment form "{/* `#upgrade-notes` */}" (remove the
backslashes) so the anchor is parsed and functions correctly.
| # バージョン 6.12.14 2024-11-26 | ||
|
|
||
| ## アップグレードに関する注意事項 | ||
| ## アップグレードに関する注意事項 {/\* #upgrade-notes \*/} |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check how many files have escaped anchor syntax
rg -n --type=md '{/\\* #[a-z-]+ \\*/}' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/
# Check if there are any correctly formatted unescaped anchors
rg -n --type=md '{/\* #[a-z-]+ \*/}' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/Repository: unraid/docs
Length of output: 244
🏁 Script executed:
cat -n i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md | head -30Repository: unraid/docs
Length of output: 1439
🏁 Script executed:
# Check the English source file
cat -n docs/unraid-os/release-notes/6.12.14.md | head -30Repository: unraid/docs
Length of output: 1723
🏁 Script executed:
# Check if this escaping pattern is systematic across other i18n/ja files
rg -l '{/\\' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/ | head -5Repository: unraid/docs
Length of output: 134
🏁 Script executed:
# Count files in i18n/ja with this escaped anchor pattern
rg '{/\\\\\\* #' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/ | wc -lRepository: unraid/docs
Length of output: 160
🏁 Script executed:
# Check if the English source file has ANY heading anchors
grep -n '{/\*' docs/unraid-os/release-notes/6.12.14.mdRepository: unraid/docs
Length of output: 37
🏁 Script executed:
# Check other i18n/ja files to see if this is systematic
fd . i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/ --type f -x sh -c 'echo "File: {}"; grep -c "{/\\\\" {} 2>/dev/null || echo "0"' | head -20Repository: unraid/docs
Length of output: 942
🏁 Script executed:
# Check if English source files have heading anchors
find docs/unraid-os/release-notes/ -name "*.md" -type f -exec grep -l '{/\*' {} \; | head -5Repository: unraid/docs
Length of output: 37
🏁 Script executed:
# Get sample of actual anchor lines from Japanese translation
grep -h '{/\\' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md | head -3Repository: unraid/docs
Length of output: 167
🏁 Script executed:
# Check if English version of 6.12.3 has heading anchors
grep -h '{/\*' docs/unraid-os/release-notes/6.12.3.md | head -3Repository: unraid/docs
Length of output: 37
🏁 Script executed:
# Check what the escaped backslash actually renders as by looking at raw bytes
od -c i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md | grep -A 5 "u p g r"Repository: unraid/docs
Length of output: 95
🏁 Script executed:
# Check if English 6.12.14 source has ANY anchors at all (not just MDX comments)
grep -E '{#|/\*' docs/unraid-os/release-notes/6.12.14.mdRepository: unraid/docs
Length of output: 37
🏁 Script executed:
# Check a recent Japanese file to compare anchor syntax
head -30 i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdRepository: unraid/docs
Length of output: 1474
🏁 Script executed:
# Check the corresponding English file for 7.3.0
head -30 docs/unraid-os/release-notes/7.3.0.mdRepository: unraid/docs
Length of output: 2180
🏁 Script executed:
# Check if this is Crowdin adding anchors to Japanese files
# Look for a pattern: do all Japanese release notes have these, but English doesn't?
echo "=== Files with escaped anchors in i18n/ja ==="
find i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes -name "*.md" -type f -exec sh -c 'count=$(grep -c "{/\\\\" "$1" 2>/dev/null || echo 0); if [ "$count" -gt 0 ]; then echo "$1: $count"; fi' _ {} \; | wc -l
echo "=== Files with unescaped anchors in English source ==="
find docs/unraid-os/release-notes -name "*.md" -type f -exec sh -c 'count=$(grep -c "{/\*" "$1" 2>/dev/null || echo 0); if [ "$count" -gt 0 ]; then echo "$1: $count"; fi' _ {} \;Repository: unraid/docs
Length of output: 1770
🏁 Script executed:
# Verify: check if 6.12.14.md English has ANY version of anchors
cat docs/unraid-os/release-notes/6.12.14.md | grep -i -E '(`#upgrade`|#known|#rolling)' | head -10Repository: unraid/docs
Length of output: 237
🏁 Script executed:
# Cleaner check: how many Japanese files have these anchors vs English
echo "Japanese files with escaped anchors:"
find i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes -name "*.md" -type f | xargs grep -l '{/\\' 2>/dev/null | wc -l
echo "English files with any heading anchors:"
find docs/unraid-os/release-notes -name "*.md" -type f | xargs grep -l '{/\*' 2>/dev/null | wc -lRepository: unraid/docs
Length of output: 136
🏁 Script executed:
# Check if the learnings repo pattern applies - look for docusaurus config
find . -name "docusaurus.config.js" -o -name "docusaurus.config.ts" | head -1 | xargs cat | head -50Repository: unraid/docs
Length of output: 2336
Fix escaped heading anchor syntax across 29 Japanese translation files.
The escaped anchor syntax {/\* #upgrade-notes \*/} prevents MDX from parsing the comment, causing anchors to not be created and rendering as literal text in headings. Use the correct unescaped syntax: {/* #upgrade-notes */}.
This is a systematic issue affecting all 29 Japanese release note files in i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/. Each file must have its heading anchors corrected from:
{/\*#anchor-name\*/}→{/*#anchor-name*/}
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 the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md`
at line 3, Several Japanese release-note headings use the escaped anchor token
"{/\* `#anchor-name` \*/}" which MDX treats as literal text; replace each
occurrence with the correct MDX-safe comment anchor "{/* `#anchor-name` */}"
(e.g., change "{/\* `#upgrade-notes` \*/}" to "{/* `#upgrade-notes` */}") across all
29 Japanese release-note files so the anchors are parsed and created properly.
| [6.12.1](6.12.1.md) との差分 | ||
|
|
||
| ## アップグレードに関する注意事項 | ||
| ## アップグレードに関する注意事項 {/\* #upgrade-notes \*/} |
There was a problem hiding this comment.
Critical: Incorrect MDX anchor syntax - backslashes will break anchor functionality.
The heading anchors use escaped syntax {/\* #anchor \*/} which is incorrect for MDX. The backslashes prevent these from being parsed as MDX comments, causing the text to render literally instead of creating functional anchors.
As per coding guidelines, use the correct MDX comment syntax: {/* #anchor */} (without backslashes).
🐛 Correct anchor syntax
-## アップグレードに関する注意事項 {/\* `#upgrade-notes` \*/}
+## アップグレードに関する注意事項 {/* `#upgrade-notes` */}
-### 既知の問題 {/\* `#known-issues` \*/}
+### 既知の問題 {/* `#known-issues` */}
-### ロールバック {/\* `#rolling-back` \*/}
+### ロールバック {/* `#rolling-back` */}Also applies to: 7-7, 11-11
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md`
at line 5, Replace the incorrect escaped MDX comment anchors that use
backslashes (e.g. the heading "## アップグレードに関する注意事項 {/\* `#upgrade-notes` \*/}")
with proper MDX comment syntax so anchors work; specifically update occurrences
like "{/\* `#upgrade-notes` \*/}" (and the same pattern on the other flagged
headings) to use "{/* `#upgrade-notes` */}" (remove the backslashes) so the anchor
comments are parsed correctly.
| # バージョン 6.12.4 2023-08-31 | ||
|
|
||
| ## アップグレードに関する注意事項 | ||
| ## アップグレードに関する注意事項 {/\* #upgrade-notes \*/} |
There was a problem hiding this comment.
Critical: Incorrect MDX anchor syntax - backslashes will break anchor functionality.
The heading anchors use escaped syntax {/\* #anchor \*/} which is incorrect for MDX. The backslashes prevent these from being parsed as MDX comments, causing the text to render literally instead of creating functional anchors.
As per coding guidelines, use the correct MDX comment syntax: {/* #anchor */} (without backslashes).
🐛 Correct anchor syntax
-## アップグレードに関する注意事項 {/\* `#upgrade-notes` \*/}
+## アップグレードに関する注意事項 {/* `#upgrade-notes` */}
-### 既知の問題 {/\* `#known-issues` \*/}
+### 既知の問題 {/* `#known-issues` */}
-### ロールバック {/\* `#rolling-back` \*/}
+### ロールバック {/* `#rolling-back` */}
-## macvlan のコールトレースの修正 {/\* `#fix-for-macvlan-call-traces` \*/}
+## macvlan のコールトレースの修正 {/* `#fix-for-macvlan-call-traces` */}
-## システムドライバー ページ {/\* `#system-drivers-page` \*/}
+## システムドライバー ページ {/* `#system-drivers-page` */}Also applies to: 5-5, 9-9, 24-24, 68-68
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md`
at line 3, The MDX heading anchor uses incorrect escaped comment syntax "{/\*
`#upgrade-notes` \*/}" which renders literally; update the anchor to the proper
MDX comment form "{/* `#upgrade-notes` */}" so it becomes a functional anchor.
Locate the heading "## アップグレードに関する注意事項" and replace the escaped anchor token
with the correct one, and scan the same file for other similarly escaped anchors
(the other occurrences flagged in the review) and fix each by removing the
backslashes so they use "{/* ... */}".
| 手順ごとの説明は、[Unraid のアップグレード](../../unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx) を参照してください。[ライセンス](../../unraid-os/troubleshooting/licensing-faq.mdx#license-types--features) に関する質問はこちらですか? | ||
|
|
||
| ### 既知の問題 | ||
| ### 既知の問題 {/\* #known-issues \*/} |
There was a problem hiding this comment.
Critical: Incorrect MDX anchor syntax - backslashes will break anchor functionality.
The heading anchors use escaped syntax {/\* #anchor \*/} which is incorrect for MDX. The backslashes prevent these from being parsed as MDX comments, causing the text to render literally instead of creating functional anchors.
As per coding guidelines, use the correct MDX comment syntax: {/* #anchor */} (without backslashes).
🐛 Correct anchor syntax
-### 既知の問題 {/\* `#known-issues` \*/}
+### 既知の問題 {/* `#known-issues` */}
-### ロールバック {/\* `#rolling-back` \*/}
+### ロールバック {/* `#rolling-back` */}Also applies to: 13-13
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md`
at line 9, The MDX anchor comment on the "### 既知の問題" heading uses an incorrect
escaped form "{/\* `#known-issues` \*/}" which renders literally; replace it with
the correct MDX comment syntax "{/* `#known-issues` */}" (remove the backslashes).
Do the same fix for the other occurrence using "{/\* `#anchor` \*/}" → "{/*
`#anchor` */}" so anchors are parsed correctly.
| 手順については、[Unraid のアップグレード](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/) をご覧ください。[ライセンス](/unraid-os/troubleshooting/licensing-faq/) に関するご質問がありますか? | ||
|
|
||
| ### 既知の問題 | ||
| ### 既知の問題 {/\* #known-issues \*/} |
There was a problem hiding this comment.
Critical: Incorrect MDX anchor syntax - backslashes will break anchor functionality.
The heading anchors use escaped syntax {/\* #anchor \*/} which is incorrect for MDX. The backslashes prevent these from being parsed as MDX comments, causing the text to render literally instead of creating functional anchors.
As per coding guidelines, use the correct MDX comment syntax: {/* #anchor */} (without backslashes).
🐛 Correct anchor syntax
-### 既知の問題 {/\* `#known-issues` \*/}
+### 既知の問題 {/* `#known-issues` */}
-### ロールバック {/\* `#rolling-back` \*/}
+### ロールバック {/* `#rolling-back` */}Also applies to: 15-15
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md`
at line 11, The MDX anchor comment in the heading "### 既知の問題 {/\* `#known-issues`
\*/}" uses escaped backslashes which breaks anchor parsing; update the MDX
comment to the correct syntax by removing the backslashes so it reads {/*
`#known-issues` */}, and likewise fix the other occurrence of the same escaped
pattern (e.g., the similar anchor at the second occurrence) to use {/* `#anchor`
*/} form so anchors render correctly.
| # セキュリティの基本 | ||
|
|
||
| :::note[最小権限の原則] | ||
| :::note[Principle の最小権限 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Detect malformed admonition opener patterns in translated MDX docs (read-only).
rg -nP '^:::[A-Za-z]+\[[^\]]*$|^:::[A-Za-z]+\\\[' --type-add 'mdx:*.mdx' -tmdx i18nRepository: unraid/docs
Length of output: 37959
🏁 Script executed:
sed -n '1,15p;60,65p' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdxRepository: unraid/docs
Length of output: 692
Fix malformed admonition headers to avoid MDX parse failures.
Line 8 is missing a closing ] for the note title, and Line 62 uses an escaped bracket instead of a literal bracket.
Suggested fix
-:::note[Principle の最小権限
+:::note[最小権限の原則]
-:::note\[Example]
+:::note[Example]🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx`
at line 8, The MDX admonition header ":::note[Principle の最小権限" is malformed
(missing a closing ]) and later usage on line 62 uses an escaped bracket; fix by
adding the missing closing bracket to the note header so it reads
":::note[Principle の最小権限]" and replace any escaped bracket sequences (e.g.,
"\]") with a literal "]" so the admonition and any bracketed titles parse
correctly (search for the literal admonition start string ":::note[Principle
の最小権限" and the escaped "\]" occurrences to locate edits).
| 不適切なシャットダウンは、Unraid が %%array|array%% がシステムの電源が切れる前に正しく停止されなかったことを検出したときに発生します。この状況では、データの整合性を確保するため、次回の起動時に自動的に %%parity check|parity-check%% が実行される場合があります。 | ||
|
|
||
| :::important[不適切なシャットダウンを防ぐための推奨事項] | ||
| :::important[Recommendations 不適切なシャットダウンを防ぐため |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Detect malformed admonition headers missing a closing ']'
rg -nP '^:::(tip|note|info|warning|danger|important)\[[^\]]*$' --iglob '*.mdx'Repository: unraid/docs
Length of output: 7927
🏁 Script executed:
sed -n '10,20p' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx | cat -nRepository: unraid/docs
Length of output: 902
🏁 Script executed:
sed -n '10,35p' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx | cat -nRepository: unraid/docs
Length of output: 1732
Close the admonition title bracket to fix MDX parse failure.
Line 13 is missing the closing ] in the admonition header. Docusaurus admonition syntax requires :::type[Title] format to parse correctly.
Proposed fix
-:::important[Recommendations 不適切なシャットダウンを防ぐため
+:::important[Recommendations 不適切なシャットダウンを防ぐため]📝 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.
| :::important[Recommendations 不適切なシャットダウンを防ぐため | |
| :::important[Recommendations 不適切なシャットダウンを防ぐため] |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx`
at line 13, The MDX admonition header starting with
":::important[Recommendations 不適切なシャットダウンを防ぐため" is missing the closing bracket;
update the admonition header (the ":::important[...") to include the trailing
"]" so it conforms to the Docusaurus ":::type[Title]" admonition syntax (i.e.,
change the header to ":::important[Recommendations 不適切なシャットダウンを防ぐため]") to
resolve the MDX parse error in unclean-shutdowns.mdx.
| </Tabs> | ||
|
|
||
| :::important[サポートを確認する方法] | ||
| :::important[How サポートを確認するには |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify admonition title lines are syntactically closed with ']'
python - <<'PY'
from pathlib import Path
p = Path("i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx")
for i, line in enumerate(p.read_text(encoding="utf-8").splitlines(), start=1):
s = line.strip()
if s.startswith(":::") and "[" in s and not s.endswith("]"):
print(f"Potential malformed admonition title at Line {i}: {s}")
PYRepository: unraid/docs
Length of output: 133
🏁 Script executed:
cat -n i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx | sed -n '55,75p;95,120p;130,150p;180,210p'Repository: unraid/docs
Length of output: 4374
🏁 Script executed:
rg -n "#要件|#requirements" i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxRepository: unraid/docs
Length of output: 37
🏁 Script executed:
rg -r 'overview-and-system-prep.*#(要件|requirements)' --glob='**/*.mdx' --glob='**/*.md'Repository: unraid/docs
Length of output: 451
🏁 Script executed:
rg '#要件|#requirements' --glob='**/*.mdx' --glob='**/*.md'Repository: unraid/docs
Length of output: 1639
Fix critical MDX syntax errors and broken cross-file links.
Line 110 has a missing closing bracket that breaks MDX parsing, and the requirements heading (Line 61) lost its anchor without preserving it as an MDX-safe comment, breaking links from other documentation files.
Proposed fixes
Line 110 (malformed admonition):
-:::important[How サポートを確認するには
+:::important[サポートを確認する方法]Line 61 (missing stable anchor):
-## 要件
+## 要件 {/* `#requirements` */}The #requirements anchor is referenced by cross-file links in vm-conversion-and-migration.mdx across multiple language versions. The MDX-safe comment syntax preserves backward compatibility.
Additionally, Lines 135 and 143 contain mixed English-Japanese admonition labels ([General ヒント] and [Always 変更]) that degrade localization quality. Consider translating labels fully into Japanese.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx`
at line 110, The MDX broken parsing is caused by a malformed admonition open
token ":::important[How サポートを確認するには" (missing closing bracket) — fix that
admonition by closing the bracket and ensuring the admonition block is properly
closed; restore the stable anchor for the Requirements heading by inserting an
MDX-safe comment anchor (e.g. <!-- `#requirements` -->) immediately adjacent to
the "requirements" heading (the heading referenced as "#requirements"); and
replace mixed-language admonition labels "General ヒント" and "Always 変更" with
fully Japanese labels (e.g., "一般的なヒント" and "常に変更") to preserve localization
consistency.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
unraid-docs | e0c5878 | Apr 16 2026, 02:56 PM |
1 participant
Summary by CodeRabbit