Conversation
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 7
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
♻️ Duplicate comments (1)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
35-35:⚠️ Potential issue | 🔴 CriticalFix invalid admonition marker escaping at Line 35.
:::info\[Example]is malformed and can break admonition parsing. Use a normal bracketed title.Proposed fix
-:::info\[Example] +:::info[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/advanced-configurations/optimize-storage/zfs-storage.mdx` at line 35, The admonition marker in the doc is malformed: replace the incorrect token ":::info\[Example]" with a proper admonition header like ":::info[Example]" (remove the backslash) and ensure the corresponding closing ":::” is present; locate the usage of the admonition token in the file (the string :::info\[Example]) and update it to the bracketed title form so the admonition parser can recognize it.
🟡 Minor comments (15)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx-33-33 (1)
33-33:⚠️ Potential issue | 🟡 MinorLocalize remaining English sentences in JA doc.
These lines are still in English inside a Japanese page, which causes inconsistent UX for localized docs.
Also applies to: 365-365, 368-368, 378-378
🤖 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 remaining English sentence(s) into Japanese in the indicated JA doc so the page is fully localized; specifically replace the English sentence containing the tokens %%ZFS|zfs%%, %%array|array%% and %%parity|parity%% with a natural Japanese translation while preserving those token markers (e.g., keep %%ZFS|zfs%%, %%array|array%%, %%parity|parity%% exactly as-is) and apply the same fix to the other occurrences referenced (lines containing the same sentence patterns around tokens at the other three locations).i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md-146-146 (1)
146-146:⚠️ Potential issue | 🟡 Minor用語に文字化け/混在タイポがあります。
Line 146 の
статisticsはstatisticsの誤記です。🔧 Proposed fix
-- 機能: Dashboard が Unraid API から CPU 使用率 статистics を取得するようになりました +- 機能: Dashboard が Unraid API から CPU 使用率 statistics を取得するようになりました🤖 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` at line 146, Replace the typo in the Japanese release-note sentence "Dashboard が Unraid API から CPU 使用率 статистics を取得するようになりました" by changing the Cyrillic/incorrect token "статistics" to the correct English "statistics" so the line reads "Dashboard が Unraid API から CPU 使用率 statistics を取得するようになりました"; locate and update that exact string in the document (the release notes entry) to correct the mixed-character typo.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md-62-62 (1)
62-62:⚠️ Potential issue | 🟡 Minor相対リンクの階層が1つ浅く、リンク切れの可能性があります。
Line 62 の
../using-unraid-to/...は、このファイル位置からだと../../using-unraid-to/...でないと解決できない可能性が高いです。🔧 Proposed fix
-詳細はドキュメントの [新しいファイルシステムタイプへの変換](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) を参照してください。 +詳細はドキュメントの [新しいファイルシステムタイプへの変換](../../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) を参照してください。🤖 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` at line 62, The relative link in the release notes text uses `../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type`, which from this file's location likely needs one more `..` to resolve; update that markdown link in i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md so it points to `../../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type` (i.e., change `../using-unraid-to/...` to `../../using-unraid-to/...`) to fix the broken relative path.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx-266-266 (1)
266-266:⚠️ Potential issue | 🟡 MinorJapanese locale text is mixed with an English section label.
Line 266 starts with
User Preferencesでは...; consider localizing this label (e.g.,ユーザー設定では...) to keep terminology consistent across this Japanese page.🤖 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 266, The string "User Preferences" is left in English inside the Japanese document; replace that label with a localized Japanese term (e.g., "ユーザー設定") in the sentence that begins with "User Preferencesでは..." so the terminology is consistent; ensure the rest of the sentence (including tokens like "%%Mover|mover%%") remains unchanged and that any other occurrences of "User Preferences" in this file are updated similarly.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx-331-340 (1)
331-340:⚠️ Potential issue | 🟡 MinorIn-page link target may break without an explicit heading ID.
Line 331 links to
#smtp-settings, but Line 340’s heading does not define that explicit anchor. Please add a stable ID to avoid broken jumps in localized builds.🔧 Proposed fix
-- **メール**: メールで通知を送信します（[SMTP 設定](`#smtp-settings`) が必要です） +- **メール**: メールで通知を送信します（[SMTP 設定](`#smtp-settings`) が必要です） -#### SMTP 設定 +#### SMTP 設定 {`#smtp-settings`}🤖 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` around lines 331 - 340, The in-page link targets "#smtp-settings" but the "#### SMTP 設定" heading has no explicit ID, so add a stable anchor to that heading (e.g., change the heading to include {`#smtp-settings`} or insert an HTML anchor <a id="smtp-settings"></a> immediately before the "#### SMTP 設定" heading) so the link reliably jumps to the section; update the "SMTP 設定" heading in the file to include that explicit ID.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx-38-38 (1)
38-38:⚠️ Potential issue | 🟡 Minor日本語ロケール内の英語文を翻訳してください。
Line 38 が英語のままで、同ページ内の言語一貫性が崩れています。
Proposed fix
- To set the %%parity|parity%% bits, we find the total for each column. If the sum is even, the %%parity|parity%% bit is 0; if odd, the %%parity|parity%% bit is 1. + %%parity|parity%%ビットを設定するには、各列の合計を求めます。合計が偶数なら%%parity|parity%%ビットは0、奇数なら1になります。🤖 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` at line 38, このファイル内の英語文 "To set the %%parity|parity%% bits, we find the total for each column. If the sum is even, the %%parity|parity%% bit is 0; if odd, the %%parity|parity%% bit is 1." must be translated into Japanese while preserving the placeholder tokens %%parity|parity%% exactly as-is; replace that sentence with a natural Japanese equivalent (e.g. "%%parity|parity%% ビットを設定するには、各列の合計を求めます。合計が偶数なら %%parity|parity%% ビットは 0、奇数なら 1 になります。") and ensure punctuation and spacing match the surrounding locale style for consistency.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx-23-23 (1)
23-23:⚠️ Potential issue | 🟡 Minor未翻訳文とトークン語尾 typo を同時に修正してください。
Line 23 は日本語ページ内で英語のままです。加えて
%%parity drive|parity-drives%%sは語尾sが余分で表示崩れになります。Proposed fix
- The main job of an Unraid %%array|array%% is to organize and protect the data stored across several drives. It does this by using up to two special drives called %%parity drive|parity-drives%%s. These %%parity drive|parity-drives%%s are important because they help reconstruct your data if one of the other drives fails. In fact, with just one %%parity drive|parity-drives%%, you can protect all the other drives in your %%array|array%%, keeping your data safe. Plus, you can mix different sized drives and easily expand your storage over time, making Unraid a user-friendly option for anyone looking to manage their data effectively. + Unraidの%%array|array%%の主な役割は、複数のドライブに保存されたデータを整理し保護することです。これには、最大2台の特別なドライブ（%%parity drive|parity-drives%%）を使用します。%%parity drive|parity-drives%%は、ほかのドライブが故障した際のデータ再構築に重要です。実際、%%parity drive|parity-drives%%が1台あれば、%%array|array%%内のほかのドライブすべてを保護できます。さらに、異なる容量のドライブを混在でき、ストレージを段階的に拡張できるため、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/what-is-unraid.mdx` at line 23, The sentence on line with tokens is still in English and contains a token suffix typo; replace the English sentence with a proper Japanese translation and fix the token usage by removing the stray "s" after the token so that "%%parity drive|parity-drives%%s" becomes "%%parity drive|parity-drives%%" and keep "%%array|array%%" tokens correctly placed; ensure the translated Japanese text conveys the meaning about the array organizing/protecting data, using up to two parity drives, single-parity protection, mixed drive sizes, and easy expansion while preserving the token markers exactly as corrected.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx-155-155 (1)
155-155:⚠️ Potential issue | 🟡 Minorこの段落も日本語へ統一してください。
Line 155 は英語文のままです。日本語ページとしては未翻訳に見えます。
Proposed fix
- Unraid's %%KVM|kvm%%-based virtualization uses modern tools for flexible hardware assignment while maintaining host stability. + Unraidの%%KVM|kvm%%ベースの仮想化は、ホストの安定性を維持しながら、柔軟なハードウェア割り当てを可能にする最新ツールを利用します。🤖 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` at line 155, この英語文 "Unraid's %%KVM|kvm%%-based virtualization uses modern tools for flexible hardware assignment while maintaining host stability." を日本語に翻訳して置き換えてください（ファイル内の該当箇所はトークン %%KVM|kvm%% を保持する必要があります）。例えば「Unraid の %%KVM|kvm%% ベースの仮想化は、ホストの安定性を保ちながら柔軟なハードウェア割り当てを可能にする最新のツールを利用しています。」のように翻訳し、MDX のマークアップや特殊トークンを変更しないでコミットしてください。i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-147-147 (1)
147-147:⚠️ Potential issue | 🟡 MinorMixed-language typo at Line 147 in a Japanese page.
प्राथमिकis Hindi text embedded in ja locale content and should be replaced with Japanese wording.Proposed fix
-✅ USB フラッシュドライブを प्राथमिक起動デバイスとして設定します。\ +✅ USB フラッシュドライブを主要な起動デバイスとして設定します。\🤖 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 147, The sentence contains a Hindi token `प्राथमिक` embedded in Japanese; replace that token with the appropriate Japanese wording (e.g., "主要" or "プライマリ") so the line reads like "✅ USB フラッシュドライブを主要起動デバイスとして設定します。" (or "✅ USB フラッシュドライブをプライマリ起動デバイスとして設定します。") to fix the mixed-language typo.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 | 🟡 MinorUntranslated English sentence at Line 169.
This line is still in English inside a Japanese doc and should be localized for consistency.
Proposed 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 proper Japanese localization; for example: "多くのマザーボードは起動デバイスの選択を12台のハードドライブに制限します。USBフラッシュドライブがハードドライブとして認識されると、12台の物理ハードドライブをインストールした後にそこから起動できなくなる可能性があります。可能であればBIOSでフラッシュドライブをリムーバブルデバイスとして扱うように設定してください。" Ensure the replacement occurs in the same paragraph in the document where that English sentence appears.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx-53-53 (1)
53-53:⚠️ Potential issue | 🟡 MinorThe in-page anchor is likely broken.
Line 191 links to
#repair-file-systems, but the target heading at Line 53 has no explicit id and is Japanese text. Add an explicit id to keep this link stable.🔗 Proposed fix
-## ファイルシステムを修復する +## ファイルシステムを修復する {`#repair-file-systems`}Also applies to: 191-191
🤖 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 53, The anchor link to "#repair-file-systems" is broken because the target heading "## ファイルシステムを修復する" has no explicit id; update that heading to include the explicit id (for example add `{`#repair-file-systems`}` or an equivalent HTML anchor) so the link at the location referencing "#repair-file-systems" resolves correctly; ensure you modify the heading text "## ファイルシステムを修復する" to include the id token exactly matching the linked anchor.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx-30-31 (1)
30-31:⚠️ Potential issue | 🟡 MinorAvoid preview-domain links in published documentation.
unraid-production-481d40bf.preview.craft.cloudURLs are environment-specific and brittle. Prefer canonical production docs/app links onunraid.net.Also applies to: 254-254
🤖 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` around lines 30 - 31, Replace the preview-domain URLs (unraid-production-481d40bf.preview.craft.cloud) used in the Duplicati and rclone links with their canonical production links on unraid.net; specifically update the two links that reference "Duplicati" and "rclone" to use the official unraid.net app/doc URLs (and mirror the same change for the duplicated occurrence noted at line 254), ensuring the link text and anchors remain correct.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx-187-187 (1)
187-187:⚠️ Potential issue | 🟡 MinorRemove duplicated wording for clarity.
「代わりに、まず最初に…」 has redundant phrasing. Use either 「まず」 or 「最初に」.
✂️ Proposed 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/troubleshooting/common-issues/data-recovery.mdx` at line 187, The sentence contains redundant phrasing "代わりに、まず最初にファイルシステムの修復を試みるべきです。" — edit that sentence (the one starting with "代わりに、まず最初に") to remove duplication by using either "まず" or "最初に" (e.g., "まずファイルシステムの修復を試みるべきです。") so the meaning stays the same and wording is clearer.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx-83-84 (1)
83-84:⚠️ Potential issue | 🟡 MinorLocalize the remaining English bullet in this Japanese page.
Line 84 is still English, which breaks localization consistency.
✏️ 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` around lines 83 - 84, Translate the leftover English bullet "For non-%%array|array%% drives (like %%cache|cache%%-only devices), use the direct partition path, e.g., `/dev/sdj1`." into Japanese and replace the English line in the document; keep the localization tokens %%array|array%% and %%cache|cache%% intact and preserve the example device path `/dev/sdj1` in the translated sentence so formatting and placeholders remain correct.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx-268-268 (1)
268-268:⚠️ Potential issue | 🟡 MinorFix malformed inline code formatting.
There is an unmatched backtick in `/boot/ddrescue.log`` which will render incorrectly.
🧹 Proposed fix
-- /boot/ddrescue.log\` ファイルは進行状況を記録し、処理が中断されても再開できるようにします。 +- `/boot/ddrescue.log` ファイルは進行状況を記録し、処理が中断されても再開できるようにします。🤖 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 268, Fix the malformed inline code by removing the stray backslash and unmatched backtick in the fragment `/boot/ddrescue.log\`` and render the path as a proper inline code token (e.g., `/boot/ddrescue.log`), ensuring the opening and closing backticks match in the sentence where that string appears.
🧹 Nitpick comments (3)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md (1)
9-9: 日本語として不自然な疑問文です。Line 9 の「質問はこちらですか?」は直訳調なので、「質問はこちら」などにすると自然です。
✍️ Suggested wording
-手順ごとの説明は、[Unraid のアップグレード](../../unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx) を参照してください。[ライセンス](../../unraid-os/troubleshooting/licensing-faq.mdx#license-types--features) に関する質問はこちらですか? +手順ごとの説明は、[Unraid のアップグレード](../../unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx) を参照してください。[ライセンス](../../unraid-os/troubleshooting/licensing-faq.mdx#license-types--features) に関する質問はこちら。🤖 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` at line 9, Replace the unnatural literal question "質問はこちらですか?" in the sentence that references the Unraid upgrade and license links with a more natural phrasing such as "ご質問はこちら" (or "ご質問はこちらをご覧ください" / "ご質問はこちらから") so the line reads naturally in Japanese; locate the exact string "質問はこちらですか?" in the current doc and swap it with the chosen natural variant.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (1)
120-120: Optional copy polish: simplify repeated “ことができます” phrasing.These lines read naturally, but trimming repeated “ことができます” can make the Japanese copy tighter and more direct.
Also applies to: 406-406, 447-447
🤖 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 120, The sentence repeats 「ことができます」 and should be tightened: rewrite the line "Docker コンテナーで WiFi を使用する予定の場合は、Docker サービスを開始する**前に**、有線接続があれば必ず取り外してください。これにより、両方のインターフェースが同時に有効なときに発生する可能性のあるネットワーク構成の競合を防ぐことができます。" to remove the duplicated 「ことができます」 phrasing (for example, change the clause to 「これにより、両方のインターフェースが同時に有効になると発生するネットワーク構成の競合を防げます。」 or similar), and apply the same simplification to the other occurrences noted (lines referenced 406 and 447) so each sentence uses a single, concise 「防げます」/「防ぎます」 form instead of repeating 「ことができます」.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md (1)
275-275: Consider more specific heading names to avoid duplication.The heading "その他の変更" (Other Changes) appears four times under different parent sections. While technically valid, duplicate headings can cause ambiguous fragment IDs and make it harder to link to specific sections.
Consider using more specific headings like:
- "その他の Docker の変更" (Other Docker Changes) - Line 275
- "その他のネットワークの変更" (Other Network Changes) - Line 303
- "その他の webGUI の変更" (Other webGUI Changes) - Line 378
- "その他の全般的な変更" (Other General Changes) - Line 404
Also applies to: 303-303, 378-378, 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/release-notes/7.0.0.md` at line 275, The heading "その他の変更" is duplicated across four sections; rename each duplicate heading to be specific to its parent context (replace the "その他の変更" heading instances with "その他の Docker の変更", "その他のネットワークの変更", "その他の webGUI の変更", and "その他の全般的な変更" respectively) so fragment IDs are unique and links unambiguous, and update any local anchors or cross-links that referenced the old "その他の変更" heading text to the new, more specific headings.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`:
- Line 351: The admonition intro `:::tip[Planning 先を見据えて` is missing a closing
`]`, which breaks MDX parsing; edit the line containing `:::tip[Planning 先を見据えて`
in the file and add the missing `]` so it becomes `:::tip[Planning 先を見据えて]`,
ensuring the admonition title is properly closed and the MDX admonition block
parses correctly.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 10: The admonition syntax in multiple localization docs uses an escaped
bracket (":::info\[Localize]") which prevents Docusaurus from parsing the title;
replace every occurrence of that token with the correct admonition syntax
(":::info[Localize]") across the affected localization files (de, es, fr, ja,
zh) so the admonition title renders properly, ensuring you update all instances
in the document (search for ":::info\\[Localize]" and change to
":::info[Localize]").
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx`:
- Around line 68-76: 画像要素の英語の代替テキストとキャプションが残っているため、日本語ロケール向けに統一してください:
"/img/User_shares_-_distribution@500px.png" の img alt を「ユーザー共有 -
分布の例」などの日本語に、対応する figcaption「User shares - Distribution」を「ユーザー共有 - 分布」に、
"/img/User_shares_-_access@500px.png" の img alt を「ユーザー共有 - アクセスの例（大）」など日本語に、対応する
figcaption「User shares - Access」を「ユーザー共有 - アクセス」にそれぞれ変更して、alt と figcaption
が日本語で一致するように更新してください。
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md`:
- Line 11: Links in the doc use English fragment IDs (e.g.,
`#tailscale-integration`, `#add-support-for-overlay2-storage-driver`) but the target
headings are in Japanese, so the anchors are broken; locate every link that
points to those English fragments (references to `#tailscale-integration`,
`#add-support-for-overlay2-storage-driver` and the others mentioned in the review)
and replace the fragment with the slug Docusaurus generates from the actual
Japanese heading text (i.e., update links like [Tailscale Docker
統合](`#tailscale-integration`) to use the Japanese-slugified anchor that matches
the heading, and do the same for the overlay2/storage-driver and the other
occurrences at the noted locations).
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Line 115: Replace the corrupted Bengali word "টাইপো" in the release note line
referencing "rc.crond" with the correct Japanese katakana "タイポ"; update the
string "- 修正: rc.crond のステータスの টাইপোを修正" to use "タイポ" so the sentence reads
correctly as "- 修正: rc.crond のステータスのタイポを修正" and ensure the file encoding is
saved as UTF-8 to prevent further character corruption.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx`:
- Around line 100-103: The BTRFS entry currently lists "**BTRFS:** `btrfs
scrub`" which is misleading because scrub only verifies checksums and repairs
from redundant copies and does not perform structural repairs; update the
documentation entry for the BTRFS bullet (the line containing "**BTRFS:** `btrfs
scrub`") to recommend using "btrfs check" for structural repair and explicitly
warn that "btrfs check --repair" must be used only with caution (and reference
the existing guide section on repair best practices), replacing the scrub
recommendation with this corrected guidance and an explicit note about scrub's
limited role.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx`:
- Line 54: Translate the English paragraph on anonymization into Japanese and
replace the English text at the indicated location; preserve all special
placeholders and formatting such as %%Mover|mover%%, %%syslog|syslog%%, and the
bold path ***Settings → Scheduler → Mover Settings***, and maintain the
surrounding section title "### 診断データの匿名化" and tone consistent with the rest of
the file; ensure the translation conveys that diagnostics are anonymized by
default, that enabling %%Mover|mover%% logging under the specified settings will
include file details in %%syslog|syslog%%, and that enabling it should be
limited to troubleshooting mover-related issues because it may reveal file paths
and names.
---
Minor comments:
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`:
- Line 33: Translate the remaining English sentence(s) into Japanese in the
indicated JA doc so the page is fully localized; specifically replace the
English sentence containing the tokens %%ZFS|zfs%%, %%array|array%% and
%%parity|parity%% with a natural Japanese translation while preserving those
token markers (e.g., keep %%ZFS|zfs%%, %%array|array%%, %%parity|parity%%
exactly as-is) and apply the same fix to the other occurrences referenced (lines
containing the same sentence patterns around tokens at the other three
locations).
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx`:
- Line 266: The string "User Preferences" is left in English inside the Japanese
document; replace that label with a localized Japanese term (e.g., "ユーザー設定") in
the sentence that begins with "User Preferencesでは..." so the terminology is
consistent; ensure the rest of the sentence (including tokens like
"%%Mover|mover%%") remains unchanged and that any other occurrences of "User
Preferences" in this file are updated similarly.
- Around line 331-340: The in-page link targets "#smtp-settings" but the "####
SMTP 設定" heading has no explicit ID, so add a stable anchor to that heading
(e.g., change the heading to include {`#smtp-settings`} or insert an HTML anchor
<a id="smtp-settings"></a> immediately before the "#### SMTP 設定" heading) so the
link reliably jumps to the section; update the "SMTP 設定" heading in the file to
include that explicit ID.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Line 147: The sentence contains a Hindi token `प्राथमिक` embedded in Japanese;
replace that token with the appropriate Japanese wording (e.g., "主要" or "プライマリ")
so the line reads like "✅ USB フラッシュドライブを主要起動デバイスとして設定します。" (or "✅ USB
フラッシュドライブをプライマリ起動デバイスとして設定します。") to fix the mixed-language typo.
- 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 proper Japanese localization; for example:
"多くのマザーボードは起動デバイスの選択を12台のハードドライブに制限します。USBフラッシュドライブがハードドライブとして認識されると、12台の物理ハードドライブをインストールした後にそこから起動できなくなる可能性があります。可能であればBIOSでフラッシュドライブをリムーバブルデバイスとして扱うように設定してください。"
Ensure the replacement occurs in the same paragraph in the document where that
English sentence appears.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx`:
- Line 38: このファイル内の英語文 "To set the %%parity|parity%% bits, we find the total for
each column. If the sum is even, the %%parity|parity%% bit is 0; if odd, the
%%parity|parity%% bit is 1." must be translated into Japanese while preserving
the placeholder tokens %%parity|parity%% exactly as-is; replace that sentence
with a natural Japanese equivalent (e.g. "%%parity|parity%%
ビットを設定するには、各列の合計を求めます。合計が偶数なら %%parity|parity%% ビットは 0、奇数なら 1 になります。") and
ensure punctuation and spacing match the surrounding locale style for
consistency.
- Line 23: The sentence on line with tokens is still in English and contains a
token suffix typo; replace the English sentence with a proper Japanese
translation and fix the token usage by removing the stray "s" after the token so
that "%%parity drive|parity-drives%%s" becomes "%%parity drive|parity-drives%%"
and keep "%%array|array%%" tokens correctly placed; ensure the translated
Japanese text conveys the meaning about the array organizing/protecting data,
using up to two parity drives, single-parity protection, mixed drive sizes, and
easy expansion while preserving the token markers exactly as corrected.
- Line 155: この英語文 "Unraid's %%KVM|kvm%%-based virtualization uses modern tools
for flexible hardware assignment while maintaining host stability."
を日本語に翻訳して置き換えてください（ファイル内の該当箇所はトークン %%KVM|kvm%% を保持する必要があります）。例えば「Unraid の
%%KVM|kvm%% ベースの仮想化は、ホストの安定性を保ちながら柔軟なハードウェア割り当てを可能にする最新のツールを利用しています。」のように翻訳し、MDX
のマークアップや特殊トークンを変更しないでコミットしてください。
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`:
- Line 146: Replace the typo in the Japanese release-note sentence "Dashboard が
Unraid API から CPU 使用率 статистics を取得するようになりました" by changing the
Cyrillic/incorrect token "статistics" to the correct English "statistics" so the
line reads "Dashboard が Unraid API から CPU 使用率 statistics を取得するようになりました"; locate
and update that exact string in the document (the release notes entry) to
correct the mixed-character typo.
- Line 62: The relative link in the release notes text uses
`../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type`,
which from this file's location likely needs one more `..` to resolve; update
that markdown link in
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md
so it points to
`../../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type`
(i.e., change `../using-unraid-to/...` to `../../using-unraid-to/...`) to fix
the broken relative path.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx`:
- Line 53: The anchor link to "#repair-file-systems" is broken because the
target heading "## ファイルシステムを修復する" has no explicit id; update that heading to
include the explicit id (for example add `{`#repair-file-systems`}` or an
equivalent HTML anchor) so the link at the location referencing
"#repair-file-systems" resolves correctly; ensure you modify the heading text
"## ファイルシステムを修復する" to include the id token exactly matching the linked anchor.
- Around line 30-31: Replace the preview-domain URLs
(unraid-production-481d40bf.preview.craft.cloud) used in the Duplicati and
rclone links with their canonical production links on unraid.net; specifically
update the two links that reference "Duplicati" and "rclone" to use the official
unraid.net app/doc URLs (and mirror the same change for the duplicated
occurrence noted at line 254), ensuring the link text and anchors remain
correct.
- Line 187: The sentence contains redundant phrasing
"代わりに、まず最初にファイルシステムの修復を試みるべきです。" — edit that sentence (the one starting with
"代わりに、まず最初に") to remove duplication by using either "まず" or "最初に" (e.g.,
"まずファイルシステムの修復を試みるべきです。") so the meaning stays the same and wording is clearer.
- Around line 83-84: Translate the leftover English bullet "For
non-%%array|array%% drives (like %%cache|cache%%-only devices), use the direct
partition path, e.g., `/dev/sdj1`." into Japanese and replace the English line
in the document; keep the localization tokens %%array|array%% and
%%cache|cache%% intact and preserve the example device path `/dev/sdj1` in the
translated sentence so formatting and placeholders remain correct.
- Line 268: Fix the malformed inline code by removing the stray backslash and
unmatched backtick in the fragment `/boot/ddrescue.log\`` and render the path as
a proper inline code token (e.g., `/boot/ddrescue.log`), ensuring the opening
and closing backticks match in the sentence where that string appears.
---
Duplicate comments:
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`:
- Line 35: The admonition marker in the doc is malformed: replace the incorrect
token ":::info\[Example]" with a proper admonition header like
":::info[Example]" (remove the backslash) and ensure the corresponding closing
":::” is present; locate the usage of the admonition token in the file (the
string :::info\[Example]) and update it to the bracketed title form so the
admonition parser can recognize it.
---
Nitpick comments:
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx`:
- Line 120: The sentence repeats 「ことができます」 and should be tightened: rewrite the
line "Docker コンテナーで WiFi を使用する予定の場合は、Docker
サービスを開始する**前に**、有線接続があれば必ず取り外してください。これにより、両方のインターフェースが同時に有効なときに発生する可能性のあるネットワーク構成の競合を防ぐことができます。"
to remove the duplicated 「ことができます」 phrasing (for example, change the clause to
「これにより、両方のインターフェースが同時に有効になると発生するネットワーク構成の競合を防げます。」 or similar), and apply the
same simplification to the other occurrences noted (lines referenced 406 and
447) so each sentence uses a single, concise 「防げます」/「防ぎます」 form instead of
repeating 「ことができます」.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md`:
- Line 275: The heading "その他の変更" is duplicated across four sections; rename each
duplicate heading to be specific to its parent context (replace the "その他の変更"
heading instances with "その他の Docker の変更", "その他のネットワークの変更", "その他の webGUI の変更",
and "その他の全般的な変更" respectively) so fragment IDs are unique and links unambiguous,
and update any local anchors or cross-links that referenced the old "その他の変更"
heading text to the new, more specific headings.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`:
- Line 9: Replace the unnatural literal question "質問はこちらですか?" in the sentence
that references the Unraid upgrade and license links with a more natural
phrasing such as "ご質問はこちら" (or "ご質問はこちらをご覧ください" / "ご質問はこちらから") so the line reads
naturally in Japanese; locate the exact string "質問はこちらですか?" in the current doc
and swap it with the chosen natural variant.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 51f64ca2-0f53-44ee-accf-90cf20b76a70
📒 Files selected for processing (136)
i18n/ja/docusaurus-plugin-content-docs/current/API/api-key-app-developer-authorization-flow.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/cli.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/index.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/partials/get-started-pre72.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/upcoming-features.mdxi18n/ja/docusaurus-plugin-content-docs/current/contribute/style-guide.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-account/_category_.jsoni18n/ja/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-account/update-billing-address-on-file.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.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/explore-the-user-interface/tour-the-web-gui.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.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/set-up-unraid/internal-boot-faq.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/7.0.0.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.3.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-manual-method.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/manual-downgrade-command-line.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/manual-downgrade-simplest.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/reset-password-advanced.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/reset-password-basic.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.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/docker-troubleshooting.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-xfs.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/unclean-shutdowns/flash-drive-failure.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/troubleshooting/diagnostics/partials/syslog-server/local.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/partials/licensing-faq/manual-keyfile-network.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/partials/licensing-faq/manual-keyfile-offline.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/partials/windows-upgrade-clean-install.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/partials/windows-upgrade-in-place.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/partials/windows-virtio-automatic.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/partials/windows-virtio-manual.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/create-virtual-machines/vm-conversion-and-migration.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/partials/safe-mode-alternative.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/partials/safe-mode-preferred.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.jsoni18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/adding-disks-to-array.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/overview.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/add-data-disk-no-parity.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/add-data-disk-parity-protected.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-read.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-btrfs.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-xfs.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-zfs.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-btrfs.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-xfs.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-zfs.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-array-to-pool.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-between-pools-manual.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-between-pools-using-mover.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/parity-swap-what.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/parity-swap-when.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/pool-multi-device-mode.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/pool-single-device-mode.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-standard.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-command-line.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/shares-array-to-cache-611.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/shares-array-to-cache-612.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/shares-cache-to-array-611.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/shares-cache-to-array-612.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/shares-primary-storage-611.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/shares-primary-storage-612.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-device-limit.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-key-server.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-missing-disks.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-withdrawn-release.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/managing-and-customizing-containers.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/community-apps-installing.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/community-apps-reinstalling.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/community-apps-removing.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/command-logs.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/command-restart.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/command-start.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/command-status.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/command-stop.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/network-type.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/port-mappings.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/volume-mappings.mdxi18n/ja/docusaurus-theme-classic/footer.json
✅ Files skipped from review due to trivial changes (40)
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-manual-method.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/API/partials/get-started-pre72.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/manual-downgrade-simplest.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/unclean-shutdowns/flash-drive-failure.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/reset-password-basic.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-account/category.json
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/manual-downgrade-command-line.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/reset-password-advanced.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-xfs.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/docker-troubleshooting.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/contribute/style-guide.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/API/api-key-app-developer-authorization-flow.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
- i18n/ja/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx
🚧 Files skipped from review as they are similar to previous changes (11)
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-account/update-billing-address-on-file.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/API/cli.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/API/index.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
| - **より大容量のドライブに交換する:** vdev 内の各ドライブを、1台ずつより大きいディスクに交換します。詳細な手順は[ドライブ交換](../../using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx#replacing-faileddisabled-disks)を参照してください。すべてのドライブを交換してプールが再計算されると、vdev の容量が増加します。 | ||
| - **新しいプールを作成する:** 新しい %%ZFS|zfs%% プールを用意すると、異なるデータ種別やワークロードを整理して独立して管理できます。 | ||
|
|
||
| :::tip[Planning 先を見据えて |
Contributor
There was a problem hiding this comment.
Close the admonition title bracket at Line 351.
:::tip[Planning 先を見据えて is missing a closing ], which can break MDX/admonition parsing.
Proposed fix
-:::tip[Planning 先を見据えて
+:::tip[Planning 先を見据えて]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| :::tip[Planning 先を見据えて | |
| :::tip[Planning 先を見据えて] |
🤖 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 351, The admonition intro `:::tip[Planning 先を見据えて` is missing a closing
`]`, which breaks MDX parsing; edit the line containing `:::tip[Planning 先を見据えて`
in the file and add the missing `]` so it becomes `:::tip[Planning 先を見据えて]`,
ensuring the admonition title is properly closed and the MDX admonition block
parses correctly.
|
|
||
| Unraid OSを初めて起動した後は、%%WebGUI|web-gui%%を使用してシステム設定を完了します。このインターフェースでは、サーバーの管理、ストレージの設定、ユーザー共有の構成、%%hardware virtualization|hvm%%やDockerコンテナなどの機能の制御を行えます。 | ||
|
|
||
| :::info\[Localize] |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify whether escaped admonition-title syntax exists elsewhere in MDX files.
rg -nP ':::(info|note|tip|warning|danger)\\\[' --type mdx
rg -nP ':::(info|note|tip|warning|danger)\[' --type mdx | head -n 20Repository: unraid/docs
Length of output: 110
🌐 Web query:
What is the correct Docusaurus MDX admonition syntax for adding a title, and is :::info[Title] valid?
💡 Result:
The correct Docusaurus MDX admonition syntax for adding a title is :::info[Title] followed by the content on a new line and closing with :::. :::info[Title] is valid. This syntax uses square brackets for the optional title, which supports Markdown syntax. Example from official docs: :::note[Your Title with some Markdown syntax!] Some content with some Markdown syntax. ::: Note: Older versions used space-separated titles like :::note Your Title, but current docs (published 2026-03-06) use the bracketed format.
Citations:
- 1: https://docusaurus.io/docs/markdown-features/admonitions
- 2: https://docusaurus.io/docs/2.x/markdown-features/admonitions
- 3: https://docusaurus.io/pt-BR/docs/3.3.2/markdown-features/admonitions
🏁 Script executed:
# Find the file and read its content around line 10
fd 'deploy-and-configure-unraid-os.mdx' --path '*ja/*'Repository: unraid/docs
Length of output: 270
🏁 Script executed:
# Find the file more directly
fd 'deploy-and-configure-unraid-os.mdx'Repository: unraid/docs
Length of output: 744
🏁 Script executed:
# Read the Japanese MDX file around line 10
sed -n '1,20p' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
echo "---"
echo "For comparison, English source:"
# Read English version for comparison
sed -n '1,20p' docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxRepository: unraid/docs
Length of output: 1635
🏁 Script executed:
# Check if other localization files have the same escaped bracket issue
grep -r ':::info\\' i18n/*/docusaurus-plugin-content-docs/current/ --include='*.mdx' | head -20Repository: unraid/docs
Length of output: 2573
Remove backslash escape from admonition title syntax at Line 10.
The syntax :::info\[Localize] is incorrect. Docusaurus admonitions use :::info[Localize] without a backslash. The backslash breaks the bracket parsing and prevents the title from rendering. This pattern appears systematically across all localization files (de, es, fr, ja, zh), so address it consistently.
Proposed fix
-:::info\[Localize]
+:::info[Localize]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| :::info\[Localize] | |
| :::info[Localize] |
🤖 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 10, The admonition syntax in multiple localization docs uses an escaped
bracket (":::info\[Localize]") which prevents Docusaurus from parsing the title;
replace every occurrence of that token with the correct admonition syntax
(":::info[Localize]") across the affected localization files (de, es, fr, ja,
zh) so the admonition title renders properly, ensuring you update all instances
in the document (search for ":::info\\[Localize]" and change to
":::info[Localize]").
Comment on lines
+68
to
+76
| <img src="/img/User_shares_-_distribution@500px.png" alt="User shares distribution example" /> | ||
|
|
||
| <figcaption>User shares - Distribution</figcaption> | ||
| </figure> | ||
|
|
||
| <figure className="flex-figure"> | ||
| <img src="/img/User_shares_-_access@500px.png" alt="User shares distribution example larger" /> | ||
|
|
||
| <figcaption>User shares - Access</figcaption> |
Contributor
There was a problem hiding this comment.
alt とキャプションを日本語化してアクセシビリティを揃えてください。
Line 68-76 の alt と figcaption が英語です。日本語ロケールでは支援技術利用時の体験が不一致になります。
Proposed fix
- <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>📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| <img src="/img/User_shares_-_distribution@500px.png" alt="User shares distribution example" /> | |
| <figcaption>User shares - Distribution</figcaption> | |
| </figure> | |
| <figure className="flex-figure"> | |
| <img src="/img/User_shares_-_access@500px.png" alt="User shares distribution example larger" /> | |
| <figcaption>User shares - Access</figcaption> | |
| <img src="/img/User_shares_-_distribution@500px.png" alt="ユーザー共有の分散設定例" /> | |
| <figcaption>ユーザー共有 - 分散</figcaption> | |
| </figure> | |
| <figure className="flex-figure"> | |
| <img src="/img/User_shares_-_access@500px.png" alt="ユーザー共有のアクセス設定例" /> | |
| <figcaption>ユーザー共有 - アクセス</figcaption> |
🤖 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 - 76, 画像要素の英語の代替テキストとキャプションが残っているため、日本語ロケール向けに統一してください:
"/img/User_shares_-_distribution@500px.png" の img alt を「ユーザー共有 -
分布の例」などの日本語に、対応する figcaption「User shares - Distribution」を「ユーザー共有 - 分布」に、
"/img/User_shares_-_access@500px.png" の img alt を「ユーザー共有 - アクセスの例（大）」など日本語に、対応する
figcaption「User shares - Access」を「ユーザー共有 - アクセス」にそれぞれ変更して、alt と figcaption
が日本語で一致するように更新してください。
| - @bonienl が **Dynamix File Manager** プラグインを webgui に統合してくれたことに感謝します | ||
| - @Squid が **GUI Search** および **Unlimited Width Plugin** プラグインを webgui に統合してくれたことに感謝します | ||
| - @ludoux（**Proxy Editor** プラグイン）および @Squid（**Community Applications** プラグイン）が、http プロキシ対応の先駆的な作業を行い、そのいくつかのアイデアが webgui に取り入れられたことに感謝します | ||
| - @ich777 のサードパーティ製ドライバープラグインの維持と、[Tailscale Docker 統合](#tailscale-integration) に感謝します |
Contributor
There was a problem hiding this comment.
Fix broken internal anchor links - fragment IDs don't match Japanese headings.
The internal anchor links use English fragment identifiers (e.g., #tailscale-integration, #add-support-for-overlay2-storage-driver) but the target headings are in Japanese. Docusaurus generates fragment IDs from the actual heading text, so Japanese headings create Japanese fragments. These links will be broken for users.
🔗 Proposed fix to update fragment references
Line 11:
-- `@ich777` のサードパーティ製ドライバープラグインの維持と、[Tailscale Docker 統合](`#tailscale-integration`) に感謝します
+- `@ich777` のサードパーティ製ドライバープラグインの維持と、[Tailscale Docker 統合](`#tailscale-統合`) に感謝しますLine 50:
-- ZFS ボリュームで **Docker data-root=directory** を使用している場合は、[overlay2 ストレージドライバーのサポートを追加](`#add-support-for-overlay2-storage-driver`) を参照してください。
+- ZFS ボリュームで **Docker data-root=directory** を使用している場合は、[overlay2 ストレージドライバーのサポートを追加](`#overlay2-ストレージドライバーのサポートを追加`) を参照してください。Line 102:
-[overlay2 ストレージドライバーを有効にした後](`#add-support-for-overlay2-storage-driver`) にロールバックする場合は、Docker ディレクトリを削除し、Docker にイメージレイヤーを再ダウンロードさせる必要があります。
+[overlay2 ストレージドライバーを有効にした後](`#overlay2-ストレージドライバーのサポートを追加`) にロールバックする場合は、Docker ディレクトリを削除し、Docker にイメージレイヤーを再ダウンロードさせる必要があります。Line 104:
-[Docker コンテナ内で Tailscale をインストールした後](`#tailscale-integration`) にロールバックする場合は、コンテナを編集し、ダミーの変更を加えて **Apply** を押し、Tailscale 統合なしでコンテナを再構築する必要があります。
+[Docker コンテナ内で Tailscale をインストールした後](`#tailscale-統合`) にロールバックする場合は、コンテナを編集し、ダミーの変更を加えて **Apply** を押し、Tailscale 統合なしでコンテナを再構築する必要があります。Line 277:
-- [Tailscale 統合](`#tailscale-integration`) を参照してください
+- [Tailscale 統合](`#tailscale-統合`) を参照してくださいAlso applies to: 50-50, 102-102, 104-104, 277-277
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 11-11: Link fragments should be valid
(MD051, link-fragments)
🤖 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.0.0.md`
at line 11, Links in the doc use English fragment IDs (e.g.,
`#tailscale-integration`, `#add-support-for-overlay2-storage-driver`) but the target
headings are in Japanese, so the anchors are broken; locate every link that
points to those English fragments (references to `#tailscale-integration`,
`#add-support-for-overlay2-storage-driver` and the others mentioned in the review)
and replace the fragment with the slug Docusaurus generates from the actual
Japanese heading text (i.e., update links like [Tailscale Docker
統合](`#tailscale-integration`) to use the Japanese-slugified anchor that matches
the heading, and do the same for the overlay2/storage-driver and the other
occurrences at the noted locations).
| - 修正: Docker ページのタブ動作の回帰を修正 | ||
| - 修正: localhost のみへのバインドに対する Docker ポートマッピング表示を修正 | ||
| - 修正: 80 番ポートで CONNECT をブロックする HTTP プロキシ使用時の厳密なプロキシ接続チェックを修正 | ||
| - 修正: rc.crond のステータスの টাইपोを修正 |
Contributor
There was a problem hiding this comment.
Text corruption: Bengali character in Japanese text.
Line 115 contains Bengali script "টাইপো" where Japanese katakana "タイポ" is expected. This appears to be an encoding error or incorrect translation that makes the text unreadable.
🔤 Proposed fix for character encoding
-- 修正: rc.crond のステータスの টাইপোを修正
+- 修正: rc.crond のステータスのタイポを修正📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - 修正: rc.crond のステータスの টাইपोを修正 | |
| - 修正: rc.crond のステータスのタイポを修正 |
🤖 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.3.0.md`
at line 115, Replace the corrupted Bengali word "টাইপো" in the release note line
referencing "rc.crond" with the correct Japanese katakana "タイポ"; update the
string "- 修正: rc.crond のステータスの টাইপোを修正" to use "タイポ" so the sentence reads
correctly as "- 修正: rc.crond のステータスのタイポを修正" and ensure the file encoding is
saved as UTF-8 to prevent further character corruption.
Comment on lines
+100
to
+103
| - ファイルシステムに適した修復ツールを使用します: | ||
| - **XFS:** `xfs_repair` | ||
| - **BTRFS:** `btrfs scrub` | ||
|
|
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
In official BTRFS docs, what is the difference between btrfs scrubandbtrfs check --repair, and which one is intended for structural filesystem repair?
💡 Result:
In official BTRFS documentation, btrfs scrub and btrfs check --repair differ significantly in purpose and capability. btrfs scrub verifies checksums of all data and metadata blocks on a mounted filesystem. It detects corruption via checksum mismatches, disk read errors, and basic errors, and repairs by copying from good replicas in replicated profiles (e.g., RAID1). It explicitly does not check or repair structural filesystem damage, acting as a checksum validator rather than a full fsck. btrfs check --repair (part of btrfs check) verifies and repairs structural integrity of an unmounted filesystem. It checks internal objects and data structures for consistency, attempting fixes with --repair (dangerous, use only with expert advice). Without --repair, it performs read-only structural checks. btrfs check --repair is intended for structural filesystem repair; btrfs scrub is not.
Citations:
- 1: https://btrfs.readthedocs.io/en/latest/Scrub.html
- 2: https://man7.org/linux/man-pages/man8/btrfs-check.8.html
- 3: https://docs.bugs.cc/btrfs/en/stable/Scrub.html
- 4: https://man7.org/linux/man-pages/man8/btrfs-scrub.8.html
- 5: https://man.archlinux.org/man/core/btrfs-progs/btrfs-scrub.8.en
- 6: https://man.archlinux.org/man/btrfs-check.8.en
btrfs scrub is not a structural filesystem repair tool.
In the context of filesystem repair guidance, btrfs scrub is misleading here. Scrub validates checksums and repairs from redundant copies, but does not address structural filesystem damage. For actual filesystem repair, use btrfs check with --repair only under careful consideration, as documented elsewhere in this guide.
Suggested fix
- ファイルシステムに適した修復ツールを使用します:
- **XFS:** `xfs_repair`
- - **BTRFS:** `btrfs scrub`
+ - **BTRFS:** `btrfs check`（必要時のみ `--repair` を検討。実行前にバックアップ推奨）📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - ファイルシステムに適した修復ツールを使用します: | |
| - **XFS:** `xfs_repair` | |
| - **BTRFS:** `btrfs scrub` | |
| - ファイルシステムに適した修復ツールを使用します: | |
| - **XFS:** `xfs_repair` | |
| - **BTRFS:** `btrfs check`（必要時のみ `--repair` を検討。実行前にバックアップ推奨） |
🤖 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`
around lines 100 - 103, The BTRFS entry currently lists "**BTRFS:** `btrfs
scrub`" which is misleading because scrub only verifies checksums and repairs
from redundant copies and does not perform structural repairs; update the
documentation entry for the BTRFS bullet (the line containing "**BTRFS:** `btrfs
scrub`") to recommend using "btrfs check" for structural repair and explicitly
warn that "btrfs check --repair" must be used only with caution (and reference
the existing guide section on repair best practices), replacing the scrub
recommendation with this corrected guidance and an explicit note about scrub's
limited role.
|
|
||
| ### 診断データの匿名化 | ||
|
|
||
| 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. |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Search for common English phrases that might indicate untranslated content
rg -n "By default|If you|It's best|You can|This will" "i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx"Repository: unraid/docs
Length of output: 435
🏁 Script executed:
# Read the file to see context around line 54
sed -n '45,65p' "i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx"Repository: unraid/docs
Length of output: 1029
Critical: Untranslated English paragraph in Japanese localization file.
Line 54 contains a full English paragraph that should be translated to Japanese. The paragraph is surrounded by Japanese content and appears in a section titled "### 診断データの匿名化" (Anonymization of diagnostic data).
The untranslated text is:
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.
This needs to be translated to Japanese to complete the localization.
🤖 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 on anonymization into Japanese and
replace the English text at the indicated location; preserve all special
placeholders and formatting such as %%Mover|mover%%, %%syslog|syslog%%, and the
bold path ***Settings → Scheduler → Mover Settings***, and maintain the
surrounding section title "### 診断データの匿名化" and tone consistent with the rest of
the file; ensure the translation conveys that diagnostics are anonymized by
default, that enabling %%Mover|mover%% logging under the specified settings will
include file details in %%syslog|syslog%%, and that enabling it should be
limited to troubleshooting mover-related issues because it may reveal file paths
and names.
Contributor
|
Caution Review failedAn error occurred during the review process. Please try again later. 📝 WalkthroughWalkthroughAdds extensive Japanese localization and many new Japanese documentation pages (API, Unraid OS guides, Connect, troubleshooting, release notes, etc.), plus whitespace/formatting normalization of inline JSX Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit
New Features
Documentation