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: 15
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx (1)
219-264:⚠️ Potential issue | 🟠 MajorRemove the conflicting Nerd Tools install path from the ddrescue section
Line 250 switches to the standalone
ddrescueplugin, but Lines 262–264 still tell readers to install/enable ddrescue via Nerd Tools. These instructions conflict and should be unified.Suggested fix
-Die empfohlene Methode zur Installation von ddrescue erfolgt über das **[Nerd Tools](https://unraid.net/community/apps?q=nerd+tools#r)** Plugin (das 2022 das veraltete NerdPack ersetzt hat). +Die empfohlene Methode, ddrescue zu installieren, ist das **[ddrescue](https://ca.unraid.net/apps?q=ddrescue\&type=plugin)**-Plugin. @@ -- Installieren Sie [Nerd Tools](https://unraid-production-481d40bf.preview.craft.cloud/community/apps?q=nerd+tools#r:~:text=of%201%20App-,Nerd%20Tools,-unRaid.es) aus dem **Apps**-Tab in der Unraid %%WebGUI|web-gui%%. -- Öffnen Sie ***Einstellungen → Nerd Tools*** und aktivieren Sie **ddrescue**.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx` around lines 219 - 264, The ddrescue section currently contradicts itself by recommending the standalone ddrescue plugin ("Die empfohlene Methode, ddrescue zu installieren, ist das **ddrescue**-Plugin") but still includes two bullet points instructing readers to install/enable ddrescue via Nerd Tools; remove those two bullets and any stray references to Nerd Tools in the "Klonen einer fehlerhaften Festplatte" section so the installation instructions consistently point only to the ddrescue plugin (reference the ddrescue plugin link and the "Klonen einer fehlerhaften Festplatte" section to locate the lines to edit).
♻️ Duplicate comments (5)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md (1)
13-13:⚠️ Potential issue | 🔴 CriticalReplace classic heading IDs with MDX-safe anchor comments.
Line 13 and Line 17 still use
{#...}anchors, which should not be used in translated MDX/MD docs in this repo.Suggested edit
-### Problemas conocidos {`#known-issues`} +### Problemas conocidos {/* `#known-issues` */} ... -### Deshacer cambios {`#rolling-back`} +### Deshacer cambios {/* `#rolling-back` */}As per coding guidelines: “Do not use classic heading IDs like
### Heading {#stable-anchor}in translated MDX files; Crowdin's MDX import parser can reject them”.Also applies to: 17-17
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md` at line 13, Remove the classic heading ID syntax used in the headings (e.g., "### Problemas conocidos {`#known-issues`}") and replace it with an MDX-safe anchor comment: remove the "{`#known-issues`}" portion from the heading line and add a separate HTML comment anchor like "<!-- `#known-issues` -->" on the line directly after the heading; do the same for the other affected heading (the one using "{#...}" at line 17) so translated MDX no longer contains "{#...}" IDs.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md (1)
13-13:⚠️ Potential issue | 🔴 CriticalConvert classic heading IDs to MDX-safe comment syntax.
Lines 13 and 17 use
{#known-issues}and{#rolling-back}, which violates coding guidelines for translated MDX files. Crowdin's MDX import parser can reject these.🔧 Proposed fix
-### 已知问题 {`#known-issues`} +### 已知问题 {/* `#known-issues` */}-### 回滚 {`#rolling-back`} +### 回滚 {/* `#rolling-back` */}As per coding guidelines: "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:
### Heading {/*#stable-anchor*/}."Also applies to: 17-17
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md` at line 13, Replace the classic anchor syntax used on the translated headings with MDX-safe comment anchors: for the heading "### 已知问题 {`#known-issues`}" and the heading that uses "{`#rolling-back`}", remove the curly-brace anchors and append the MDX-safe comment anchor instead (e.g., change the heading containing "{`#known-issues`}" to "### 已知问题 {/* `#known-issues` */}" and do the same for the "{`#rolling-back`}" anchor) so Crowdin's MDX import parser accepts the file.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md (1)
13-13:⚠️ Potential issue | 🔴 CriticalClassic heading ID syntax still present—convert to MDX-safe comment syntax.
Lines 13 and 17 use
{#known-issues}and{#rolling-back}, which violates the coding guidelines for translated MDX files. Crowdin's MDX import parser can reject classic heading IDs.🔧 Proposed fix
-### Bekannte Probleme {`#known-issues`} +### Bekannte Probleme {/* `#known-issues` */}-### Rückschritte {`#rolling-back`} +### Rückschritte {/* `#rolling-back` */}As per coding guidelines: "Do not use classic heading IDs like
### Heading {#stable-anchor}in translated MDX files; Crowdin's MDX import parser can reject them. For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax:### Heading {/*#stable-anchor*/}."Also applies to: 17-17
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md` at line 13, Replace the classic heading ID syntax used on the "Bekannte Probleme" and "Zurückrollen" headings (the instances of {`#known-issues`} and {`#rolling-back`}) with MDX-safe comment anchors; locate the headings (e.g., the lines containing "### Bekannte Probleme {`#known-issues`}" and "### Zurückrollen {`#rolling-back`}") and change those trailing classic IDs to the Docusaurus MDX-safe form using a comment-style anchor (/* `#known-issues` */ and /* `#rolling-back` */) so the headings become MDX-safe without altering text.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md (1)
9-13:⚠️ Potential issue | 🟠 MajorFix escaped heading-anchor markers on Line 9 and Line 13.
{/\* ... \*/}is the escaped form and should not be used for stable heading anchors here. Use MDX-safe comment anchor syntax directly so#known-issuesand#rolling-backremain reliable.Proposed fix
-### 既知の問題 {/\* `#known-issues` \*/} +### 既知の問題 {/* `#known-issues` */} ... -### ロールバック {/\* `#rolling-back` \*/} +### ロールバック {/* `#rolling-back` */}#!/bin/bash # Verify escaped markers are gone and MDX-safe markers are present. set -euo pipefail FILE="i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md" echo "Escaped markers (should return no lines):" rg -nF '{/\* `#known-issues` \*/}' "$FILE" || true rg -nF '{/\* `#rolling-back` \*/}' "$FILE" || true echo "MDX-safe markers (should return one line each):" rg -nF '{/* `#known-issues` */}' "$FILE" rg -nF '{/* `#rolling-back` */}' "$FILE"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 the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md` around lines 9 - 13, Replace the escaped MDX comment anchors currently used on the headings "### 既知の問題" and "### ロールバック" (they use "{/\* `#known-issues` \*/}" and "{/\* `#rolling-back` \*/}") with MDX-safe Docusaurus anchors using the syntax "{/* `#known-issues` */}" and "{/* `#rolling-back` */}"; update the anchor text immediately following the "### 既知の問題" and "### ロールバック" headings so the stable anchor tokens are preserved exactly as "#known-issues" and "#rolling-back" but wrapped in the MDX-safe comment form.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md (1)
13-17:⚠️ Potential issue | 🔴 CriticalReplace classic heading IDs with MDX-safe anchor comments.
Line 13 and Line 17 still use classic
{#...}IDs, which are disallowed for translated docs in this repo.As per coding guidelines: "Do not use classic heading IDs like `### Heading {`#stable-anchor`}` in translated MDX files; Crowdin's MDX import parser can reject them".🔧 Proposed fix
-### Problèmes connus {`#known-issues`} +### Problèmes connus {/* `#known-issues` */} -### Rétrogradation {`#rolling-back`} +### Rétrogradation {/* `#rolling-back` */}🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md` around lines 13 - 17, The headings "### Problèmes connus {`#known-issues`}" and "### Rétrogradation {`#rolling-back`}" use classic `{#...}` IDs which are disallowed; remove the `{`#known-issues`}` and `{`#rolling-back`}` suffixes and add MDX-safe anchor comments immediately above each heading (for example, an HTML comment with the anchor name such as <!-- `#known-issues` --> and <!-- `#rolling-back` -->) so the headings remain the same text but use MDX-safe anchors.
🟡 Minor comments (9)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md-32-32 (1)
32-32:⚠️ Potential issue | 🟡 MinorFix mixed-language word in Spanish sentence.
Line 32 includes
специально(Russian) inside Spanish text; this should be replaced with Spanish wording (e.g., “especialmente”).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md` at line 32, Replace the stray Russian word "специально" inside the Spanish release-note sentence with the correct Spanish wording (for example "especialmente") so the line reads: "Seguridad: Incorpora correcciones upstream para CVE-2026-31430, un problema de acceso fuera de límites de Linux X.509 provocado por certificados especialmente diseñados." Locate and update the sentence containing "специально" in the release-notes content to use "especialmente" (or another appropriate Spanish synonym) and ensure punctuation and accents remain correct.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx-58-58 (1)
58-58:⚠️ Potential issue | 🟡 MinorTranslate the troubleshooting section heading to German.
Line 58 (
## Troubleshooting upgrade issues) is still English in an otherwise German page.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx` at line 58, The heading "## Troubleshooting upgrade issues" on the German page needs to be translated; locate the markdown heading string and replace it with an appropriate German translation such as "## Fehlerbehebung bei Upgrade-Problemen" (or "## Fehlerbehebung bei Aktualisierungsproblemen") so the section title matches the rest of the page language.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx-72-72 (1)
72-72:⚠️ Potential issue | 🟡 MinorTranslate remaining English troubleshooting text in the zh locale page.
Lines 72, 95, 106, and 126 still contain English sentences. Please localize them to Chinese for consistency and usability.
Also applies to: 95-95, 106-106, 126-126
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx` at line 72, Translate the remaining English troubleshooting sentences into Chinese: replace "If you have %%OVMF|ovmf%%-based %%VMs|vm%% created in older Unraid versions, you might encounter an EFI shell. You can boot the %%VM|vm%% by entering the following commands:" with an appropriate Chinese version, and similarly localize the English lines at the other occurrences (the other English sentences on this page, including the lines containing the same troubleshooting instructions and any standalone English phrases near markers like %%OVMF|ovmf%% and %%VMs|vm%%) so the entire zh locale page is fully in Chinese while preserving the special tokens (%%OVMF|ovmf%%, %%VMs|vm%%, %%VM|vm%%) exactly as-is.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdx-4-4 (1)
4-4:⚠️ Potential issue | 🟡 MinorUse typographic apostrophes consistently in French text.
Line 4 uses straight apostrophes (
s'il,n'existe) while surrounding French text uses typographic apostrophes. Please normalize punctuation for consistency.Suggested edit
-4. Créez un répertoire `previous` s'il n'existe pas déjà. +4. Créez un répertoire `previous` s’il n’existe pas déjà.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdx` at line 4, Replace the straight ASCII apostrophes in the sentence "Créez un répertoire `previous` s'il n'existe pas déjà." with French typographic apostrophes (’), so it reads "Créez un répertoire `previous` s’il n’existe pas déjà." to match the surrounding punctuation style.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md-47-47 (1)
47-47:⚠️ Potential issue | 🟡 MinorTranslate English sentences to Chinese.
Lines 47 and 65 contain English text in a Chinese translation file. These should be fully translated for consistency.
Line 47: "For details, see [Onboarding]..." should be translated to Chinese.
Line 65: "To proactively switch to TPM-based licensing, see [How can I move from flash-based licensing to TPM-based licensing]..." should be translated to Chinese.Also applies to: 65-65
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md` at line 47, Replace the two remaining English sentences in the Chinese release-notes file: change "For details, see [Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/)." to its Chinese equivalent "详情请参见 [入门指南](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/)。" and change "To proactively switch to TPM-based licensing, see [How can I move from flash-based licensing to TPM-based licensing]..." to "如需主动切换到基于 TPM 的授权，请参阅 [如何将基于闪存的授权迁移到基于 TPM 的授权]..." so both English sentences are fully translated and links remain unchanged; update the corresponding lines containing those exact English phrases.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md-47-47 (1)
47-47:⚠️ Potential issue | 🟡 MinorTranslate English sentences to Spanish.
Lines 47 and 65 contain English text in a Spanish translation file. These should be fully translated.
Line 47: "For details, see [Onboarding]..." should be translated to Spanish.
Line 65: "To proactively switch to TPM-based licensing, see [How can I move from flash-based licensing to TPM-based licensing]..." should be translated to Spanish.Also applies to: 65-65
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md` at line 47, Translate the two English sentences in the Spanish release-notes file to Spanish: replace "For details, see [Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/)." with an equivalent Spanish sentence (e.g., "Para más detalles, consulte [Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/).") and replace "To proactively switch to TPM-based licensing, see [How can I move from flash-based licensing to TPM-based licensing]..." with a Spanish version (e.g., "Para cambiar proactivamente a la licencia basada en TPM, consulte [¿Cómo puedo pasar de la licencia basada en flash a la basada en TPM]?"). Ensure the link texts are translated while preserving the markdown link targets and surrounding punctuation in the same file (the Spanish translation file containing these lines).i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md-47-47 (1)
47-47:⚠️ Potential issue | 🟡 MinorTranslate English sentences to German.
Lines 47 and 65 contain English text in a German translation file. These should be fully translated.
Line 47: "For details, see [Onboarding]..." should be translated to German.
Line 65: "To proactively switch to TPM-based licensing, see [How can I move from flash-based licensing to TPM-based licensing]..." should be translated to German.Also applies to: 65-65
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md` at line 47, Replace the two English sentences with German translations: change "For details, see [Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/)." to a German equivalent such as "Weitere Informationen finden Sie in [Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/)." and change "To proactively switch to TPM-based licensing, see [How can I move from flash-based licensing to TPM-based licensing]..." to a German equivalent such as "Um proaktiv auf TPM-basierte Lizenzierung umzusteigen, siehe [Wie kann ich von flash-basierter Lizenzierung auf TPM-basierte Lizenzierung wechseln]..."; ensure the translated text preserves the existing link targets and punctuation exactly as in the original strings.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdx-2-2 (1)
2-2:⚠️ Potential issue | 🟡 MinorKeep
sidebar_positionaligned with source ordering.Line 2 sets
sidebar_position: 9, while the source page (docs/unraid-os/download_list.mdx) is at7. This can create locale-specific sidebar drift.🔧 Suggested fix
-sidebar_position: 9 +sidebar_position: 7🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdx` at line 2, The localized document's frontmatter has sidebar_position: 9 which is out of sync with the source page (should be 7); update the localized download_list.mdx frontmatter key sidebar_position to 7 so the locale's sidebar ordering matches the source and avoid sidebar drift.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md-71-73 (1)
71-73:⚠️ Potential issue | 🟡 MinorRemove escaped asterisks to restore bold formatting in the Docker warning.
Lines 71-72 have unnecessary backslash escaping that prevents the bold emphasis from rendering. Change
\*\*Important...to**Important...on both lines.Suggested fix
-\*\*Important : Docker a été mis à jour de la version v27 (dans 7.2.4) à la version v29. Cela modifie la manière dont les adresses MAC sont attribuées aux conteneurs et les randomise. -\*\* +**Important : Docker a été mis à jour de la version v27 (dans 7.2.4) à la version v29. Cela modifie la manière dont les adresses MAC sont attribuées aux conteneurs et les randomise.**🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md` around lines 71 - 73, Remove the backslash escapes before the asterisks in the bold Docker warning so the emphasis renders; specifically, edit the Markdown lines containing "\*\*Important : Docker a été mis à jour..." to use "**Important : Docker a été mis à jour..." (and the corresponding closing "**") so the bold formatting around the Docker warning is restored.
🧹 Nitpick comments (1)
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/release-types.mdx (1)
66-66: Prefer consistent Simplified Chinese terminology for “account”.Line 66 uses
帐户repeatedly; consider standardizing to账户for locale consistency across zh docs.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/release-types.mdx` at line 66, The text on that line uses the term “帐户” inconsistently with Simplified Chinese conventions—replace every occurrence of “帐户” in the sentence (e.g., the phrases “管理 Unraid.net 帐户” and “Unraid 帐户应用”) with “账户” so the line reads using “账户” consistently; ensure the revised sentence still reads naturally and update both instances in the same sentence.
🤖 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/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Line 13: The headings "Bekannte Probleme {`#known-issues`}" and the heading with
"{`#rolling-back`}" use classic heading ID syntax; update them to MDX-safe
comment-style anchors by replacing the trailing {`#known-issues`} and
{`#rolling-back`} tokens with HTML comment anchors (e.g., <!-- `#known-issues` -->
and <!-- `#rolling-back` -->) so the headings (e.g., the "Bekannte Probleme" and
the corresponding rolling-back heading) keep the same anchors but follow the
translated MDX guidelines.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx`:
- Around line 62-128: Duplicate troubleshooting <details> blocks for "VMs zeigen
'Kann Schnittstellen-MTU nicht abrufen'", "VNC-Zugriff auf VMs funktioniert
nicht oder ist langsam", and "VM wird nicht booten (EFI-Shell erscheint)" should
be consolidated: locate each repeated <summary> text (e.g., "VMs zeigen 'Kann
Schnittstellen-MTU nicht abrufen'", "VNC-Zugriff auf VMs funktioniert nicht oder
ist langsam", "VM wird nicht booten (EFI-Shell erscheint)"), keep one complete
<details> block per topic containing the full, non-conflicting steps (include
fs0:/fs1:, cd efi/boot, bootx64.efi, the Apps reinstallation step, the VM edit →
Apply guidance, and the VNC/QXL/Cirrus/vmvga steps), remove the
duplicate/partial blocks, preserve the Unraid forum link and formatting, and
ensure the remaining blocks are ordered logically and free of repeated content.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Line 13: Replace classic heading ID syntax used on the "Problemas conocidos"
and the heading that uses the {`#rolling-back`} anchor by removing the trailing
`{`#known-issues`}` and `{`#rolling-back`}` tokens and instead add the corresponding
MDX-safe comment-style anchors immediately after each heading (use the MDX
comment form for anchors so Crowdin's MDX parser accepts them); locate the
headings that contain the exact tokens `{`#known-issues`}` and `{`#rolling-back`}`
and update them to the MDX-safe comment form right after the heading text.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx`:
- Around line 62-128: There are duplicate <details> blocks for the same issues
(summaries: "Las VMs muestran 'no se puede obtener la interfaz MTU' o errores de
red", "El acceso VNC a las VMs no funciona o es lento", and "La VM no arranca
(aparece shell EFI)") causing partial/overlapping instructions; consolidate by
keeping exactly one complete <details> block per unique summary (remove the
repeated blocks), merge the missing steps so each block contains the full,
correct remediation flow (e.g., for MTU include fs0:/fs1:/cd
efi/boot/bootx64.efi and forum link, for VNC include edit VM → Apply and network
bridge br0 steps, for EFI include editing VM, set VNC video controller to
QXL/Cirrus/vmvga and Apply), and ensure the MTU section does not include
unrelated VNC or reinstallation steps.
In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdx`:
- Line 10: The link "./updating-unraid/index.mdx#standard-update-process" uses
an English slug anchor that likely doesn't exist in the French page; update the
link in download_list.mdx to a safe target by removing the fragile anchor (use
"./updating-unraid/index.mdx") or replace it with the correct localized anchor
text if one exists; search for and edit the link string
"./updating-unraid/index.mdx#standard-update-process" and change it to the
stable target.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md`:
- Line 11: Replace the classic heading ID syntax used in the headings "###
Problèmes connus {`#known-issues`}" and the other "### ... {`#rolling-back`}" with
MDX-safe HTML comments: remove the `{#...}` from the heading text and add an
MDX-safe comment containing the anchor directly after the heading (for example
change `### Problèmes connus {`#known-issues`}` to `### Problèmes connus` followed
by a new line with `<!-- `#known-issues` -->`), do the same for the
`{`#rolling-back`}` anchor so translated MDX uses HTML comment anchors instead of
classic `{`#id`}` syntax.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Around line 47-65: Translate the two leftover English sentences into French:
replace "For details, see
[Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/)."
with a French equivalent (e.g., "Pour plus de détails, voir
[Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/).")
and replace "To proactively switch to TPM-based licensing, see [How can I move
from flash-based licensing to TPM-based
licensing](/unraid-os/troubleshooting/tpm-licensing-faq/#tpm)." with a French
equivalent (e.g., "Pour passer proactivement à une licence basée sur le TPM,
voir [Comment passer d'une licence basée sur le flash à une licence basée sur le
TPM](/unraid-os/troubleshooting/tpm-licensing-faq/#tpm)."); ensure link targets
remain unchanged and update surrounding punctuation to match French localization
style.
- Line 86: The sentence in the release notes contains a corrupted non-French
token (नियंत्रले) in the line mentioning the adjustable ZFS ARC max setting;
locate the string containing **zfs_arc_max** in the file and replace the
corrupted token with the proper French word (e.g., "contrôlé") so the sentence
reads correctly about where the setting was previously controlled.
- Around line 13-25: The translated headings "### Problèmes connus
{`#known-issues`}" and "### Rétrogradation {`#rolling-back`}" use classic anchor
syntax which Crowdin rejects; update both headings to MDX-safe anchor comments
(e.g., change the heading text to use the {/* `#stable-anchor` */} form) so they
match the Japanese release notes pattern—locate the two headings in the file and
replace "{`#known-issues`}" with "{/* `#known-issues` */}" and "{`#rolling-back`}"
with "{/* `#rolling-back` */}" respectively.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx`:
- Around line 63-128: The accordion blocks in this section are duplicated and
misassigned: consolidate and deduplicate the repeated <summary> sections ("Les
conteneurs Docker ne fonctionnent pas correctement après une mise à niveau",
"Les VMs affichent \"impossible d'obtenir l'interface MTU\" ou des erreurs
réseau", "L'accès VNC aux VMs ne fonctionne pas ou est lent", "La VM ne démarre
pas (shell EFI apparaît)") so each summary contains only the matching fix steps;
move the Docker rebuild steps (currently missing after “Voici comment :”) into
the Docker accordion, remove the unrelated Apps reinstall step from the MTU
accordion and place it under the proper Apps section, ensure EFI shell boot
commands remain only in the EFI/VM-start accordion (include fs0:/fs1:, cd
efi/boot, bootx64.efi), and delete the duplicated accordion blocks (the repeated
MTU/VNC/EFI groups) so each unique fix appears once and entirely in its correct
accordion.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md`:
- Line 11: The heading "### 既知の問題 {/\* `#known-issues` \*/}" uses escaped comment
braces causing the comment to render literally; edit this heading (and the
similar occurrence around line 15) to use MDX-safe comment syntax without
backslashes (e.g. change {/\* `#known-issues` \*/} to {/* `#known-issues` */}) so
the anchor comment is hidden as intended.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx`:
- Around line 106-113: The localized troubleshooting block contains mixed
languages (English and Devanagari) inside Japanese text; make the entire
paragraph fully Japanese. Replace the English sentence starting with "If you
have %%OVMF|ovmf%%-based %%VMs|vm%% ..." with a Japanese equivalent mentioning
OVMF/VM (e.g., "古い Unraid バージョンで作成した %%OVMF|ovmf%% ベースの %%VMs|vm%% を使用している場合、EFI
シェルが表示されることがあります。次のコマンドで起動できます："), ensure the steps referencing `fs0:`, `cd
efi/boot`, `bootx64.efi` remain as-is, change the fallback note to Japanese
(e.g., "`fs0:` で動作しない場合は `fs1:` を試してください。"), and translate the final help
sentence and link label to Japanese (e.g., "問題が続く場合は、[Unraid
フォーラム](https://forums.unraid.net/) でサポートを求めてください。").
In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdx`:
- Line 10: The deep-link "./updating-unraid/index.mdx#standard-update-process"
likely breaks because the Chinese heading doesn't declare that explicit ID; open
the target page (updating-unraid/index.mdx) and add an MDX-safe explicit anchor
to the corresponding heading using Docusaurus comment syntax, e.g. change the
heading line to include {/* `#standard-update-process` */} (for example: "###
标准更新流程 {/* `#standard-update-process` */}") so the existing link resolves
reliably.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Line 13: Replace the classic heading ID syntax by moving the anchor into an
MDX-safe HTML comment: change the heading line containing "### 已知问题
{`#known-issues`}" to "### 已知问题 <!-- `#known-issues` -->" and likewise change the
heading line containing "{`#rolling-back`}" to include the ID as an HTML comment
after the heading (e.g., "### 回滚 <!-- `#rolling-back` -->"), ensuring the visible
heading text remains unchanged and only the ID format is updated.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx`:
- Around line 62-128: The file contains duplicated <details> blocks for the same
issues (headers "VMs 显示“无法获取接口 MTU”或网络错误", "VNC 无法访问或速度慢", "VM 无法启动（出现 EFI
shell）"); remove the repeated/truncated blocks and keep exactly one complete
<details> panel per issue, preserving the full EFI shell boot steps (fs0:/fs1:,
cd efi/boot, bootx64.efi), the VNC fix (edit VM in %%WebGUI|web-gui%% and click
Apply, change bridge to br0 and default bridge in VM Manager), and the
MTU/network message (keep forum link), and remove the unrelated "应用 → 先前的应用"
app-reinstall guidance that was mistakenly included in the MTU panel; ensure
each remaining panel has a single clear summary header matching the original
Chinese titles.
---
Outside diff comments:
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx`:
- Around line 219-264: The ddrescue section currently contradicts itself by
recommending the standalone ddrescue plugin ("Die empfohlene Methode, ddrescue
zu installieren, ist das **ddrescue**-Plugin") but still includes two bullet
points instructing readers to install/enable ddrescue via Nerd Tools; remove
those two bullets and any stray references to Nerd Tools in the "Klonen einer
fehlerhaften Festplatte" section so the installation instructions consistently
point only to the ddrescue plugin (reference the ddrescue plugin link and the
"Klonen einer fehlerhaften Festplatte" section to locate the lines to edit).
---
Minor comments:
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Line 47: Replace the two English sentences with German translations: change
"For details, see
[Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/)."
to a German equivalent such as "Weitere Informationen finden Sie in
[Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/)."
and change "To proactively switch to TPM-based licensing, see [How can I move
from flash-based licensing to TPM-based licensing]..." to a German equivalent
such as "Um proaktiv auf TPM-basierte Lizenzierung umzusteigen, siehe [Wie kann
ich von flash-basierter Lizenzierung auf TPM-basierte Lizenzierung
wechseln]..."; ensure the translated text preserves the existing link targets
and punctuation exactly as in the original strings.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx`:
- Line 58: The heading "## Troubleshooting upgrade issues" on the German page
needs to be translated; locate the markdown heading string and replace it with
an appropriate German translation such as "## Fehlerbehebung bei
Upgrade-Problemen" (or "## Fehlerbehebung bei Aktualisierungsproblemen") so the
section title matches the rest of the page language.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md`:
- Line 32: Replace the stray Russian word "специально" inside the Spanish
release-note sentence with the correct Spanish wording (for example
"especialmente") so the line reads: "Seguridad: Incorpora correcciones upstream
para CVE-2026-31430, un problema de acceso fuera de límites de Linux X.509
provocado por certificados especialmente diseñados." Locate and update the
sentence containing "специально" in the release-notes content to use
"especialmente" (or another appropriate Spanish synonym) and ensure punctuation
and accents remain correct.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Line 47: Translate the two English sentences in the Spanish release-notes file
to Spanish: replace "For details, see
[Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/)."
with an equivalent Spanish sentence (e.g., "Para más detalles, consulte
[Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/).")
and replace "To proactively switch to TPM-based licensing, see [How can I move
from flash-based licensing to TPM-based licensing]..." with a Spanish version
(e.g., "Para cambiar proactivamente a la licencia basada en TPM, consulte [¿Cómo
puedo pasar de la licencia basada en flash a la basada en TPM]?"). Ensure the
link texts are translated while preserving the markdown link targets and
surrounding punctuation in the same file (the Spanish translation file
containing these lines).
In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdx`:
- Line 2: The localized document's frontmatter has sidebar_position: 9 which is
out of sync with the source page (should be 7); update the localized
download_list.mdx frontmatter key sidebar_position to 7 so the locale's sidebar
ordering matches the source and avoid sidebar drift.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Around line 71-73: Remove the backslash escapes before the asterisks in the
bold Docker warning so the emphasis renders; specifically, edit the Markdown
lines containing "\*\*Important : Docker a été mis à jour..." to use
"**Important : Docker a été mis à jour..." (and the corresponding closing "**")
so the bold formatting around the Docker warning is restored.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdx`:
- Line 4: Replace the straight ASCII apostrophes in the sentence "Créez un
répertoire `previous` s'il n'existe pas déjà." with French typographic
apostrophes (’), so it reads "Créez un répertoire `previous` s’il n’existe pas
déjà." to match the surrounding punctuation style.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md`:
- Line 47: Replace the two remaining English sentences in the Chinese
release-notes file: change "For details, see
[Onboarding](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/)."
to its Chinese equivalent "详情请参见
[入门指南](/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/)。"
and change "To proactively switch to TPM-based licensing, see [How can I move
from flash-based licensing to TPM-based licensing]..." to "如需主动切换到基于 TPM 的授权，请参阅
[如何将基于闪存的授权迁移到基于 TPM 的授权]..." so both English sentences are fully translated and
links remain unchanged; update the corresponding lines containing those exact
English phrases.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx`:
- Line 72: Translate the remaining English troubleshooting sentences into
Chinese: replace "If you have %%OVMF|ovmf%%-based %%VMs|vm%% created in older
Unraid versions, you might encounter an EFI shell. You can boot the %%VM|vm%% by
entering the following commands:" with an appropriate Chinese version, and
similarly localize the English lines at the other occurrences (the other English
sentences on this page, including the lines containing the same troubleshooting
instructions and any standalone English phrases near markers like %%OVMF|ovmf%%
and %%VMs|vm%%) so the entire zh locale page is fully in Chinese while
preserving the special tokens (%%OVMF|ovmf%%, %%VMs|vm%%, %%VM|vm%%) exactly
as-is.
---
Duplicate comments:
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md`:
- Line 13: Replace the classic heading ID syntax used on the "Bekannte Probleme"
and "Zurückrollen" headings (the instances of {`#known-issues`} and
{`#rolling-back`}) with MDX-safe comment anchors; locate the headings (e.g., the
lines containing "### Bekannte Probleme {`#known-issues`}" and "### Zurückrollen
{`#rolling-back`}") and change those trailing classic IDs to the Docusaurus
MDX-safe form using a comment-style anchor (/* `#known-issues` */ and /*
`#rolling-back` */) so the headings become MDX-safe without altering text.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md`:
- Line 13: Remove the classic heading ID syntax used in the headings (e.g., "###
Problemas conocidos {`#known-issues`}") and replace it with an MDX-safe anchor
comment: remove the "{`#known-issues`}" portion from the heading line and add a
separate HTML comment anchor like "<!-- `#known-issues` -->" on the line directly
after the heading; do the same for the other affected heading (the one using
"{#...}" at line 17) so translated MDX no longer contains "{#...}" IDs.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md`:
- Around line 13-17: The headings "### Problèmes connus {`#known-issues`}" and
"### Rétrogradation {`#rolling-back`}" use classic `{#...}` IDs which are
disallowed; remove the `{`#known-issues`}` and `{`#rolling-back`}` suffixes and add
MDX-safe anchor comments immediately above each heading (for example, an HTML
comment with the anchor name such as <!-- `#known-issues` --> and <!--
`#rolling-back` -->) so the headings remain the same text but use MDX-safe
anchors.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md`:
- Around line 9-13: Replace the escaped MDX comment anchors currently used on
the headings "### 既知の問題" and "### ロールバック" (they use "{/\* `#known-issues` \*/}"
and "{/\* `#rolling-back` \*/}") with MDX-safe Docusaurus anchors using the syntax
"{/* `#known-issues` */}" and "{/* `#rolling-back` */}"; update the anchor text
immediately following the "### 既知の問題" and "### ロールバック" headings so the stable
anchor tokens are preserved exactly as "#known-issues" and "#rolling-back" but
wrapped in the MDX-safe comment form.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md`:
- Line 13: Replace the classic anchor syntax used on the translated headings
with MDX-safe comment anchors: for the heading "### 已知问题 {`#known-issues`}" and
the heading that uses "{`#rolling-back`}", remove the curly-brace anchors and
append the MDX-safe comment anchor instead (e.g., change the heading containing
"{`#known-issues`}" to "### 已知问题 {/* `#known-issues` */}" and do the same for the
"{`#rolling-back`}" anchor) so Crowdin's MDX import parser accepts the file.
---
Nitpick comments:
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/release-types.mdx`:
- Line 66: The text on that line uses the term “帐户” inconsistently with
Simplified Chinese conventions—replace every occurrence of “帐户” in the sentence
(e.g., the phrases “管理 Unraid.net 帐户” and “Unraid 帐户应用”) with “账户” so the line
reads using “账户” consistently; ensure the revised sentence still reads naturally
and update both instances in the same sentence.
🪄 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: 41b33718-ce50-430d-a74e-82009c558b8d
📒 Files selected for processing (100)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/_category_.jsoni18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/_category_.jsoni18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/_category_.jsoni18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-command-line.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-legacy-611-612.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-modern.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/release-types.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/_category_.jsoni18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/_category_.jsoni18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/_category_.jsoni18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-command-line.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-legacy-611-612.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-modern.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/release-types.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/_category_.jsoni18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/_category_.jsoni18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/_category_.jsoni18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-command-line.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-legacy-611-612.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-modern.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/release-types.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/_category_.jsoni18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/_category_.jsoni18n/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/troubleshooting/common-issues/data-recovery.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/_category_.jsoni18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-command-line.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-legacy-611-612.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-modern.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/release-types.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/_category_.jsoni18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/_category_.jsoni18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/_category_.jsoni18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-command-line.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-legacy-611-612.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-modern.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/release-types.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
✅ Files skipped from review due to trivial changes (61)
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/category.json
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
- i18n/zh/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-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/category.json
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-legacy-611-612.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-legacy-611-612.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-legacy-611-612.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/category.json
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/category.json
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/category.json
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/category.json
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-legacy-611-612.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/category.json
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/category.json
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/category.json
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-modern.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/category.json
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/category.json
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-command-line.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/release-types.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-modern.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/category.json
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-modern.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-simplest.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-command-line.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdx
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/category.json
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/category.json
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/upgrade-modern.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdx
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/category.json
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-command-line.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/partials/manual-downgrade-command-line.mdx
🚧 Files skipped from review as they are similar to previous changes (6)
- 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/data-recovery.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/release-notes/7.2.0.md
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md
- i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.md
| 手順については、[Unraid の更新](/unraid-os/updating-unraid/) をご覧ください。[ライセンス](../../unraid-os/troubleshooting/licensing-faq.mdx#license-types--features) に関するご質問がありますか? | ||
|
|
||
| ### 既知の問題 {/* #known-issues */} | ||
| ### 既知の問題 {/\* #known-issues \*/} |
Contributor
There was a problem hiding this comment.
Remove backslashes from comment syntax.
Lines 11 and 15 use escaped comment syntax {/\* ... \*/} which causes the comment markers to display as visible text instead of being actual comments. Remove the backslashes.
🔧 Proposed fix
-### 既知の問題 {/\* `#known-issues` \*/}
+### 既知の問題 {/* `#known-issues` */}-### ロールバック {/\* `#rolling-back` \*/}
+### ロールバック {/* `#rolling-back` */}As per coding guidelines: "For explicit heading anchors in MDX, especially translated docs, prefer Docusaurus's MDX-safe comment syntax: ### Heading {/* #stable-anchor */}."
Also applies to: 15-15
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md`
at line 11, The heading "### 既知の問題 {/\* `#known-issues` \*/}" uses escaped comment
braces causing the comment to render literally; edit this heading (and the
similar occurrence around line 15) to use MDX-safe comment syntax without
backslashes (e.g. change {/\* `#known-issues` \*/} to {/* `#known-issues` */}) so
the anchor comment is hidden as intended.
Comment on lines
+106
to
+113
| If you have %%OVMF|ovmf%%-based %%VMs|vm%% created in older Unraid versions, you might encounter an EFI shell. You can boot the %%VM|vm%% by entering the following commands: | ||
|
|
||
| 1. `fs0:` と入力します。 | ||
| 2. 次に `cd efi/boot` と入力します。 | ||
| 3. 最後に `bootx64.efi` と入力します。 | ||
|
|
||
| `fs0:` で動作しない場合は、代わりに `fs1:` を試してください。問題が続く場合は、[Unraid forums](https://forums.unraid.net/) で सहायताを求めてください。 | ||
|
|
Contributor
There was a problem hiding this comment.
Localized troubleshooting text is corrupted/mixed-language.
Line 106 is still in English, and Line 112 contains the Devanagari word सहायता inside Japanese text. This should be fully Japanese for consistency and clarity.
🤖 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/updating-unraid/index.mdx`
around lines 106 - 113, The localized troubleshooting block contains mixed
languages (English and Devanagari) inside Japanese text; make the entire
paragraph fully Japanese. Replace the English sentence starting with "If you
have %%OVMF|ovmf%%-based %%VMs|vm%% ..." with a Japanese equivalent mentioning
OVMF/VM (e.g., "古い Unraid バージョンで作成した %%OVMF|ovmf%% ベースの %%VMs|vm%% を使用している場合、EFI
シェルが表示されることがあります。次のコマンドで起動できます："), ensure the steps referencing `fs0:`, `cd
efi/boot`, `bootx64.efi` remain as-is, change the fallback note to Japanese
(e.g., "`fs0:` で動作しない場合は `fs1:` を試してください。"), and translate the final help
sentence and link label to Japanese (e.g., "問題が続く場合は、[Unraid
フォーラム](https://forums.unraid.net/) でサポートを求めてください。").
| # 版本存档 | ||
|
|
||
| 需要 USB 创建工具吗？[开始使用 Unraid](https://unraid.net/getting-started) | ||
| 使用此存档查找 Unraid OS 版本的发布说明和下载链接。要更新现有服务器，请使用内置更新程序；有关步骤，请参阅[标准更新流程](./updating-unraid/index.mdx#standard-update-process)。要创建新的启动设备，请使用 [Unraid USB Creator](https://unraid.net/download)。 |
Contributor
There was a problem hiding this comment.
Fix likely broken in-page anchor to the zh update workflow heading.
Line 10 links to ./updating-unraid/index.mdx#standard-update-process, but the target heading in the Chinese page does not declare this explicit ID. This link will likely not resolve as intended.
Suggested fix (keep deep-link stable)
# i18n/zh/.../updating-unraid/index.mdx
-## 标准升级流程
+## 标准升级流程 {/* `#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 */}”.
📝 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
| 使用此存档查找 Unraid OS 版本的发布说明和下载链接。要更新现有服务器，请使用内置更新程序；有关步骤，请参阅[标准更新流程](./updating-unraid/index.mdx#standard-update-process)。要创建新的启动设备，请使用 [Unraid USB Creator](https://unraid.net/download)。 | |
| ## 标准升级流程 {/* `#standard-update-process` */} |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~10-~10: 动词的修饰一般为‘形容词（副词）+地+动词’。您的意思是否是：新"地"启动
Context: .../index.mdx#standard-update-process)。要创建新的启动设备，请使用 [Unraid USB Creator](https://un...
(wb4)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdx`
at line 10, The deep-link "./updating-unraid/index.mdx#standard-update-process"
likely breaks because the Chinese heading doesn't declare that explicit ID; open
the target page (updating-unraid/index.mdx) and add an MDX-safe explicit anchor
to the corresponding heading using Docusaurus comment syntax, e.g. change the
heading line to include {/* `#standard-update-process` */} (for example: "###
标准更新流程 {/* `#standard-update-process` */}") so the existing link resolves
reliably.
Comment on lines
+62
to
+128
| <details> | ||
| <summary><strong>升级后 Docker 容器无法正常工作</strong> - 点击以展开/收起</summary> | ||
|
|
||
| 如果您遇到类似 "layers from manifest don't match image configuration" 的错误，您可能需要重新构建您的 Docker 镜像文件。以下是方法： | ||
|
|
||
| </details> | ||
|
|
||
| <details> | ||
| <summary><strong>VMs 显示“无法获取接口 MTU”或网络错误</strong> - 点击以展开/收起</summary> | ||
|
|
||
| If you have %%OVMF|ovmf%%-based %%VMs|vm%% created in older Unraid versions, you might encounter an EFI shell. You can boot the %%VM|vm%% by entering the following commands: | ||
|
|
||
| 1. 键入 `fs0:`。 | ||
| 2. 然后键入 `cd efi/boot`。 | ||
| 3. 最后，键入 `bootx64.efi`。 | ||
| 4. 导航到 **应用** 标签页，选择 **先前的应用**，勾选要重新安装的应用并点击 **安装 xx 应用**。 | ||
|
|
||
| </details> | ||
|
|
||
| <details> | ||
| <summary><strong>VNC 无法访问或速度慢</strong> - 点击以展开/收起</summary> | ||
|
|
||
| 为了解决此问题，在 %%WebGUI|web-gui%% 中编辑 %%VM|vm%%，然后在不进行任何修改的情况下点击 **Apply**。此操作将更新机器类型为最新支持版本。 | ||
|
|
||
| 1. 前往 **VMs** 标签页并编辑每个 %%VM%%（确保启用 **高级视图**）。 | ||
| 2. 将网络桥接设置为 `br0` 并点击 **应用**。 | ||
| 3. 前往 ***设置 → VM 管理器***（在 **高级视图** 中）并将默认桥接设置为 `br0`。 | ||
|
|
||
| </details> | ||
|
|
||
| <details> | ||
| <summary><strong>VM 无法启动（出现 EFI shell）</strong> - 点击以展开/收起</summary> | ||
|
|
||
| If you have %%OVMF|ovmf%%-based %%VMs|vm%% created in older Unraid versions, you might encounter an EFI shell. You can boot the %%VM|vm%% by entering the following commands: | ||
|
|
||
| 1. 在 **VMs** 标签页编辑 %%VM%%（选择 **高级视图**）。 | ||
| 2. 将 **VNC 视频驱动程序** 设置为 **QXL**（推荐）。如果 QXL 不成功，可以尝试 **Cirrus** 或 **vmvga**。 | ||
| 3. 点击 **应用** 以保存更改。 | ||
|
|
||
| </details> | ||
|
|
||
| <details> | ||
| <summary><strong>VMs 显示“无法获取接口 MTU”或网络错误</strong> - 点击以展开/收起</summary> | ||
|
|
||
| If you have %%OVMF|ovmf%%-based %%VMs|vm%% created in older Unraid versions, you might encounter an EFI shell. You can boot the %%VM|vm%% by entering the following commands: | ||
|
|
||
| 1. 键入 `fs0:`。 | ||
| 2. 然后键入 `cd efi/boot`。 | ||
| 3. 最后，键入 `bootx64.efi`。 | ||
|
|
||
| 如果 `fs0:` 不起作用，您可以尝试 `fs1:`。如果问题仍然存在，请访问 [Unraid 论坛](https://forums.unraid.net/) 寻求帮助。 | ||
|
|
||
| </details> | ||
|
|
||
| <details> | ||
| <summary><strong>VNC 无法访问或速度慢</strong> - 点击以展开/收起</summary> | ||
|
|
||
| 为了解决此问题，在 %%WebGUI|web-gui%% 中编辑 %%VM|vm%%，然后在不进行任何修改的情况下点击 **Apply**。此操作将更新机器类型为最新支持版本。 | ||
|
|
||
| </details> | ||
|
|
||
| <details> | ||
| <summary><strong>VM 无法启动（出现 EFI shell）</strong> - 点击以展开/收起</summary> | ||
|
|
||
| If you have %%OVMF|ovmf%%-based %%VMs|vm%% created in older Unraid versions, you might encounter an EFI shell. You can boot the %%VM|vm%% by entering the following commands: | ||
|
|
||
| </details> |
Contributor
There was a problem hiding this comment.
Consolidate duplicated/truncated troubleshooting panels.
Lines 62-128 contain repeated <details> sections (MTU/VNC/EFI shell) with overlapping and incomplete content, and one MTU section includes unrelated app reinstall guidance. This will mislead users and makes the troubleshooting flow inconsistent. Please keep one complete panel per issue and remove duplicates.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdx`
around lines 62 - 128, The file contains duplicated <details> blocks for the
same issues (headers "VMs 显示“无法获取接口 MTU”或网络错误", "VNC 无法访问或速度慢", "VM 无法启动（出现 EFI
shell）"); remove the repeated/truncated blocks and keep exactly one complete
<details> panel per issue, preserving the full EFI shell boot steps (fs0:/fs1:,
cd efi/boot, bootx64.efi), the VNC fix (edit VM in %%WebGUI|web-gui%% and click
Apply, change bridge to br0 and default bridge in VM Manager), and the
MTU/network message (keep forum link), and remove the unrelated "应用 → 先前的应用"
app-reinstall guidance that was mistakenly included in the MTU panel; ensure
each remaining panel has a single clear summary header matching the original
Chinese titles.
* Purpose: publish the accumulated Docusaurus 3.10 and translation-structure cleanup on the current branch. * Before: many source and translated docs still used legacy anchors, disclosure blocks, escaped admonition labels, nested glossary links, and localized MDX/JSX breakage that made Crowdin syncs and markdown linting fragile. * Problem: the branch had the fixes only in the worktree, so Crowdin uploads could finish while the git branch still lagged behind the actual cleaned state. * Change: convert translated MDX anchors to the Docusaurus 3.10-safe comment form, flatten translated disclosure wrappers, normalize parser-hostile markdown and image/caption wrappers, repair localized API/MDX syntax, and add the missing release-types source page needed for translation sync. * Result: the branch now contains the full source and i18n cleanup that was uploaded to Crowdin, with local-only helper files left out of the commit.
- merge origin/main into l10n_main after the docs update-page reorganization - preserve the Docusaurus 3.10 upgrade and MDX heading anchor fixes from this branch - keep main's newer updating-unraid structure while resolving path and content conflicts - leave local-only .codex/ and internal/ files untracked and out of the branch
- purpose: restore real admonition components in source storage docs that were flattened during the broader i18n structure cleanup - before: short tip and caution sections in cache pool guidance and the XFS repair partial were rendered as plain bold paragraphs instead of Docusaurus admonitions - problem: the change weakened visual emphasis and dropped important formatting like the explicit Maintenance Mode reference in the parity warning - change: convert the example and use-case callouts in cache-pools back to :::tip blocks and restore the XFS parity warning to a :::caution block - result: source docs keep the intended admonition styling while translation-side syntax repairs remain unchanged
- Purpose: resolve CodeRabbit feedback across localized documentation files. - Before: translated MDX files included Crowdin-hostile heading IDs, malformed admonitions, duplicate blocks, and mixed-language artifacts. - Problem: those issues risked Crowdin import failures, broken anchors, and confusing localized docs. - New behavior: localized docs use MDX-safe anchors, cleaned admonitions, corrected duplicate sections, and fixed affected release-note/link text. - Implementation: applied focused edits across German, Spanish, French, Japanese, and Chinese i18n content while preserving existing structure.
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.
Codex update
pnpm exec remark --no-ignore --quiet --frailandgit diff --cached --check; full build was intentionally not run per repo guidance.pnpm run crowdin:upload:translations; many translations uploaded, but Crowdin exited with missing-source errors for someupdating-unraidsource paths that require a separate source push.Summary by CodeRabbit