Conversation
📝 WalkthroughWalkthroughThis pull request updates documentation files across multiple localized versions (German, Spanish, French, Japanese, and Chinese). Changes include converting MDX heading anchor syntax from Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~35 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 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: 28
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/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx (1)
113-134:⚠️ Potential issue | 🟠 MajorConsolidate the duplicated “VM を設定する” sections.
There are two consecutive setup sections with overlapping instructions and nearly identical titles, which makes the flow ambiguous for readers. Please merge them into one section (or clearly differentiate titles and non-overlapping scope).
✂️ Suggested consolidation (example)
-<details> - <summary><strong>3. VM を設定する</strong> - クリックして展開/折りたたみ</summary> - ... -</details> - -<details> - <summary><strong>4. VM を設定する</strong> - クリックして展開/折りたたみ</summary> +<details> + <summary><strong>3. VM を設定する</strong> - クリックして展開/折りたたみ</summary> ... </details>🤖 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` around lines 113 - 134, Merge the two consecutive "4. VM を設定する" collapsible sections into a single consolidated details block titled "4. VM を設定する" that contains the non-duplicated, ordered steps for configuring the VM; keep and merge unique steps involving %%VM|vm%% (WebGUI, Settings → Identification, Display settings, %%SMB|samba%% Workgroup settings, UPS passthrough, starting %%array|array%%, Community Applications, Tools → Update OS), remove repeated sentences, reconcile numbering so the list is sequential and coherent, and ensure any VM-specific placeholders (%%VM|vm%%, %%WebGUI|web-gui%%, %%SMB|samba%%, %%array|array%%) remain intact and referenced once.
🟠 Major comments (15)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx-103-103 (1)
103-103:⚠️ Potential issue | 🟠 MajorRestore the stable anchor to keep existing in-page links working.
Line 103 removed the explicit anchor, but Line 84 still links to
#adding-disks-to-a-pool. The target is no longer defined anywhere in the document, breaking the in-page reference.Suggested fix
-## プールへのディスク追加 +## プールへのディスク追加 {/* `#adding-disks-to-a-pool` */}🤖 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` at line 103, The anchor target referenced by in-page links (`#adding-disks-to-a-pool`) was removed when the heading "## プールへのディスク追加" was changed; restore the stable anchor by re-adding the explicit anchor/id to that heading (for example by appending the MDX/Markdown id `{`#adding-disks-to-a-pool`}` or adding an HTML anchor tag immediately before the "## プールへのディスク追加" heading) so existing links still resolve.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx-35-35 (1)
35-35:⚠️ Potential issue | 🟠 MajorUse standard admonition syntax without bracket escaping on line 35, and localize the title to Japanese.
The escaped bracket
\[Example]is non-standard in Docusaurus admonition syntax and may cause parsing issues. The title should also be translated to match this Japanese documentation file.Suggested fix
-:::info\[Example] +:::info[例]🤖 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 35, Replace the non-standard escaped admonition marker `:::info\[Example]` with the standard Docusaurus admonition syntax and translate the title into Japanese; e.g., change the line containing `:::info\[Example]` to use `:::info[例]` (or `:::info[例]` if you prefer the short form) so the admonition parses correctly and the title is localized.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md-9-13 (1)
9-13:⚠️ Potential issue | 🟠 MajorCorrect escaped heading anchors to MDX-safe comment anchors.
Line 9 and Line 13 should use unescaped comment anchors. The current escaped form can prevent anchor parsing.
Suggested fix
-### 既知の問題 {/\* `#known-issues` \*/} +### 既知の問題 {/* `#known-issues` */} -### ロールバック {/\* `#rolling-back` \*/} +### ロールバック {/* `#rolling-back` */}Based on learnings: In translated MDX/Markdown docs, explicit heading anchors should use
### 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/7.1.2.md` around lines 9 - 13, Replace the escaped MDX comment anchors on the headings so they are MDX-safe: locate the headings "### 既知の問題 {/\* `#known-issues` \*/}" and "### ロールバック {/\* `#rolling-back` \*/}" and change their anchors to the unescaped MDX comment form (e.g., "### 既知の問題 {/* `#known-issues` */}" and "### ロールバック {/* `#rolling-back` */}") so the explicit heading anchors parse correctly in MDX.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.md-7-11 (1)
7-11:⚠️ Potential issue | 🟠 MajorFix escaped anchor comment syntax in both headings.
Line 7 and Line 11 use escaped comment text (
{/\* ... \*/}), which can break stable anchor generation in MDX. Use the unescaped MDX-safe heading comment form.Suggested fix
-### 既知の問題 {/\* `#known-issues` \*/} +### 既知の問題 {/* `#known-issues` */} -### ロールバック {/\* `#rolling-back` \*/} +### ロールバック {/* `#rolling-back` */}As per coding guidelines: For explicit heading anchors in MDX, prefer
### 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/7.1.4.md` around lines 7 - 11, Replace the escaped comment syntax `{/\* ... \*/}` used in the headings "### 既知の問題 {/\* `#known-issues` \*/}" and "### ロールバック {/\* `#rolling-back` \*/}" with the MDX-safe unescaped form `{/* `#stable-anchor` */}` so anchors are generated reliably; locate the two heading lines (the "既知の問題" and "ロールバック" headings) and change their trailing comment tokens to `{/* `#known-issues` */}` and `{/* `#rolling-back` */}` respectively.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md-7-12 (1)
7-12:⚠️ Potential issue | 🟠 MajorUse MDX-safe heading anchors without escaping.
Line 7 and Line 12 currently use
{/\* ... \*/}. This should be{/* ... */}so anchors are parsed correctly and remain stable.Suggested fix
-### 既知の問題 {/\* `#known-issues` \*/} +### 既知の問題 {/* `#known-issues` */} -### ロールバック {/\* `#rolling-back` \*/} +### ロールバック {/* `#rolling-back` */}As per coding guidelines: For explicit heading anchors in MDX, prefer
### 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/7.1.3.md` around lines 7 - 12, The MDX heading anchors on the headings "### 既知の問題" and "### ロールバック" use escaped comment syntax `{/\* `#known-issues` \*/}` and `{/\* `#rolling-back` \*/}` which prevents proper anchor parsing; update those to use MDX-safe anchor comments with a leading space like ` {/* `#known-issues` */}` and ` {/* `#rolling-back` */}` respectively so the anchors are parsed and remain stable.i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx-23-23 (1)
23-23:⚠️ Potential issue | 🟠 MajorUse MDX-safe comment anchor syntax instead of classic heading ID.
Line 23 currently uses
{#data-collection-and-privacy}. Please switch to{/*#data-collection-and-privacy*/}to match translated MDX import expectations.As per coding guidelines: Do not use classic heading IDs like `### Heading {`#stable-anchor`}` in translated MDX files; Crowdin's MDX import parser can reject them.🛠️ Proposed fix
-## Datenerfassung und Datenschutz {`#data-collection-and-privacy`} +## Datenerfassung und Datenschutz {/* `#data-collection-and-privacy` */}🤖 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` at line 23, Replace the classic heading ID on the "Datenerfassung und Datenschutz" heading—currently using {`#data-collection-and-privacy`}—with MDX-safe comment-anchor syntax: change the trailing anchor to {/* `#data-collection-and-privacy` */} so the translated MDX import/parser accepts the file.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md-5-5 (1)
5-5:⚠️ Potential issue | 🟠 MajorRemove backslash escapes from anchor comment syntax on lines 5, 7, and 11.
The escaped syntax
{/\*#anchor\*/}will not be processed by Docusaurus—use{/*#anchor*/}instead. Without this fix, the anchor links will not function.🤖 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.3.md` at line 5, Lines contain escaped comment anchor syntax like {/\* `#upgrade-notes` \*/} (and similar on lines 7 and 11); replace each occurrence with the correct Docusaurus anchor comment syntax {/* `#upgrade-notes` */} (and corresponding anchor names on lines 7 and 11) so the anchors render and links work; locate the exact tokens `{/\* ... \*/}` in the file and change the backslash-escaped form to `{/* ... */}` for each anchor comment.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md-3-3 (1)
3-3:⚠️ Potential issue | 🟠 MajorSwitch these headings from escaped
{/\* #... \*/}to proper MDX comment syntax{/* #... */}.The escaped backslashes on lines 3, 7, and 42 violate the project's MDX anchor guidelines. Docusaurus requires literal forward slashes in the comment syntax, not escaped ones.
🤖 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.12.md` at line 3, Replace the escaped MDX comment anchors that use backslashes (e.g. "{/\* `#upgrade-notes` \*/}") with proper MDX comment syntax using literal forward slashes and asterisks ("{/* `#upgrade-notes` */}"); update every occurrence including the heading "## アップグレードに関する注意事項" and the other two headings that currently contain "{/\* #... \*/}" so they become "{/* #... */}" to comply with Docusaurus MDX anchor guidelines.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md-9-9 (1)
9-9:⚠️ Potential issue | 🟠 MajorFix escaped anchor syntax in section headings.
Lines 9 and 15 use escaped asterisks in the MDX comment syntax (
{/\*#anchor\*/}), which breaks parsing. Change to the correct form:{/*#anchor*/}.
- Line 9:
### 既知の問題 {/*#known-issues*/}- Line 15:
### ロールバック {/*#rolling-back*/}🤖 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.1.md` at line 9, The MDX comment anchor syntax is escaped incorrectly in the headings; update the two headings that use `{/\* ... \*/}` to the correct `{/* ... */}` form — specifically change the heading "### 既知の問題 {/\* `#known-issues` \*/}" to "### 既知の問題 {/* `#known-issues` */}" and the heading "### ロールバック {/\* `#rolling-back` \*/}" to "### ロールバック {/* `#rolling-back` */}" so the anchors parse correctly.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md-11-11 (1)
11-11:⚠️ Potential issue | 🟠 MajorRemove backslashes from heading anchor comments.
Lines 11 and 15 use escaped asterisks (
{/\*#known-issues\*/}and{/\*#rolling-back\*/}), but should use the proper MDX-safe comment syntax:{/*#known-issues*/}and{/*#rolling-back*/}. The escaped variant breaks the anchor functionality and is not aligned with repository standards for translated MDX files.🤖 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` at line 11, Replace the escaped asterisk MDX comment sequences `{/\* `#known-issues` \*/}` and `{/\* `#rolling-back` \*/}` with the MDX-safe comment syntax `{/* `#known-issues` */}` and `{/* `#rolling-back` */}` respectively so the anchor comments work correctly; search for the exact strings `{/\* `#known-issues` \*/}` and `{/\* `#rolling-back` \*/}` in the file and update them to `{/* `#known-issues` */}` and `{/* `#rolling-back` */}`.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md-3-3 (1)
3-3:⚠️ Potential issue | 🟠 MajorRemove backslash escapes from heading anchor comments.
Lines 3, 14, and 49 use escaped syntax
{/\*#anchor\*/}instead of the correct MDX-safe comment form{/*#anchor*/}. The literal backslashes must be removed to comply with Docusaurus's anchor comment syntax for translated documents.Lines affected
- Line 3:
## アップグレードに関する注意事項 {/\*#upgrade-notes\*/}→## アップグレードに関する注意事項 {/*#upgrade-notes*/}- Line 14:
### 既知の問題 {/\*#known-issues\*/}→### 既知の問題 {/*#known-issues*/}- Line 49:
### ロールバック {/\*#rolling-back\*/}→### ロールバック {/*#rolling-back*/}🤖 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.8.md` at line 3, Remove the literal backslashes from the MDX-style anchor comments so they use the Docusaurus-safe form; replace `{/\* `#upgrade-notes` \*/}`, `{/\* `#known-issues` \*/}`, and `{/\* `#rolling-back` \*/}` with `{/* `#upgrade-notes` */}`, `{/* `#known-issues` */}`, and `{/* `#rolling-back` */}` respectively in the headings "## アップグレードに関する注意事項", "### 既知の問題", and "### ロールバック" to ensure valid anchor comment syntax.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md-5-5 (1)
5-5:⚠️ Potential issue | 🟠 MajorFix MDX anchor syntax on headings—remove backslash escaping.
Lines 5, 7, and 11 use
{/\*#anchor\*/}(escaped) instead of the required{/*#anchor*/}(unescaped). The escaped form breaks anchor generation in Docusaurus and conflicts with Crowdin's MDX parser expectations for translated docs.Suggested fix
-## アップグレードに関する注意事項 {/\* `#upgrade-notes` \*/} +## アップグレードに関する注意事項 {/* `#upgrade-notes` */} -### 既知の問題 {/\* `#known-issues` \*/} +### 既知の問題 {/* `#known-issues` */} -### ロールバック {/\* `#rolling-back` \*/} +### ロールバック {/* `#rolling-back` */}🤖 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.1.md` at line 5, The MDX anchor comments on the headings are escaped (e.g., "## アップグレードに関する注意事項 {/\* `#upgrade-notes` \*/}") which prevents Docusaurus/Crowdin from generating anchors; locate the three headings that use the escaped pattern (the lines containing "{/\* `#upgrade-notes` \*/}" and the other two similar occurrences) and replace the escaped comment syntax with the correct unescaped MDX comment form "{/* `#anchor` */}" (i.e., remove the backslashes so each "{/\* ... \*/}" becomes "{/* ... */}"), preserving the anchor names exactly.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md-3-3 (1)
3-3:⚠️ Potential issue | 🟠 MajorFix escaped anchor syntax in headings.
Lines 3, 7, and 15 use escaped curly braces and asterisks in anchor comments. Replace with MDX-safe syntax:
{/*#anchor-name*/}(without backslash escapes). Escaped syntax breaks anchor parsing in translated MDX files.🤖 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.5.md` at line 3, Replace the MDX-escaped anchor comments that use backslash-escaped curly braces and asterisks (e.g., "{/\* `#upgrade-notes` \*/}") with MDX-safe comments using plain braces and asterisks (e.g., "{/* `#upgrade-notes` */}") wherever the headings contain anchors like "#upgrade-notes", "#known-issues" and "#other-changes" so the anchor parsing works correctly in translated MDX files.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md-3-3 (1)
3-3:⚠️ Potential issue | 🟠 MajorReplace escaped anchor syntax with MDX-safe comment syntax.
Lines 3, 8, and 50 currently use escaped anchor markers (
{/\*#anchor\*/}). Switch to the proper Docusaurus MDX-safe syntax:{/*#anchor*/}(without the escaping).Example fix for line 3:
Show diff
-## アップグレードに関する注意事項 {/\* `#upgrade-notes` \*/} +## アップグレードに関する注意事項 {/* `#upgrade-notes` */}This applies to translated MDX files where Crowdin integration requires the proper comment syntax to preserve anchor stability across localization cycles.
Also applies to: lines 8, 50
🤖 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, Replace the escaped MDX comment-style anchors that use "{/\* ... \*/}" with the Docusaurus-safe "{/* ... */}" syntax throughout the document; specifically update the anchor for "#upgrade-notes" (currently "{/\* `#upgrade-notes` \*/}") and the other two escaped anchors referenced in the review (lines 8 and 50) so they become "{/* `#anchor` */}" (preserving the same anchor names) to ensure Crowdin/localization stability.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md-9-9 (1)
9-9:⚠️ Potential issue | 🟠 MajorEnglish text in Chinese localization file.
Line 9 contains English text in a Chinese (zh) locale file. This should be translated to maintain consistency with the locale.
Expected Chinese translation similar to other Chinese release notes files.
🤖 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, The line containing 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/)?" should be replaced with a Chinese translation while keeping the Markdown links intact; update that sentence to something like: "有关逐步说明，请参阅 [升级 Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/)。有关许可证的问题，请参阅 [许可常见问题](/unraid-os/troubleshooting/licensing-faq/)。" and ensure the punctuation and link targets remain unchanged in the file (the sentence in this diff is the target to edit).
🟡 Minor comments (20)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx-68-70 (1)
68-70:⚠️ Potential issue | 🟡 MinorKeep captions/alt text localized and fix the second image alt mismatch.
Line 68/70 and Line 74/76 switched to English in a Japanese page, and Line 74’s alt text describes “distribution” while the figure is “access”. This is a small i18n + accessibility quality regression.
Suggested patch
- <img src="/img/User_shares_-_distribution@500px.png" alt="User shares distribution example" /> + <img src="/img/User_shares_-_distribution@500px.png" alt="ユーザー共有の分布例" /> - <figcaption>User shares - Distribution</figcaption> + <figcaption>ユーザー共有 - 分布</figcaption> - <img src="/img/User_shares_-_access@500px.png" alt="User shares distribution example larger" /> + <img src="/img/User_shares_-_access@500px.png" alt="ユーザー共有のアクセス例" /> - <figcaption>User shares - Access</figcaption> + <figcaption>ユーザー共有 - アクセス</figcaption>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, The image captions and alt text are in English and the second image has an alt/description mismatch; update the two img alt attributes and their figcaption texts to Japanese and correct the second image's alt to match the actual figure. Specifically, replace the English caption/alt for the distribution image (src "/img/User_shares_-_distribution@500px.png", figcaption "User shares - Distribution") with a Japanese caption/alt (e.g., "ユーザー共有 - 配布"), and for the access image (the block around lines 74–76) ensure its alt and figcaption reflect "ユーザー共有 - アクセス" so the alt text describes the access figure correctly.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx-84-84 (1)
84-84:⚠️ Potential issue | 🟡 MinorKeep language consistent in the Japanese locale page.
Line 84 is currently English in an otherwise Japanese document, which hurts readability and localization quality.
💡 Suggested 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 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 while preserving the placeholder tokens %%array|array%% and %%cache|cache%% and the example path `/dev/sdj1`; locate the exact string in the file (the sentence containing "non-%%array|array%%" / "%%cache|cache%%-only") and substitute it with a concise Japanese sentence that conveys the same meaning and keeps formatting and backticks intact.i18n/ja/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx-58-58 (1)
58-58:⚠️ Potential issue | 🟡 MinorFix note title typo in Line 58 (extra
[character).The title currently renders as
Server [コンテキストが必要, which looks accidental and reduces readability.Suggested 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, There's a typo in the MDX note title where an extra "[" is present in the note header (currently reads ":::note[Server [コンテキストが必要"); update the note block header to remove the stray bracket so it reads ":::note[Server コンテキストが必要]" (or the intended title) ensuring the closing bracket remains; locate the note block containing the string "Server [コンテキストが必要" and correct the title text.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 | 🟡 Minor重複している案内文を1行にしてください。
Line 69 の文が Line 70 と同一で、同じ説明が連続表示されています。どちらか1行だけ残すのがよいです。
✂️ Suggested edit
- `X` は、削除するデータディスクの番号に置き換えてください。 `X` は、削除するデータディスクの番号に置き換えてください。🤖 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, The sentence "`X` は、削除するデータディスクの番号に置き換えてください。" appears twice consecutively; remove one of the duplicate lines so only a single instance remains, preserving the surrounding punctuation and spacing and keeping the sentence in place under the same paragraph where it currently appears.i18n/fr/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 | 🟡 MinorSupprimer la consigne en doublon.
Le texte ajouté en Line 69 est le même que celui déjà présent en Line 70. Garder une seule occurrence évite la répétition.
✂️ Suggested edit
- 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.🤖 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 - 70, The file contains a duplicated sentence "Remplacez `X` par le numéro spécifique du disque de données que vous supprimez." appearing twice; remove the redundant occurrence so the sentence appears only once (keep one instance and delete the other) to eliminate the duplicate text.i18n/de/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 | 🟡 MinorDoppelte Anweisung entfernen.
Line 69 und Line 70 enthalten denselben Hinweis, dadurch erscheint die Anleitung doppelt. Bitte nur eine Zeile behalten.
✂️ Suggested edit
- 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.🤖 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 - 70, Die beiden identischen Sätze "Ersetzen Sie `X` durch die spezifische Nummer der Datenfestplatte, die Sie entfernen möchten." sind doppelt vorhanden; entferne eine der beiden Duplikatzeilen in der Datei so dass nur eine Kopie des Hinweises verbleibt (suche nach dieser genauen Zeichenfolge und lösche entweder die Zeile im Block, der die zweite Instanz enthält, oder die überflüssige Wiederholung innerhalb des Abschnitts).i18n/es/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 | 🟡 MinorEliminar la línea de instrucción duplicada.
La indicación en Line 69 es idéntica a la de Line 70, por lo que queda duplicada de forma consecutiva. Mantén solo una.
✂️ Suggested edit
- 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.🤖 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 - 70, Remove the duplicated instruction that reads "Reemplace `X` con el número específico del disco de datos que está eliminando." and keep a single instance; locate the repeated string in the section about removing disks from the array (the consecutive duplicate lines) and delete one of them so the sentence appears only once.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 | 🟡 MinorRevert to fully German translation.
The note title mixes English and German:
Benefits des Ruhezustands. In a German localization file, the title should be fully translated. The original textVorteile des Ruhezustandswas correct.🌐 Proposed fix to restore German translation
-:::note[Benefits des Ruhezustands] +:::note[Vorteile des Ruhezustands]🤖 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 note title is mixed English/German (:::note[Benefits des Ruhezustands]); replace it with the fully German title by changing the note declaration to :::note[Vorteile des Ruhezustands] so the localization is correct (locate the :::note[...] token in windows-on-a-vm.mdx and update the bracketed text).i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx-110-110 (1)
110-110:⚠️ Potential issue | 🟡 MinorVerify mixed-language callout title.
The admonition title mixes English and Japanese:
How サポートを確認するには. This creates redundancy since the Japanese phrase already contains the meaning of "how." In Japanese documentation, callout titles are typically either fully Japanese or fully English for consistency. The originalサポートを確認する方法was fully Japanese.This may be a Crowdin translation artifact. Please verify whether this mixed-language approach is intentional or if the title should be either:
- Fully Japanese:
サポートを確認する方法orサポートを確認するには- Fully English:
How to Confirm Support🤖 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 admonition title string ":::important[How サポートを確認するには" mixes English and Japanese; update the callout title in this file to be language-consistent by replacing "How サポートを確認するには" with a fully Japanese title (e.g., "サポートを確認する方法" or "サポートを確認するには") or a fully English title ("How to Confirm Support"), ensuring the change is made where the admonition is declared (the ":::important[...]" line).i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx-143-143 (1)
143-143:⚠️ Potential issue | 🟡 MinorVerify mixed-language callout title.
The admonition title mixes English and Japanese:
Always 変更. This is grammatically awkward (English adverb + Japanese noun) and less clear than the original変更に関する注意(Note about changes).Please verify whether this should be:
- Fully Japanese:
変更に関する注意or常に変更を確認- Fully English:
Always ChangingorNote About Changes🤖 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 143, The admonition title currently reads :::info[Always 変更], mixing English and Japanese; replace that token with a consistent language version (e.g., :::info[変更に関する注意] for full Japanese or :::info[Note About Changes] for full English) and ensure any other similar admonitions in the same document use the same language choice; update the single token :::info[Always 変更] accordingly (and adjust surrounding text if needed to match the chosen language).i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx-135-135 (1)
135-135:⚠️ Potential issue | 🟡 MinorVerify mixed-language callout title.
The admonition title mixes English and Japanese:
General ヒント. The original一般的なヒントwas fully Japanese. This inconsistent approach may confuse readers.Please verify whether this should be:
- Fully Japanese:
一般的なヒント- Fully English:
General Tips🤖 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 135, The admonition title currently reads "::tip[General ヒント]" which mixes English and Japanese; confirm the intended language and replace that title with a consistent translation (either fully Japanese "一般的なヒント" or fully English "General Tips") in the admonition declaration (the "::tip[...]" token) so the callout title is language-consistent across the document.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 | 🟡 MinorKeep admonition titles fully Japanese for locale consistency.
Lines [92], [394], and [404] introduce English/mixed labels in a Japanese page.
Suggested 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, The admonition titles in this Japanese page use English/mixed text (e.g., the admonition token :::important[Initial setup requirements] and similar admonitions at the other occurrences), so replace those bracketed titles with fully Japanese strings to keep locale consistency; locate the admonition instances (the :::important[...] blocks at the shown positions and the other two occurrences) and update the bracketed text to appropriate Japanese translations while preserving the admonition syntax and spacing.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 | 🟡 MinorLocalize the new Exit-Node section text for DE docs.
Lines [77] and [79] are English/mixed language in a German page.
Suggested 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 Nutzer, die verschlüsselten ausgehenden Traffic ohne die Komplexität klassischer %%VPN|vpn-tunnel%% 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 English/mixed-language sentence in the "Exit-Node" section (the paragraph containing "%%Tailscale|tailscale%% exit nodes offer a secure and modern way..." and the similar line referenced at 79) needs to be translated/localized into German; replace the English text with an equivalent German translation that preserves the token placeholders (e.g., %%Tailscale|tailscale%%, %%Tailnet|tailnet%%, %%VPN|vpn-tunnel%%) and the meaning about routing outgoing traffic, encrypted outgoing traffic, and simplicity compared to traditional VPNs so the DE docs are fully localized.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx-33-33 (1)
33-33:⚠️ Potential issue | 🟡 MinorLine [33] is not localized for the Japanese page.
This new paragraph is English and should be translated for JA doc consistency.
🤖 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, The paragraph at line 33 is still in English; replace it with a natural Japanese translation while preserving the special localization tokens (e.g., %%ZFS|zfs%%, %%array|array%%, %%parity|parity%%) and sentence meaning: explain that Unraid supports %%ZFS|zfs%% for any storage pool, that you can create or import a %%ZFS|zfs%% pool, and describe the hybrid option of adding a %%ZFS|zfs%%-formatted disk directly to the Unraid %%array|array%% (not a pool) to combine %%ZFS|zfs%% features with Unraid’s %%parity|parity%% protection, all in Japanese.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 | 🟡 MinorLine [169] is untranslated in a Japanese page.
This paragraph should be localized to match the rest of the document.
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 台取り付けた後はそこから起動できなくなる可能性があります。可能であれば、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, Replace the untranslated English sentence "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." with a Japanese localization; for example use: 「多くのマザーボードはブートデバイスの選択を最大12台のハードドライブに制限しています。USBフラッシュドライブがハードドライブとして認識されると、物理ドライブを12台インストールした後にUSBから起動できなくなる可能性があります。可能であればBIOSでフラッシュドライブをリムーバブルデバイスとして扱うよう設定してください。」; ensure the replacement is saved in UTF-8 and matches the surrounding document tone and punctuation in deploy-and-configure-unraid-os.mdx.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx-79-80 (1)
79-80:⚠️ Potential issue | 🟡 MinorRemove duplicated Windows subsection label.
Line 79 repeats the same label already present at Line 77, so this creates redundant content in the rendered page.
Suggested fix
-**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 79 - 80, Remove the duplicated subsection heading "Windows 7 以降:" so only one occurrence remains; locate the repeated heading near the Windows subsection in the create-your-bootable-media.mdx content and delete the second instance (the duplicate), leaving the original heading and its content intact to avoid redundant rendering.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-37-38 (1)
37-38:⚠️ Potential issue | 🟡 MinorRemove duplicated FAQ lines in this section.
Line 37 repeats the previous controller guidance, and Line 57 repeats guidance already present later in the same block. This creates visible redundancy in the German FAQ flow.
✂️ Suggested cleanup
-Ü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. @@ -If you're uncertain about a drive's health, you can share your %%SMART|smart%% data in the [General Support forum](https://forums.unraid.net/forum/55-general-support/) for assistance from the community.Also applies to: 57-57
🤖 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, The German FAQ contains duplicated guidance lines—remove the repeated sentence beginning "Ü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." (the repeated controller guidance) and the other duplicated guidance later in the same block so the section only contains one instance of that controller recommendation; update surrounding spacing/punctuation so the paragraph reads cleanly and retains the reference link to the Empfohlene Controller-Thread.i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx-96-97 (1)
96-97:⚠️ Potential issue | 🟡 MinorClean up accidental duplicated lines and heading block.
Line 96 duplicates “Dann:”, Line 104 duplicates the internal-boot FAQ sentence, and Lines 124/126 duplicate content that appears again immediately below.
✂️ Suggested cleanup
-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/). @@ -### Richtlinie für sensible Daten - -Um Ihre Privatsphäre zu schützen, werden die folgenden **niemals** in Cloud-Backups gespeichert:Also applies to: 104-105, 124-126
🤖 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 96 - 97, Remove the accidental duplicated content: delete the extra standalone "Dann:" line, remove the repeated internal-boot FAQ sentence (the duplicated sentence containing "internal-boot" / the FAQ wording), and remove the duplicated block that appears twice around the middle of the document (the content repeated immediately below lines 124/126). Locate these exact duplicated text fragments ("Dann:", the internal-boot FAQ sentence, and the repeated paragraph block) and keep only a single instance of each so the MDX no longer contains repeated headings or sentences.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx-54-54 (1)
54-54:⚠️ Potential issue | 🟡 MinorKeep locale language consistent in Japanese docs.
Lines 54, 64, and 68 switch to English inside a Japanese page. Please translate these updated strings to Japanese to avoid mixed-language UX.
Also applies to: 64-64, 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/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx` at line 54, The Japanese doc contains English phrases in the sentence referencing %%Mover|mover%% and %%syslog|syslog%% and the menu path "Settings → Scheduler → Mover Settings"; replace that English sentence with a fully Japanese translation while preserving the interpolation tokens (%%Mover|mover%%, %%syslog|syslog%%) and emphasis markup (*** ... ***)—for example translate the menu path to "設定 → スケジューラ → ムーバー設定" and convert the surrounding explanatory text into natural Japanese so the page remains consistently Japanese (apply the same translation fixes to the other occurrences that use the same tokens).i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx-11-11 (1)
11-11:⚠️ Potential issue | 🟡 MinorPlease normalize language consistency for the zh locale.
These updated lines introduce English headings/body text in a Simplified Chinese page. Keep terminology in one locale (or intentionally bilingual everywhere) to avoid inconsistent UX.
Also applies to: 33-33, 129-129, 191-191, 351-351, 378-378
🤖 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/advanced-configurations/optimize-storage/zfs-storage.mdx` at line 11, The header snippet contains mixed-language text (":::important[Special 谢谢]") breaking zh locale consistency; update this and the other similar tokens to be fully Chinese (e.g., replace "Special" with "特别" or a consistent Chinese phrase) or make a deliberate bilingual pattern across the document; search for occurrences of the token pattern ":::important[...]" and other English headings/body text referenced in the review and convert them to the chosen consistent Chinese wording (or apply the agreed bilingual format) so all instances (including the other mentioned occurrences) match the zh locale.
🧹 Nitpick comments (2)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx (2)
72-72: Mixed-language admonition title typo (Line 72).
When y por qué...appears to be an accidental English/Spanish mix and should be localized consistently.Suggested fix
-:::important[When y por qué probar la velocidad] +:::important[Cuándo y por qué probar la velocidad]🤖 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 72, The admonition title contains mixed English/Spanish text in the doc admonition token :::important[When y por qué probar la velocidad]; update that token to a fully Spanish title (for example :::important[Por qué y cuándo probar la velocidad] or another equivalent Spanish phrasing) so the admonition title is consistently localized; edit the admonition header string inside the file to replace "When y por qué probar la velocidad" with the chosen Spanish text.
62-62: Untranslated English paragraph in Spanish doc (Line 62).This line is fully in English inside an
i18n/espage, which breaks localization consistency for users.Suggested fix
-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. +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 diagnosticar problemas específicos relacionados con %%Mover|mover%%, ya que puede revelar rutas y nombres de archivos.🤖 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 untranslated English paragraph with a Spanish translation while preserving the tokens and formatting (%%Mover|mover%%, %%syslog|syslog%% and the bold/arrow markup ***Settings → Scheduler → Mover Settings***); for example: "Por defecto, los diagnósticos se anonimizarán automáticamente. Si habilitas el registro de %%Mover|mover%% en ***Settings → Scheduler → Mover Settings***, el %%syslog|syslog%% incluirá detalles sobre los archivos que procesan los %%Mover|mover%%; lo recomendable es activar el registro del %%Mover|mover%% solo cuando se solucione un problema específico del %%Mover|mover%%, ya que puede revelar rutas y nombres de archivo." Ensure placeholders and markup remain unchanged and run the i18n build/lint to verify no localization keys or formatting were broken.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 25c43875-243d-4d50-9291-40f4d9863b96
📒 Files selected for processing (69)
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdxi18n/de/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/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdxi18n/es/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/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdxi18n/fr/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-account/redeem-activation-code.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.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/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.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.1.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.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/6.12.8.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.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/cache-pools.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
💤 Files with no reviewable changes (4)
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
| 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/)? | ||
|
|
||
| ### Bekannte Probleme {/* #known-issues */} | ||
| ### Bekannte Probleme {#known-issues} |
There was a problem hiding this comment.
Critical: Classic heading ID syntax forbidden in translated MDX files.
The syntax {#known-issues} and {#rolling-back} violates the coding guidelines for translated documentation. Crowdin's MDX import parser can reject classic heading IDs in translated files.
🔧 Proposed fix
-### Bekannte Probleme {`#known-issues`}
+### Bekannte Probleme {/* `#known-issues` */}-### Rückschritte {`#rolling-back`}
+### Rückschritte {/* `#rolling-back` */}As per coding guidelines: "Do not use classic heading IDs like ### Heading {#stable-anchor} in translated MDX files; Crowdin's MDX import parser can reject them"
Also applies to: 15-15
🤖 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 11, Remove the classic heading ID syntax used in the translated MDX
(e.g., the `{`#known-issues`}` and `{`#rolling-back`}` tokens) because Crowdin's MDX
import rejects them; update the headings to plain Markdown headings (e.g., "###
Bekannte Probleme" without `{#...}`) and, if an anchor is required internally,
replace with a supported approach (such as using a translated explicit HTML
anchor or Docusaurus-compatible slug usage) and verify no other occurrences of
`{#...}` remain in the file (search for `{`#known-issues`}` and `{`#rolling-back`}`
and remove or convert them).
| 7. Bestehende Dateisysteme von jedem Datenlaufwerk entfernen: | ||
|
|
||
| :::danger[Kritisch: Destruktiver Vorgang] | ||
| :::danger[Critical: Destruktiver Vorgang |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE="i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx"
echo "Checking for admonition labels missing closing bracket in $FILE ..."
rg -nP '^:::(info|tip|important|note|warning|danger|caution)\[[^\]]*$' "$FILE" || true
echo
echo "Expected result: no matches."Repository: unraid/docs
Length of output: 272
🏁 Script executed:
wc -l "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx"Repository: unraid/docs
Length of output: 139
🏁 Script executed:
sed -n '105,115p' "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx"Repository: unraid/docs
Length of output: 662
🏁 Script executed:
sed -n '109,125p' "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx"Repository: unraid/docs
Length of output: 702
🏁 Script executed:
sed -n '109,135p' "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx" | cat -nRepository: unraid/docs
Length of output: 1058
🏁 Script executed:
rg -nP '^:::(info|tip|important|note|warning|danger|caution)\[[^\]]*$' "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx"Repository: unraid/docs
Length of output: 99
Fix malformed admonition label syntax.
Line 109 is missing the closing ] in :::danger[...], which breaks MDX parsing for this callout.
Proposed fix
-:::danger[Critical: Destruktiver Vorgang
+:::danger[Critical: Destruktiver Vorgang]📝 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.
| :::danger[Critical: Destruktiver Vorgang | |
| :::danger[Critical: Destruktiver Vorgang] |
🧰 Tools
🪛 LanguageTool
[typographical] ~109-~109: Zeichen ohne sein Gegenstück: ‚]‘ scheint zu fehlen
Context: ...edem Datenlaufwerk entfernen: :::danger[Critical: Destruktiver Vorgang **Dieser...
(UNPAIRED_BRACKETS)
🤖 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`
at line 109, The admonition opening token is malformed: replace the incomplete
":::danger[" occurrence (the `:::danger[...]` token shown) with a correctly
formed admonition label by adding the missing closing bracket so it reads like
":::danger[Destruktiver Vorgang]" (and ensure the admonition block still ends
with a matching closing ":::"). Locate the ":::danger[" token in the FAQ content
and add the closing "]" to complete the label and verify the block is closed
with ":::".
| 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/)? | ||
|
|
||
| ### Problemas conocidos {/* #known-issues */} | ||
| ### Problemas conocidos {#known-issues} |
There was a problem hiding this comment.
Critical: Classic heading ID syntax forbidden in translated MDX files.
The syntax {#known-issues} and {#rolling-back} violates the coding guidelines for translated documentation. Crowdin's MDX import parser can reject classic heading IDs.
🔧 Proposed fix
-### Problemas conocidos {`#known-issues`}
+### Problemas conocidos {/* `#known-issues` */}-### Deshacer cambios {`#rolling-back`}
+### Deshacer cambios {/* `#rolling-back` */}As per coding guidelines: "Do not use classic heading IDs like ### Heading {#stable-anchor} in translated MDX files; Crowdin's MDX import parser can reject them"
Also applies to: 15-15
🤖 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 11, Remove the classic heading ID syntax from translated MDX headings
(e.g., change "### Problemas conocidos {`#known-issues`}" and any "### ...
{`#rolling-back`}" occurrences) by deleting the `{#...}` fragments so headings
rely on automatic Docusaurus anchors; ensure no other translated headings
contain `{#...}` and re-run the MDX import to confirm Crowdin accepts the file.
| 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/)? | ||
|
|
||
| ### Problèmes connus {/* #known-issues */} | ||
| ### Problèmes connus {#known-issues} |
There was a problem hiding this comment.
Critical: Classic heading ID syntax forbidden in translated MDX files.
The syntax {#known-issues} and {#rolling-back} violates the coding guidelines for translated documentation. Crowdin's MDX import parser can reject classic heading IDs.
🔧 Proposed fix
-### Problèmes connus {`#known-issues`}
+### Problèmes connus {/* `#known-issues` */}-### Rétrogradation {`#rolling-back`}
+### Rétrogradation {/* `#rolling-back` */}As per coding guidelines: "Do not use classic heading IDs like ### Heading {#stable-anchor} in translated MDX files; Crowdin's MDX import parser can reject them"
Also applies to: 15-15
🧰 Tools
🪛 LanguageTool
[style] ~11-~11: Un autre mot peut être plus précis.
Context: ...s/troubleshooting/licensing-faq/)? ### Problèmes connus {#known-issues} Pour d'autres problème...
(CELEBRE)
🤖 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 11, Remove classic heading ID syntax from translated MDX headings:
locate the headings "### Problèmes connus {`#known-issues`}" and the one
containing "{`#rolling-back`}" and delete the `{#...}` fragments so they become
plain headings (e.g., "### Problèmes connus" and "### ...rolling-back...").
Ensure no `{#...}` remains anywhere in this MDX file to comply with Crowdin
import rules and coding guidelines.
| # バージョン 6.12.0 2023-06-14 | ||
|
|
||
| ## アップグレードに関する注意事項 {/* #upgrade-notes */} | ||
| ## アップグレードに関する注意事項 {/\* #upgrade-notes \*/} |
There was a problem hiding this comment.
Incorrect heading anchor syntax breaks navigation.
The escaped syntax {/\* #... \*/} renders as literal text instead of creating heading anchors. The backslashes escape the asterisks, preventing MDX from recognizing these as comment-based anchors.
Use the proper MDX comment syntax without escapes:
-## アップグレードに関する注意事項 {/\* `#upgrade-notes` \*/}
+## アップグレードに関する注意事項 {/* `#upgrade-notes` */}
-### 既知の問題 {/\* `#known-issues` \*/}
+### 既知の問題 {/* `#known-issues` */}
-#### i915 ドライバに関連するクラッシュ {/\* `#crashes-related-to-i915-driver` \*/}
+#### i915 ドライバに関連するクラッシュ {/* `#crashes-related-to-i915-driver` */}
-### ロールバック {/\* `#rolling-back` \*/}
+### ロールバック {/* `#rolling-back` */}As per coding guidelines: For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}. Do not use classic heading IDs like ### Heading {#stable-anchor} in translated MDX files; Crowdin's MDX import parser can reject them.
Also applies to: 40-40, 42-42, 64-64
🤖 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.0.md`
at line 3, The heading "## アップグレードに関する注意事項" uses an escaped comment anchor `{/\*
`#upgrade-notes` \*/}` which renders literally; replace the escaped syntax with
MDX-safe comment anchor syntax `{/* `#upgrade-notes` */}` (i.e., remove the
backslashes and asterisk escaping) so the anchor is recognized, and apply the
same fix to the other affected headings referenced (lines containing anchors at
40, 42, and 64) to ensure Docusaurus/Crowdin accept the translated MDX.
| 不適切なシャットダウンは、Unraid が %%array|array%% がシステムの電源が切れる前に正しく停止されなかったことを検出したときに発生します。この状況では、データの整合性を確保するため、次回の起動時に自動的に %%parity check|parity-check%% が実行される場合があります。 | ||
|
|
||
| :::important[不適切なシャットダウンを防ぐための推奨事項] | ||
| :::important[Recommendations 不適切なシャットダウンを防ぐため |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, check if the file exists and read the relevant lines around line 13
if [ -f "i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx" ]; then
echo "=== File content around line 13 ==="
cat -n "i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx" | sed -n '1,25p'
else
echo "File not found. Searching for the file..."
find . -name "unclean-shutdowns.mdx" -type f
fiRepository: unraid/docs
Length of output: 1209
🏁 Script executed:
# Also search for similar admonition patterns in MDX files to verify syntax
echo "=== Checking admonition syntax patterns in other MDX files ==="
rg ':::important\[' --max-count 10 -A 1Repository: unraid/docs
Length of output: 47392
Add the closing bracket to the admonition title on line 13.
The missing ] breaks the MDX admonition syntax and will prevent the callout from rendering properly.
Suggested fix
-:::important[Recommendations 不適切なシャットダウンを防ぐため
+:::important[不適切なシャットダウンを防ぐための推奨事項]📝 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[不適切なシャットダウンを防ぐための推奨事項] |
🤖 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 admonition title starting with ":::important[Recommendations
不適切なシャットダウンを防ぐため" is missing a closing bracket; fix the MDX admonition by adding
the closing "]" so it becomes ":::important[Recommendations 不適切なシャットダウンを防ぐため]"
to restore proper callout rendering in the file (look for the admonition start
string in unclean-shutdowns.mdx).
| ::: | ||
|
|
||
| :::note[前提条件] | ||
| :::note\[Prerequisites] |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify escaped admonition-title syntax patterns that are likely invalid in MDX.
# Expected result: no matches after fix.
rg -nP '^:::(note|tip|info|caution|danger|important)\\\[' --iglob '*.{md,mdx}'Repository: unraid/docs
Length of output: 27902
Fix escaped admonition syntax at line 25.
Change :::note\[Prerequisites] to :::note[Prerequisites]. The backslash escape breaks admonition rendering in Docusaurus and prevents the docs from building correctly.
🤖 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 25, The admonition opening token is incorrectly escaped: replace the
literal string ':::note\[Prerequisites]' with the proper Docusaurus admonition
':::note[Prerequisites]' in the file so the admonition renders correctly; locate
the token in the document (currently shown as ':::note\[Prerequisites]') and
remove the backslash before the bracket.
| 4. **柔軟で専用のストレージ:** 複数の %%cache pools|cache-pool%% を使えば、用途ごとに特定のプールを割り当てられます。たとえば、1 つのプールをダウンロード専用に、別のプールを %%virtual machines|vm%% 用にすることで、リソース競合を減らし、効率を高められます。 | ||
|
|
||
| :::info[心に留めておくこと] | ||
| :::info[Keep 心に留めておく |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify malformed admonition titles (missing closing ']') in MD/MDX docs.
rg -nP --type-add 'mdx:*.mdx' --type mdx '^:::(info|tip|note|warning|important|caution)\[[^\]]*$'Repository: unraid/docs
Length of output: 8324
🏁 Script executed:
# Read the file around line 29 to see the full admonition structure
sed -n '25,40p' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxRepository: unraid/docs
Length of output: 1206
Missing closing ] in admonition title syntax breaks MDX parsing.
Line 29 opens :::info[ but does not close the title bracket before the content block starts, which breaks Docusaurus admonition rendering.
Suggested fix
-:::info[Keep 心に留めておく
+:::info[心に留めておくこと]📝 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.
| :::info[Keep 心に留めておく | |
| :::info[心に留めておくこと] |
🤖 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`
at line 29, The admonition opening token ":::info[" on the page is missing its
closing bracket which breaks MDX parsing; update the admonition line by closing
the title bracket (change ":::info[" to something like ":::info[Keep 心に留めておく]"
or add the missing "]" after the title) so the admonition title is properly
delimited before the block content begins; ensure the closing bracket is present
for the ":::info[" token and keep the rest of the admonition block unchanged.
| 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. | ||
|
|
||
| :::info[示例] | ||
| :::info\[Example] |
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/advanced-configurations/optimize-storage/zfs-storage.mdx"
echo "Checking for escaped bracket after admonition directive..."
rg -nP '^:::(info|tip|important|note|warning|danger|caution)\\\[' "$FILE" || true
echo
echo "Checking for missing closing bracket in admonition titles..."
rg -nP '^:::(info|tip|important|note|warning|danger|caution)\[[^\]]*$' "$FILE" || true
echo
echo "Expected result: no matches in either check."Repository: unraid/docs
Length of output: 269
Fix malformed admonition declarations.
Line 35 has an escaped bracket (:::info\[Example]) and line 177 is missing a closing bracket (:::tip[Optimizing 硬盘数量) in admonition openers. Both will break MDX directive parsing.
Proposed fixes
-:::info\[Example]
+:::info[Example]
-:::tip[Optimizing 硬盘数量
+:::tip[Optimizing 硬盘数量]📝 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.
| :::info\[Example] | |
| :::info[Example] |
🤖 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/advanced-configurations/optimize-storage/zfs-storage.mdx`
at line 35, The admonition openers are malformed: change the escaped bracket in
`:::info\[Example]` to a normal opener `:::info[Example]` and add the missing
closing bracket on `:::tip[Optimizing 硬盘数量` so it becomes `:::tip[Optimizing
硬盘数量]`; update these directive lines (the `:::info...` and `:::tip...` tokens)
so MDX directive parsing succeeds.
| 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/)? | ||
|
|
||
| ### 已知问题 {/* #known-issues */} | ||
| ### 已知问题 {#known-issues} |
There was a problem hiding this comment.
Use comment syntax for heading anchors instead of classic heading IDs.
Lines 11 and 15 use classic heading ID syntax {#...} which should not be used in translated MDX files as Crowdin's MDX import parser can reject them.
Use the MDX-safe comment syntax:
-### 已知问题 {`#known-issues`}
+### 已知问题 {/* `#known-issues` */}
-### 回滚 {`#rolling-back`}
+### 回滚 {/* `#rolling-back` */}As per coding guidelines: Do not use classic heading IDs like ### Heading {#stable-anchor} in translated MDX files; Crowdin's MDX import parser can reject them. For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}.
Also applies to: 15-15
🤖 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 11, Replace the classic heading ID syntax `{#...}` with MDX-safe comment
anchors for the translated headings: locate the heading "### 已知问题
{`#known-issues`}" and the other heading using `{#...}` on the same file and
change their anchors to the MDX comment form `/* `#stable-anchor` */` (e.g.,
convert the `{`#known-issues`}` anchor to a comment-style anchor) so the headings
become MDX-safe for Crowdin import; update only the anchor syntax for the
headings (keep the heading text identical) in the file.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
unraid-docs | 5f2ff82 | Apr 19 2026, 01:16 PM |
1 participant
Summary by CodeRabbit