Conversation
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
[ci skip]
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
unraid-docs | 6003989 | Commit Preview URL Branch Preview URL |
May 26 2026, 04:07 PM |
📝 WalkthroughWalkthroughAdds multilingual Linear release-note templates. Normalizes anchors, headings, and tokenized terms. Updates upgrade links in release notes. Revises troubleshooting, storage, VM, and Connect pages across de/es/fr/ja/zh. Minor content clarifications and MDX admonition syntax fixes. Changesi18n docs: anchors, links, tokens, and templates
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~30 minutes Possibly related PRs
Suggested reviewers
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
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 (7)
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx (1)
13-25:⚠️ Potential issue | 🔴 Critical | ⚡ Quick winFix unbalanced admonition fences in the intro block.
The block opens with
:::tipat Line 13 and closes at Line 16, but there is an extra closing:::at Line 25. This can break MDX parsing/rendering.🔧 Suggested fix
:::tip[New 在 Unraid 7.0 中] 查看 [%%VM|虚拟机%% 管理器功能](`#new-in-unraid-7x-vm-manager`) 部分以了解更多详情。 ::: - %%VM|虚拟机%% 克隆和快照 - 用户创建的 %%VM|虚拟机%% 模板 - 内联 XML 编辑/查看 - 高级 GPU 共享和直通功能 查看 [VM 管理器功能](`#new-in-unraid-7x-vm-manager`) 部分以了解更多详情。 - -:::🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx` around lines 13 - 25, The intro admonition opens with ":::tip" but has two closing fences; remove the extra closing ":::": keep a single matching "::: " that closes the tip block after the sentence "查看 [%%VM|虚拟机%% 管理器功能](`#new-in-unraid-7x-vm-manager`) 部分以了解更多详情。" so the ":::tip" and its single corresponding "::: " are balanced; ensure no stray "::: " remains after the list or repeated closing fence.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md (1)
274-287:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove the duplicated
overlay2subsection block.Line 274 starts a section that is repeated again at Line 281 (including body text), which creates redundant release-note content and inconsistent reading flow. Keep a single section (preferably the anchored one) and delete the duplicate block.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md` around lines 274 - 287, Delete the duplicated "### Unterstützung für overlay2 Speicher-Treiber hinzufügen" section and its body that appears twice; keep only the anchored version that contains the HTML comment {/* `#add-support-for-overlay2-storage-driver` */} so there is a single subsection with that header and its explanatory paragraphs (remove the earlier duplicate block and leave the anchored block intact).i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx (1)
37-42:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove duplicated instruction text.
The same “Mueva todos los datos…” instruction appears twice (inside the
:::importantblock and again immediately after), which reads like an accidental duplicate.Suggested fix
:::important[Before cifrando Mueva todos los datos del disco que desea cifrar a otra ubicación (otro disco en su %%array|array%%, un %%cache pool|cache-pool%%, o una copia de seguridad externa). Para obtener más detalles sobre cómo mover sus datos de manera segura, consulte [Convertir a un nuevo tipo de sistema de archivos](../../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type). ::: - -Mueva todos los datos del disco que desea cifrar a otra ubicación (otro disco en su %%array|array%%, un %%cache pool|cache-pool%%, o una copia de seguridad externa). Para obtener más detalles sobre cómo mover sus datos de manera segura, consulte [Convertir a un nuevo tipo de sistema de archivos](../../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx` around lines 37 - 42, Remove the duplicated instruction text "Mueva todos los datos del disco que desea cifrar..." by keeping it once inside the existing :::important block and deleting the repeated paragraph that immediately follows; ensure the important admonition block remains intact with its single instance of that sentence and that links/placeholders (%%array|array%%, %%cache pool|cache-pool%%) are unchanged.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx (1)
76-80:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove duplicate Windows heading.
Lines 76 and 78 both contain
**Windows 7 oder höher:**which creates unnecessary duplication. Only one label is needed before the Windows-specific instructions.📝 Proposed fix
-**Windows 7 oder höher:** - **Windows 7 oder höher:** - Rechtsklicken Sie auf `make_bootable` und wählen Sie **Als Administrator ausführen**.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx` around lines 76 - 80, Remove the duplicated heading string "**Windows 7 oder höher:**" so only one Windows-specific heading remains above the Windows instruction list; locate the two identical lines containing "**Windows 7 oder höher:**" in the block around the `make_bootable` instruction and delete the redundant one, preserving the following list item "- Rechtsklicken Sie auf `make_bootable` und wählen Sie **Als Administrator ausführen**." to keep formatting intact.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx (1)
75-79:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove duplicate Windows heading.
Lines 75 and 77 both contain
**Windows 7 以降:**which creates unnecessary duplication. Only one label is needed before the Windows-specific instructions.📝 Proposed fix
-**Windows 7 以降:** - **Windows 7 以降:** - `make_bootable` を右クリックし、**管理者として実行** を選択します。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx` around lines 75 - 79, Remove the duplicated Windows heading "**Windows 7 以降:**" so only one label remains before the Windows-specific instruction; locate the two occurrences of "**Windows 7 以降:**" in the create-your-bootable-media.mdx content (they appear consecutively in the block) and delete the redundant one, ensuring the remaining heading directly precedes the bullet "- `make_bootable` を右クリックし、**管理者として実行** を選択します。" without altering other text or formatting.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx (1)
126-128:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winLocalize the newly inserted
invalid-guidanswer text to Spanish.Lines 126-128 are in English inside a Spanish FAQ, which degrades usability for this locale.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx` around lines 126 - 128, The Spanish FAQ contains an English paragraph (the "invalid-guid" answer) that must be translated to Spanish; replace the English text between the existing paragraph that mentions %%GUID|guid%% and the two links (the block starting with "Unraid requires a boot device..." and the following "In short: Prefer drives...") with an accurate Spanish translation while preserving the placeholders %%GUID|guid%%, inline links ([Create your bootable media], [Selecting a replacement device]) and formatting; ensure the translated text conveys the same guidance about reputable retailers, second-tier brands (TeamGroup, Transcend, PNY), and avoiding generic/unbranded drives, SSDs, USB card readers, and SD adapters so the locale remains consistent.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx (1)
140-140:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix mismatched heading text for
#persistent-logs-syslog-serverin Chinese docIn
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx(line 140), the#persistent-logs-syslog-serveranchor is attached to## 访问Docker容器日志, but the section content immediately below is actually about “持久日志…syslog 服务器”. The English/Japanese “Persistent logs (syslog server)” heading text matches the anchor.🔧 Suggested fix
-## 访问Docker容器日志 {/* `#persistent-logs-syslog-server` */} +## 持久日志（syslog 服务器） {/* `#persistent-logs-syslog-server` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx` at line 140, The heading text tied to the anchor `#persistent-logs-syslog-server` is incorrect: replace the current heading "## 访问Docker容器日志" with a Chinese heading that matches the anchor/English/Japanese meaning (for example "## 持久化日志（syslog 服务器）") so the anchor, heading and section content are consistent; locate the heading line that currently reads "## 访问Docker容器日志" (the one with the `#persistent-logs-syslog-server` anchor) and update it accordingly.
🟠 Major comments (26)
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx-152-152 (1)
152-152:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore a stable anchor for the “系统准备” section.
Line 209 links to
#system-preparation, but Line 152 no longer defines that explicit anchor, so this in-page link can break.🔧 Suggested fix
-## 系统准备 +## 系统准备 {/* `#system-preparation` */}As per coding guidelines, “For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}”.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx` at line 152, Restore the missing explicit anchor for the "系统准备" heading so the in-page link to `#system-preparation` works: update the heading line that currently reads "## 系统准备" to include a Docusaurus MDX-safe comment anchor using the stable slug (e.g., change the heading definition for the "系统准备" section in this file to use the MDX comment anchor syntax like {/* `#system-preparation` */}) so the existing link to `#system-preparation` resolves correctly.i18n/fr/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx-16-16 (1)
16-16:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the explicit heading anchor to maintain cross-language linking.
Removing the
{/*#enabling-the-graphql-sandbox*/}anchor comment breaks deep links from other documentation. Without the explicit anchor, Docusaurus will auto-generate#activation-du-bac-à-sable-graphqlbased on the French heading text, breaking cross-language navigation.As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}.🔗 Restore the stable anchor
-## Activation du bac à sable GraphQL +## Activation du bac à sable GraphQL {/* `#enabling-the-graphql-sandbox` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/fr/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx` at line 16, Restore the explicit MDX-safe heading anchor for the translated heading "## Activation du bac à sable GraphQL" by adding the stable anchor comment syntax immediately after the heading (e.g., append {/* `#enabling-the-graphql-sandbox` */}) so cross-language deep links that target the original anchor `enabling-the-graphql-sandbox` continue to work; ensure the comment uses the MDX-safe form and is placed on the same line as the heading.i18n/ja/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx-124-124 (1)
124-124:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the explicit heading anchor to fix broken internal links.
Removing the
{/*#complete-workflow-example*/}anchor comment breaks the internal link at line 17 within this file. Without the explicit anchor, Docusaurus will auto-generate#完全なワークフローの例, causing the#complete-workflow-examplereference to fail.As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}.🔗 Restore the stable anchor
-## 完全なワークフローの例 +## 完全なワークフローの例 {/* `#complete-workflow-example` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/ja/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx` at line 124, Restore the explicit MDX-safe heading anchor for the "## 完全なワークフローの例" heading so internal links to "`#complete-workflow-example`" work; update the heading to include the Docusaurus MDX-safe comment anchor syntax (e.g., add {/* `#complete-workflow-example` */} immediately after the heading text) to reinstate the stable anchor used by internal references.i18n/fr/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx-124-124 (1)
124-124:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the explicit heading anchor to fix broken internal links.
Removing the
{/*#complete-workflow-example*/}anchor comment breaks the internal links at lines 17 and 19 within this file. Without the explicit anchor, Docusaurus will auto-generate#exemple-de-workflow-complet, causing the#complete-workflow-examplereferences to fail.As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}.🔗 Restore the stable anchor
-## Exemple de workflow complet +## Exemple de workflow complet {/* `#complete-workflow-example` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/fr/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx` at line 124, Restore the explicit MDX-safe heading anchor for the "## Exemple de workflow complet" heading by appending the Docusaurus MDX-safe comment anchor syntax to that heading (use the exact anchor name complete-workflow-example), i.e., change the heading to include {/* `#complete-workflow-example` */} so internal links referencing `#complete-workflow-example` (used earlier in this file) resolve correctly; ensure you place the anchor immediately after the heading text so Docusaurus preserves the stable ID.i18n/ja/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx-16-16 (1)
16-16:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the explicit heading anchor to maintain cross-language linking.
Removing the
{/*#enabling-the-graphql-sandbox*/}anchor comment breaks deep links from other documentation. Without the explicit anchor, Docusaurus will auto-generate#graphql-サンドボックスを有効にするbased on the Japanese heading text, breaking cross-language navigation.As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}.🔗 Restore the stable anchor
-## GraphQL サンドボックスを有効にする +## GraphQL サンドボックスを有効にする {/* `#enabling-the-graphql-sandbox` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/ja/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx` at line 16, Restore the explicit MDX-safe heading anchor for the "## GraphQL サンドボックスを有効にする" section by re-adding the stable anchor comment using the Docusaurus MDX-safe pattern and the anchor id "enabling-the-graphql-sandbox" so cross-language deep links continue to resolve; update the heading line that currently reads "## GraphQL サンドボックスを有効にする" to include that anchor comment in the same line.i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx-16-16 (1)
16-16:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the explicit heading anchor to maintain cross-language linking.
Removing the
{/*#enabling-the-graphql-sandbox*/}anchor comment breaks deep links from other documentation. Without the explicit anchor, Docusaurus will auto-generate#habilitación-del-sandbox-de-graphqlbased on the Spanish heading text, breaking cross-language navigation.As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}.🔗 Restore the stable anchor
-## Habilitación del sandbox de GraphQL +## Habilitación del sandbox de GraphQL {/* `#enabling-the-graphql-sandbox` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx` at line 16, Restore the explicit MDX-safe heading anchor for "Habilitación del sandbox de GraphQL" so cross-language deep links keep working: add the Docusaurus MDX comment anchor immediately after the heading text using the stable slug (e.g. {/* `#enabling-the-graphql-sandbox` */}) so the translated Spanish heading keeps the original anchor; locate the heading "Habilitación del sandbox de GraphQL" in the MDX and append the MDX-safe comment anchor right after it.i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx-124-124 (1)
124-124:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the explicit heading anchor to fix broken internal links.
Removing the
{/*#complete-workflow-example*/}anchor comment breaks the internal link at line 17 within this file. Without the explicit anchor, Docusaurus will auto-generate#ejemplo-completo-de-flujo-de-trabajo, causing the#complete-workflow-examplereference to fail.As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}.🔗 Restore the stable anchor
-## Ejemplo completo de flujo de trabajo +## Ejemplo completo de flujo de trabajo {/* `#complete-workflow-example` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx` at line 124, Restore the explicit MDX-safe anchor for the section heading "## Ejemplo completo de flujo de trabajo" so internal links to "`#complete-workflow-example`" resolve; update the heading to include the Docusaurus MDX comment-style anchor (i.e., append {/* `#complete-workflow-example` */} to the heading) to ensure the stable anchor is preserved in translated docs and avoids auto-generated IDs.i18n/de/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx-16-16 (1)
16-16:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the explicit heading anchor to maintain cross-language linking.
Removing the
{/*#enabling-the-graphql-sandbox*/}anchor comment breaks deep links from other documentation. The upstream English docs reference this anchor (seedocs/API/index.mdx:35), but without the explicit anchor, Docusaurus will auto-generate#aktivieren-der-graphql-sandboxbased on the German heading text, breaking cross-language navigation.As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}.🔗 Restore the stable anchor
-## Aktivieren der GraphQL-Sandbox +## Aktivieren der GraphQL-Sandbox {/* `#enabling-the-graphql-sandbox` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/de/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx` at line 16, Restore the explicit MDX-safe anchor for the German heading "Aktivieren der GraphQL-Sandbox" so cross-language links keep working: add the stable anchor comment using Docusaurus MDX-safe syntax immediately after the heading text (e.g. use {/* `#enabling-the-graphql-sandbox` */}) so the heading remains linkable from the upstream English docs that reference the anchor.i18n/de/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx-124-124 (1)
124-124:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the explicit heading anchor to fix broken internal links.
Removing the
{/*#complete-workflow-example*/}anchor comment breaks the internal links at lines 17 and 19 within this same file. Without the explicit anchor, Docusaurus will auto-generate#komplettes-workflow-beispiel, causing the#complete-workflow-examplereferences to fail.As per coding guidelines, for explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}.🔗 Restore the stable anchor
-## Komplettes Workflow-Beispiel +## Komplettes Workflow-Beispiel {/* `#complete-workflow-example` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/de/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx` at line 124, Restore the explicit stable heading anchor for the "Komplettes Workflow-Beispiel" heading by re-adding the MDX-safe comment anchor so internal links to `#complete-workflow-example` work; update the heading line in programmatic-api-key-management.mdx to include the anchor using Docusaurus MDX-safe comment syntax (e.g., the heading token "## Komplettes Workflow-Beispiel" should be followed by {/* `#complete-workflow-example` */}) so the existing references to complete-workflow-example at lines 17 and 19 resolve correctly.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md-13-13 (1)
13-13:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix broken internal Tailscale anchor links.
These links now target
#integration-tailscale, but the section anchor defined in this file is#tailscale-integration, so the fragments won’t resolve.Suggested fix
-- `@ich777` pour la maintenance des plugins de pilotes tiers, et pour l'intégration [Tailscale Docker](`#integration-tailscale`) +- `@ich777` pour la maintenance des plugins de pilotes tiers, et pour l'intégration [Tailscale Docker](`#tailscale-integration`) ... -Si vous revenez en arrière après avoir installé [Tailscale dans un conteneur Docker](`#integration-tailscale`), vous devrez éditer le conteneur, effectuer une modification fictive, puis **Appliquer** pour reconstruire le conteneur sans l'intégration de Tailscale. +Si vous revenez en arrière après avoir installé [Tailscale dans un conteneur Docker](`#tailscale-integration`), vous devrez éditer le conteneur, effectuer une modification fictive, puis **Appliquer** pour reconstruire le conteneur sans l'intégration de Tailscale. ... -- Voir [intégration Tailscale](`#integration-tailscale`) +- Voir [intégration Tailscale](`#tailscale-integration`)Also applies to: 112-112, 287-287
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md` at line 13, The internal Tailscale anchor is inconsistent: links use `#integration-tailscale` while the section anchor is `#tailscale-integration`; update either the link targets (replace occurrences of "`#tailscale-integration`" or "`#integration-tailscale`" to match) or rename the section anchor to "`#integration-tailscale`" so they match consistently across the document (ensure you update every occurrence of the fragment, e.g., the link text referencing Tailscale and the section heading anchor).i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md-261-261 (1)
261-261:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAnchor ID was moved to the wrong heading.
#add-support-for-overlay2-storage-drivershould remain on the overlay2 heading (Line 261), not on “其他更改” (Line 269), otherwise in-page and cross-doc links jump to the wrong section.Suggested fix
-### 添加对 overlay2 存储驱动程序的支持 +### 添加对 overlay2 存储驱动程序的支持 {/* `#add-support-for-overlay2-storage-driver` */} -### 其他更改 {/* `#add-support-for-overlay2-storage-driver` */} +### 其他更改As per coding guidelines, "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}".Also applies to: 269-269
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md` at line 261, The explicit anchor was placed on the wrong heading — move the anchor id `#add-support-for-overlay2-storage-driver` from the “其他更改” heading back to the overlay2 heading titled "添加对 overlay2 存储驱动程序的支持", and replace the raw anchor with Docusaurus MDX-safe comment syntax on that overlay2 heading (e.g., use the {/* `#add-support-for-overlay2-storage-driver` */} comment style) so in-page and cross-doc links resolve to the correct section.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md-23-23 (1)
23-23:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix malformed Markdown links (nested link syntax).
These lines use nested
[]()patterns, which breaks link rendering.Suggested fix
-> 所有其他的池在 [strverscmp()]([https://man7.org/linux/man-pages/man3/strverscmp.3.html](https://man7.org/linux/man-pages/man3/strverscmp.3.html)) 顺序中。 +> 所有其他的池按 [strverscmp()](https://man7.org/linux/man-pages/man3/strverscmp.3.html) 顺序排列。 -... 这项工作由社区成员 [`@chbmb`]([https://forums.unraid.net/profile/6219-chbmb/)、... 完成。 +... 这项工作由社区成员 [`@chbmb`](https://forums.unraid.net/profile/6219-chbmb/)、[`@bass_rock`](https://forums.unraid.net/profile/78406-bass_rock/) 和其他人完成。 -我们整合了由用户 [`@Skitals`]([https://forums.unraid.net/profile/97624-skitals/](...)) ... +我们整合了由用户 [`@Skitals`](https://forums.unraid.net/profile/97624-skitals/) 和用户 [`@ljm42`](https://forums.unraid.net/profile/61877-ljm42/) ... -由社区成员 [`@bonienl`]([https://forums.unraid.net/profile/2736-bonienl/](...)) ... +由社区成员 [`@bonienl`](https://forums.unraid.net/profile/2736-bonienl/) ... -*有关多语言支持的更多信息，[请查看我们的指南。]([https://unraid.net/blog/unraid-6-9-multi-language-support](...))* +*有关多语言支持的更多信息，请查看[我们的指南](https://unraid.net/blog/unraid-6-9-multi-language-support)。*Also applies to: 87-87, 123-123, 133-133, 141-141
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md` at line 23, The Markdown uses nested link syntax like [strverscmp()]([https://man7.org/...](https://man7.org/...)) which breaks rendering; replace each nested pattern with a normal Markdown link using the function name as the label and the raw URL as the target (e.g. change the problematic token for strverscmp() to [strverscmp()](https://man7.org/linux/man-pages/man3/strverscmp.3.html)), and apply the same fix for the other identical occurrences in this file where the nested []() pattern appears.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md-11-11 (1)
11-11:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix broken fragment links to use the existing stable anchor IDs.
These links now point to localized fragments, but the headings define stable IDs as
#tailscale-integrationand#add-support-for-overlay2-storage-driver.Suggested fix
- [Tailscale Docker 統合](`#tailscale-統合`) + [Tailscale Docker 統合](`#tailscale-integration`) - [overlay2 ストレージドライバーのサポートを追加](`#overlay2-ストレージドライバーのサポートを追加`) + [overlay2 ストレージドライバーのサポートを追加](`#add-support-for-overlay2-storage-driver`) - [overlay2 ストレージドライバーを有効にした後](`#overlay2-ストレージドライバーのサポートを追加`) + [overlay2 ストレージドライバーを有効にした後](`#add-support-for-overlay2-storage-driver`) - [Docker コンテナ内で Tailscale をインストールした後](`#tailscale-統合`) + [Docker コンテナ内で Tailscale をインストールした後](`#tailscale-integration`) - [Tailscale 統合](`#tailscale-統合`) を参照してください + [Tailscale 統合](`#tailscale-integration`) を参照してくださいAlso applies to: 50-50, 102-102, 104-104, 277-277
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md` at line 11, Links in the Japanese release notes use localized fragment anchors (e.g. "`#tailscale-統合`") that don't match the actual stable IDs; replace those localized fragments with the existing stable anchor IDs "`#tailscale-integration`" and "`#add-support-for-overlay2-storage-driver`" wherever they appear (e.g. the sentence referencing Tailscale and any links at lines noted such as 50, 102, 104, 277), ensuring the link targets exactly match the headings' IDs so fragment navigation works.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md-43-43 (1)
43-43:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the stable anchor on this heading.
Line 43 drops the explicit fragment, which risks breaking existing links that target
#bug-fixes-and-improvements.Suggested fix
-### バグ修正と改善 +### バグ修正と改善 {/* `#bug-fixes-and-improvements` */}As per coding guidelines, "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md` at line 43, Restore the explicit stable anchor for the heading "### バグ修正と改善" by adding the MDX-safe comment anchor syntax so existing links to "`#bug-fixes-and-improvements`" keep working; change the heading to include the anchor comment like: use the same heading text followed immediately by {/* `#bug-fixes-and-improvements` */} (i.e., "### バグ修正と改善 {/* `#bug-fixes-and-improvements` */}").i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx-68-68 (1)
68-68:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix admonition title syntax escape.
Line 68 uses
:::caution\[Critical], which should be:::caution[Critical]. The current escaped form risks incorrect rendering/parsing of the admonition title.Proposed fix
-:::caution\[Critical] +:::caution[Critical]🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx` at line 68, Replace the escaped admonition title token :::caution\[Critical] with the correct admonition syntax :::caution[Critical] so the admonition renders properly; locate the malformed token (:::caution\[Critical]) in the shares.mdx content and remove the backslash before the bracket to produce :::caution[Critical].i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-264-266 (1)
264-266:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRemove MBR/GPT conversion notes from WebGUI connectivity troubleshooting.
Lines 264-266 are unrelated to DNS/network diagnosis and currently replace core connection-cause bullets.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx` around lines 264 - 266, Remove the unrelated MBR/GPT conversion bullets that begin with "Le partitionnement est automatique" and the backup reminder "Sauvegardez toujours [votre périphérique de démarrage]..." from the WebGUI connectivity troubleshooting section and restore the original DNS/network connection-cause bullets they replaced; locate the block containing those exact strings in faq.mdx, delete that two-line snippet, and reinsert the original connection-cause bullet list for WebGUI connectivity (or revert this hunk to the pre-change content) so troubleshooting focuses on DNS/network diagnostics instead of partition conversion notes.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx-53-53 (1)
53-53:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAvoid duplicate
#repair-file-systemsanchors in the same page.Line 53 introduces
#repair-file-systems, but Line 64 already uses the same fragment. Keep this ID only on one heading to prevent ambiguous in-page links.Proposed fix
-### Gerätenamensgebung: Pfade und Symbole {/* `#repair-file-systems` */} +### Gerätenamensgebung: Pfade und SymboleAlso applies to: 64-64
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx` at line 53, The page contains a duplicate anchor comment {/* `#repair-file-systems` */} on the "Dateisysteme reparieren" heading; remove the redundant anchor so only one heading retains the fragment identifier `#repair-file-systems` (leave the anchor on the intended primary heading and delete the duplicate), and verify any in-page links reference the remaining anchor.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-100-100 (1)
100-100:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRemove unrelated password-reset link from the factory-reset wipe steps.
Line 100 is out of place in the destructive disk-wipe procedure and breaks the flow of critical instructions.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx` at line 100, The line containing the unrelated link "[パスワードをリセットする](../system-administration/secure-your-server/user-management.mdx#reset-your-password)" should be removed from the factory-reset disk-wipe procedure to avoid breaking the flow; locate that exact link text in the troubleshooting/faq.mdx content and delete it (or move it to the appropriate user-management section if cross-reference is needed), then run a quick read-through to ensure the destructive steps remain coherent and consecutive.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-263-265 (1)
263-265:⚠️ Potential issue | 🟠 Major | ⚡ Quick winReplace unrelated partitioning bullets in WebGUI connection troubleshooting.
Lines 263-265 discuss MBR/GPT conversion and backup, but this list is for hostname/WebGUI connectivity causes.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx` around lines 263 - 265, The two bullets about partitioning ("パーティション設定は自動です" and the paragraph about Unraid OS 6.9 partition starts and the boot device backup) are unrelated to the WebGUI/hostname troubleshooting list; remove those partition-related bullets and replace them with WebGUI/hostname-specific troubleshooting entries such as checking hostname vs IP, ensuring correct port (80/443) and protocol, verifying browser cache/CORS or mixed-content issues, confirming firewall/router/UPnP and server network settings, and verifying local hosts file or DNS resolution; update the list where the partition text appears so the items read as causes for WebGUI connectivity failure (refer to the existing bullet text starting "パーティション設定は自動です" and the following Unraid OS 6.9 paragraph to locate and replace).i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-136-138 (1)
136-138:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix heading/answer mismatches in virtualization and RAID sections.
Line 136 asks about AMD GPU VM restarts but the answer at Line 138 is about counterfeit USB/GUID.
Line 152 asks about RAID type support but Line 154 repeats GPU passthrough guidance.Also applies to: 152-155
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx` around lines 136 - 138, The answer texts are misaligned with their headings: under the heading "### Chaque fois que j'arrête ma VM Windows avec un GPU AMD assigné, elle ne parvient pas à redémarrer. Que puis-je faire ? {/* `#amd-gpu-vm-restart` */}" replace the current content about generic drives/%%GUID|guid%% with the correct AMD GPU VM restart troubleshooting text (move the GPU passthrough guidance that is currently duplicated elsewhere into this section), and for the RAID question heading (the one asking which RAID types Unraid supports) replace the duplicated GPU guidance with the proper RAID support answer; ensure you locate and update the specific headings by their exact heading text and the comment token "/* `#amd-gpu-vm-restart` */" and remove the duplicate GPU passthrough paragraph so each heading has the correct, unique answer.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-100-100 (1)
100-100:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRemove the password-reset link from the destructive wipe sequence.
Line 100 is unrelated to factory-reset disk wipe steps and interrupts the procedure in a risky section.
Proposed fix
-Consulta [Restablecer tu contraseña](../system-administration/secure-your-server/user-management.mdx#reset-your-password).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx` at line 100, The password-reset link text "Consulta [Restablecer tu contraseña](../system-administration/secure-your-server/user-management.mdx#reset-your-password)." is incorrectly embedded in the destructive factory-reset disk wipe sequence in faq.mdx; remove that line from the wipe procedure (or move it to a non-destructive section such as a general troubleshooting or user-management note) so the wipe steps remain uninterrupted and safety-critical; search for the exact link text in faq.mdx to locate and delete or relocate it and confirm surrounding headings and step numbering remain correct after removal.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx-36-36 (1)
36-36:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the explicit stable anchor on this translated heading.
Line 36 removed the explicit anchor, which can break existing links targeting
#standard-update-processin this locale.Proposed fix
-## 标准更新流程 +## 标准更新流程 {/* `#standard-update-process` */}As per coding guidelines,
For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/*#stable-anchor*/}.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx` at line 36, Restore the removed explicit stable anchor for the translated heading "## 标准更新流程" so existing links to "`#standard-update-process`" keep working; re-add the MDX-safe stable anchor immediately after that heading using Docusaurus MDX comment anchor syntax (the MDX-safe comment form for stable anchors) so the anchor is preserved in the generated HTML.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-66-68 (1)
66-68:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the missing USB-failure FAQ question and stable anchor in this section.
Line 66 currently repeats
OS と設定as a###heading, which removes the expected per-question entry (#usb-failed-restore).Proposed fix
-### OS と設定 +### ブートデバイスが故障し、バックアップがありません。構成を復元するにはどうすればよいですか？ {/* `#usb-failed-restore` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx` around lines 66 - 68, The section mistakenly repeats the "### OS と設定" heading and removed the per-question anchor; replace the duplicate heading around the USB recovery text with the original FAQ question heading and stable anchor (e.g. change the second "### OS と設定" to the USB failure FAQ heading that includes the anchor "`#usb-failed-restore`" and the appropriate Japanese question title), leaving the existing explanatory paragraph unchanged so the anchor and question entry are restored for linking and TOC generation.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-66-68 (1)
66-68:⚠️ Potential issue | 🟠 Major | ⚡ Quick winReinstate the missing “boot device failed/no backup” FAQ heading and anchor.
Line 66 repeats
OS & Configurationinstead of the expected question entry, dropping that FAQ item’s stable in-page target.Proposed fix
-### OS & Configuration +### Mon périphérique de démarrage est tombé en panne et je n’ai pas de sauvegarde. Comment restaurer ma configuration ? {/* `#usb-failed-restore` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx` around lines 66 - 68, Replace the duplicated "### OS & Configuration" FAQ entry with the missing question heading and anchor for the "Boot device failed / No backup" FAQ: add a proper level-3 heading (e.g., "### Boot device failed / No backup") and include the stable in-page anchor (same slug style used elsewhere) so links target this FAQ; ensure the explanatory paragraph about using Unraid Connect or a replacement USB and reassigning disks remains under that heading and remove the duplicate "OS & Configuration" instance.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-66-68 (1)
66-68:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRestore the missing USB-failure FAQ question and anchor.
Line 66 currently repeats the section title (
OS y Configuración) instead of the expected question entry, so this FAQ item loses its stable#usb-failed-restoretarget.Proposed fix
-### OS y Configuración +### Mi dispositivo de arranque falló y no tengo respaldo. ¿Cómo restauro mi configuración? {/* `#usb-failed-restore` */}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx` around lines 66 - 68, Replace the duplicated section title with the missing USB-failure FAQ entry by adding the question heading that provides the stable anchor "`#usb-failed-restore`" and the Spanish question text and answer; locate the repeated "OS y Configuración" heading in the file and swap it for a line like "### ¿Qué hago si la memoria USB falla? {`#usb-failed-restore`}" followed by the guidance about using Unraid Connect or a new USB flash, reinstalling Unraid, applying your license key, and reposting to the General Support forum if disk assignments are forgotten so the page regains the correct anchor and content.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx-263-265 (1)
263-265:⚠️ Potential issue | 🟠 Major | ⚡ Quick winReplace unrelated partitioning bullets in the WebGUI connectivity causes list.
Lines 263-265 describe MBR/GPT conversion, not hostname/WebGUI networking causes.
Proposed fix
-- **El particionamiento es automático**: Unraid elige automáticamente el estilo de particionamiento basado en el tamaño de la unidad: -- A partir de Unraid OS 6.9, la partición 1 comienza en 32KiB para dispositivos rotativos y en 1MiB para dispositivos no rotativos, independientemente del estilo de partición. - \-- Siempre [haz una copia de seguridad de tu dispositivo de arranque](/unraid-os/system-administration/secure-your-server/secure-your-boot-drive/#backups) antes de iniciar este proceso de conversión. +- Es posible que tu computadora y el servidor estén en subredes o VLAN distintas. +- Es posible que tu enrutador no admita resolución local de nombres de host. +- El servidor Unraid podría no estar conectado a la red o tener una configuración de red incorrecta. +- El firewall o software de seguridad podría estar bloqueando el acceso.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx` around lines 263 - 265, Remove the two unrelated partitioning bullets ("El particionamiento es automático" and the "Siempre [haz una copia de seguridad de tu dispositivo de arranque]..." line) that were mistakenly placed in the WebGUI connectivity causes list and replace them with relevant WebGUI connectivity troubleshooting bullets (e.g., hostname mismatch/incorrect URL, DNS resolution issues, firewall/port blocking, incorrect network bridge or interface assignment, and browser cache/CORS problems) so the list under the WebGUI connectivity causes section contains only networking/GUI-related causes.
🧹 Nitpick comments (2)
i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md (1)
46-46: ⚡ Quick winDeduplicate repeated anchor comment on the heading.
The same explicit anchor is declared twice on one heading. Keep a single anchor declaration to avoid parser/maintenance ambiguity.
Suggested fix
-#### Prise en charge des systèmes de fichiers Ext2/3/4, NTFS et exFAT {/* `#ext234-ntfs-and-exfat-support` */} {/* `#ext234-ntfs-and-exfat-support` */} +#### Prise en charge des systèmes de fichiers Ext2/3/4, NTFS et exFAT {/* `#ext234-ntfs-and-exfat-support` */}As per coding guidelines, "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md` at line 46, The heading "Prise en charge des systèmes de fichiers Ext2/3/4, NTFS et exFAT" contains a duplicated explicit anchor comment; remove the duplicate so only one MDX-safe anchor comment remains (e.g., keep a single {/* `#ext234-ntfs-and-exfat-support` */}) directly after the heading to avoid parser ambiguity and follow the MDX-safe anchor convention used across the docs.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md (1)
43-43: ⚡ Quick winConsider keeping the stable anchor for this heading.
Removing the explicit fragment can break existing deep links targeting this section.
Suggested fix
-### 漏洞修复和改进 +### 漏洞修复和改进 {/* `#bug-fixes-and-improvements` */}As per coding guidelines, "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md` at line 43, The heading "### 漏洞修复和改进" removed an explicit fragment and may break deep links—restore a stable anchor using Docusaurus MDX-safe comment syntax by appending the anchor comment to that heading (e.g., update the "### 漏洞修复和改进" line to include {/* `#stable-anchor` */} with a descriptive anchor name) so links remain stable across translations and builds.
| --- | ||
|
|
||
| ## 重新格式化缓存驱动器 {/* #creating-a-file-system-formatting */} | ||
| ## 重新格式化缓存驱动器 |
There was a problem hiding this comment.
Critical: Removing anchor comments breaks internal links and violates guidelines.
These changes remove explicit anchor comments from five headings. This creates the same critical issues found in the shares.mdx file:
-
Broken internal links: Line 230 references
#changing-a-file-system-type, which depends on the anchor at line 163. Removing it will break this link and likely others throughout the docs. -
Guideline violation: The coding guideline requires: "prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}" for explicit heading anchors in translated MDX files. -
Auto-generated Chinese slugs: Without explicit anchors, Docusaurus will generate slugs from the Chinese heading text instead of the stable English identifiers, breaking all cross-references.
As per coding guidelines, MDX heading anchor comments must be retained in translated docs to preserve stable fragment identifiers.
🔗 Restore all anchor comments
-## 重新格式化缓存驱动器
+## 重新格式化缓存驱动器 {/* `#reformatting-cache-drives` */}
-## 更改文件系统类型
+## 更改文件系统类型 {/* `#changing-a-file-system-type` */}
-## 转换到新的文件系统类型
+## 转换到新的文件系统类型 {/* `#converting-to-a-new-file-system-type` */}
-### 使用未分配设备插件
+### 使用未分配设备插件 {/* `#using-the-unassigned-devices-plugins` */}
-### 检查文件系统
+### 检查文件系统 {/* `#checking-a-file-system` */}Also applies to: 163-163, 187-187, 410-410, 483-483
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
at line 140, The removed MDX heading anchor comments must be restored because
they preserve stable English slugs used by cross-references; for each affected
heading (including the "重新格式化缓存驱动器" heading and the heading referenced by
"`#changing-a-file-system-type`") re-add the MDX-safe anchor comment immediately
after the heading using the original stable English slug (i.e., the same anchor
identifiers used elsewhere), following the project's MDX-safe comment pattern
for translated files; apply this fix to all five headings flagged (the ones at
the lines referenced) so internal links and auto-generated slugs remain stable.
| --- | ||
|
|
||
| ### 分配方法 {/* #allocation-method */} | ||
| ### 分配方法 |
There was a problem hiding this comment.
Critical: Removing anchor comments breaks internal links and violates guidelines.
These changes remove the explicit anchor comments {/* #allocation-method */} and {/* #split-level */} from the headings. This causes multiple issues:
-
Broken internal links: Lines 100-101 reference
#allocation-methodand#split-level, but without the explicit anchors, Docusaurus will auto-generate Chinese slugs (e.g.,#分配方法,#分级水平) from the heading text, breaking these links. -
Guideline violation: The coding guideline explicitly states: "prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}" for translated MDX files. Removing these anchors contradicts this requirement. -
Cross-reference impact: Other pages and layers in the stack may reference these stable English anchors, which will all break.
As per coding guidelines, MDX heading anchor comments should be retained in translated docs to maintain stable fragment identifiers across locales.
🔗 Restore the anchor comments
-### 分配方法
+### 分配方法 {/* `#allocation-method` */}
-### 分级水平
+### 分级水平 {/* `#split-level` */}Also applies to: 362-362
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx`
at line 283, Restore the MDX-safe anchor comments after the translated headings
so stable English fragment IDs are preserved: re-add the explicit comments `{/*
`#allocation-method` */}` and `{/* `#split-level` */}` immediately after the
corresponding headings (e.g., after `### 分配方法`) using the pattern `### Heading
{/* `#stable-anchor` */}` to match the guideline and prevent broken internal links
and cross-references.
- Purpose: restore translated MDX files on l10n_main after CodeRabbit identified structural regressions from the latest Crowdin sync. - Before: several locale files had malformed admonition syntax, duplicate or missing heading anchors, broken links, duplicated release-note blocks, and FAQ content drift. - Problem: those issues could break Crowdin parsing, remove stable anchors during reupload, or publish incorrect localized troubleshooting guidance. - Change: repair the affected German, Spanish, French, Japanese, and Chinese translation files and clean same-class Markdown defects in the PR-touched files. - How: normalize Docusaurus-safe heading anchor comments, remove duplicated anchor/comment blocks, fix admonition title syntax, restore broken fragments, and correct mistranslated FAQ/release-note content.
There was a problem hiding this comment.
♻️ Duplicate comments (1)
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (1)
140-140:⚠️ Potential issue | 🔴 Critical | ⚡ Quick winCritical: Restore all removed heading anchors.
These changes remove explicit anchor comments from five headings, creating the same critical issues documented in past review comments:
Broken internal links: Line 230 references
#changing-a-file-system-type, which depends on the anchor at line 163. Removing these anchors breaks internal links throughout the docs.Guideline violation: As per coding guidelines, translated MDX files must use "Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}" for explicit heading anchors.Auto-generated Chinese slugs: Without explicit anchors, Docusaurus generates slugs from Chinese heading text instead of stable English identifiers, breaking all cross-references.
🔗 Restore all anchor comments
-## 重新格式化缓存驱动器 +## 重新格式化缓存驱动器 {/* `#reformatting-cache-drives` */} -## 更改文件系统类型 +## 更改文件系统类型 {/* `#changing-a-file-system-type` */} -## 转换到新的文件系统类型 +## 转换到新的文件系统类型 {/* `#converting-to-a-new-file-system-type` */} -### 使用未分配设备插件 +### 使用未分配设备插件 {/* `#using-the-unassigned-devices-plugins` */} -### 检查文件系统 +### 检查文件系统 {/* `#checking-a-file-system` */}Also applies to: 163-163, 187-187, 410-410, 483-483
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx` at line 140, Restore the removed explicit MDX heading anchors by adding Docusaurus MDX-safe comment anchors to each affected heading (e.g., the heading at line 140 "重新格式化缓存驱动器" and the other headings at lines 163, 187, 410, 483) using the pattern: append {/* `#stable-english-anchor` */} to the heading so cross-references resolve (ensure the anchor for the heading referenced as `#changing-a-file-system-type` is restored exactly as that stable identifier). Make sure each anchor uses the stable English identifier used across the site (not an auto-generated Chinese slug) and apply the same change to all five headings mentioned.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Duplicate comments:
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`:
- Line 140: Restore the removed explicit MDX heading anchors by adding
Docusaurus MDX-safe comment anchors to each affected heading (e.g., the heading
at line 140 "重新格式化缓存驱动器" and the other headings at lines 163, 187, 410, 483)
using the pattern: append {/* `#stable-english-anchor` */} to the heading so
cross-references resolve (ensure the anchor for the heading referenced as
`#changing-a-file-system-type` is restored exactly as that stable identifier).
Make sure each anchor uses the stable English identifier used across the site
(not an auto-generated Chinese slug) and apply the same change to all five
headings mentioned.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 1bd8c7bd-8214-4ec0-963a-2f0068349856
📒 Files selected for processing (40)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
💤 Files with no reviewable changes (3)
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx
✅ Files skipped from review due to trivial changes (8)
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx
1 participant
Summary by CodeRabbit
Release Notes
Maintainer update