Conversation
Contributor
📝 WalkthroughWalkthroughComprehensive multilingual documentation restructuring across German, Spanish, and French localizations. Updates API guides, Unraid Connect features, setup workflows, and system administration content through UI modernization (collapsible sections), standardized admonition syntax (escaped brackets), unified anchor formats, and reorganized content structure with tokenized references. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~35 minutes Possibly related PRs
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
|
![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 severity comments were prioritized as inline comments.
🧹 Nitpick comments (16)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (1)
451-451: Keep a stable explicit anchor on this heading.To keep localized deep links stable and consistent with the rest of this page, prefer an explicit MDX-safe anchor on this heading.
Suggested change
-### Scheduler +### Scheduler {/* `#scheduler` */}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/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx` at line 451, Add an explicit MDX-safe stable anchor to the "Scheduler" heading so localized deep links remain consistent; update the heading "Scheduler" (the line currently `### Scheduler`) to include a Docusaurus MDX-safe comment anchor, e.g. `### Scheduler {/* `#scheduler` */}`, choosing a unique, lowercase hyphenated id that matches the rest of the page.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdx (1)
3-3: Prefer Markdown headings over HTML for Docusaurus compatibility.Converting these headings to HTML
<h4>tags breaks Docusaurus's automatic features, including table-of-contents generation, auto-generated heading IDs, and deep linking. Unless there's a specific technical reason, use standard Markdown heading syntax instead.📝 Proposed fix to restore Markdown headings
-<h4>Usos comunes para las variables de entorno</h4> +#### Usos comunes para las variables de entorno-<h4>Gestionando variables de entorno en el %%WebGUI|web-gui%%</h4> +#### Gestionando variables de entorno en el %%WebGUI|web-gui%%Also applies to: 10-10
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdx` at line 3, Replace the HTML heading tag <h4>Usos comunes para las variables de entorno</h4> with a Markdown heading (e.g., using "#### Usos comunes para las variables de entorno") so Docusaurus can generate TOC, heading IDs and deep links; update the same change in the other affected occurrence referenced by "Also applies to: 10-10" to ensure consistency across the docs.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-zfs.mdx (1)
3-3: Revert HTML heading elements to Markdown syntax.The conversion of standard Markdown headings (
####) to HTML<h4>elements reduces readability and goes against MDX/Markdown best practices. Docusaurus expects Markdown headings for proper table-of-contents generation and other features.♻️ Revert to standard Markdown heading syntax
-<h4>Für %%ZFS|zfs%% Pools</h4> +#### Für %%ZFS|zfs%% Pools-<h4>Für %%ZFS|zfs%% Festplatten im Array</h4> +#### Für %%ZFS|zfs%% Festplatten im ArrayAlso applies to: 9-9
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-zfs.mdx` at line 3, Replace the HTML heading element <h4>Für %%ZFS|zfs%% Pools</h4> with a Markdown heading by reverting it to the equivalent four-hash syntax (e.g., "#### Für %%ZFS|zfs%% Pools"); locate the occurrence by searching for the literal string "Für %%ZFS|zfs%% Pools" or any <h4> tags in the file and update all instances (the comment notes a second occurrence) so Docusaurus/MDX can correctly generate TOC and follow Markdown best practices.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-read.mdx (1)
9-9: Consider using Markdown headings instead of HTML elements.Converting these headings from Markdown
####to HTML<h4>prevents the use of Docusaurus's MDX-safe anchor syntax and disables automatic heading ID generation. If explicit anchors are needed in the future, Markdown headings support the preferred comment syntax:#### Heading {/*#stable-anchor*/}.♻️ Proposed refactor to restore Markdown syntax
-<h4>Por qué son importantes las verificaciones de lectura</h4> +#### Por qué son importantes las verificaciones de lectura-<h4>Cuándo usar una verificación de lectura</h4> +#### Cuándo usar una verificación de lectura-<h4>¿Qué hacer si se encuentran errores?</h4> +#### ¿Qué hacer si se encuentran errores?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, 23-23
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-read.mdx` at line 9, Replace the raw HTML heading element "<h4>Por qué son importantes las verificaciones de lectura</h4>" with a Markdown heading (four hashes) so Docusaurus can generate stable IDs and anchors; use the MDX-safe explicit anchor comment syntax if a stable anchor is required (e.g., convert the HTML heading into "#### Por qué son importantes las verificaciones de lectura {/* `#stable-anchor` */}"). Also update the other occurrences noted (the headings at lines 15 and 23) the same way to ensure consistent automatic heading ID generation and MDX-safe anchors.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx (1)
37-37: Minor grammar polish in the recommendation lead sentence.Use “die zukünftigen Erweiterungsmöglichkeiten” instead of “die zukünftige Erweiterungsmöglichkeiten”.
🤖 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/getting-started/set-up-unraid/configure-your-array.mdx` at line 37, The lead recommendation sentence contains a grammar error: replace the phrase "die zukünftige Erweiterungsmöglichkeiten" with "die zukünftigen Erweiterungsmöglichkeiten" in the string currently reading "Diese Empfehlungen zur Datenträgerzuweisung ... die zukünftige Erweiterungsmöglichkeiten" so the adjective correctly agrees in number; update that exact sentence text in the document.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx (2)
127-128: Remove duplicated prerequisite steps from the procedure list.Lines 127-128 repeat the same prerequisites already listed in Lines 120-121. Keeping both copies will drift over time.
Proposed cleanup
-1. Installieren Sie zuerst %%Tailscale|tailscale%% auf jedem Computer, der auf Ihre Docker-Container zugreift. -2. Während das Unraid-Tailscale-Plugin für die Docker-Integration nicht zwingend erforderlich ist, wird dringend empfohlen, es zu installieren und sich auf Ihrem Unraid-Server anzumelden, um die beste Erfahrung zu erzielen. -3. Aktivieren Sie den **Use Tailscale**-Schalter. -4. Geben Sie einen **Tailscale-Hostname** für den Container ein (muss eindeutig in Ihrem Tailnet sein). +1. Aktivieren Sie den **Use Tailscale**-Schalter. +2. Geben Sie einen **Tailscale-Hostname** für den Container ein (muss eindeutig in Ihrem Tailnet sein).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx` around lines 127 - 128, The procedure contains duplicated prerequisite list items (the "Installieren Sie zuerst %%Tailscale|tailscale%% ..." and the recommendation about the Unraid-Tailscale-Plugin) that are already present earlier in the same document; remove the duplicate occurrences from the procedure so only the original prerequisites remain and ensure the remaining list preserves the same wording and formatting as the first occurrence to avoid drift. Locate the duplicated list entries in tailscale.mdx (the two consecutive numbered items) and delete the second set, leaving the initial prerequisites intact.
165-165: Avoid repeating the normal-flow instruction in Troubleshooting.Line 165 duplicates the same action already given at Line 159. The troubleshooting block should focus on failure-specific recovery steps only.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx` at line 165, Remove the duplicate normal-flow instruction from the Troubleshooting block that repeats the step starting with "Zur Authentifizierung, besuchen..." (the sentence beginning "**Anwenden** Sie Ihre Änderungen und überprüfen Sie den **Erweiterten Log** ... Klicken Sie auf den **Zur Authentifizierung, besuchen...** Link"), and leave only failure-specific recovery steps in that Troubleshooting section; ensure the primary instruction remains in the main flow (the earlier instance) and adjust any references in the Troubleshooting text so it only contains unique, diagnostic actions (e.g., log checks, restart steps, or alternative auth debugging commands).i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
397-397: Use one compound style consistently (Poolnamenvs.Pool-Namen).Line 397 uses
Poolnamen, while nearby text uses hyphenated forms. Pick one style and apply it consistently in this section.🤖 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/advanced-configurations/optimize-storage/zfs-storage.mdx` at line 397, The translation uses two inconsistent compound styles ("Poolnamen" vs "Pool-Namen"); choose the preferred style (either "Poolnamen" or "Pool-Namen") and apply it consistently throughout this section—replace the instance "Poolnamen" in the sentence "Klicken Sie auf den Poolnamen (z.B. `raptor`), um seine Konfiguration zu öffnen." to match the chosen form and update any other occurrences in nearby sentences so all references use the same compound style.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (1)
386-398: Inconsistent TabItem indentation.The
mémoireTabItem (lines 391-393) lacks indentation while siblings have 2-space indentation. This inconsistency should be fixed for maintainability.Proposed fix
<TabItem value="processeur" label="Infos CPU"> <CliCpuInfo /> </TabItem> -<TabItem value="mémoire" label="Infos Mémoire"> - <CliMemoryInfo /> -</TabItem> + <TabItem value="mémoire" label="Infos Mémoire"> + <CliMemoryInfo /> + </TabItem> <TabItem value="stockage" label="Infos de stockage"> <CliStorageInfo /> </TabItem>🤖 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/system-administration/advanced-tools/command-line-interface.mdx` around lines 386 - 398, The TabItem for value="mémoire" (rendering <CliMemoryInfo />) is misindented compared to its sibling TabItem elements; fix by aligning its indentation to match the other TabItem blocks (use the same 2-space indentation as the TabItem for "processeur" and "stockage") so the block containing <TabItem value="mémoire" label="Infos Mémoire"> and its <CliMemoryInfo /> child is indented consistently.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx (1)
214-214: Localize admonition titles in the German doc for consistency.Line 214 and Line 222 still use English titles (
Prerequisites,Warnings). Consider translating these user-facing labels.Proposed patch
-:::important\[Prerequisites] +:::important\[Voraussetzungen] ... -:::warning\[Warnings] +:::warning\[Warnungen]Also applies to: 222-222
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx` at line 214, The admonition titles are still in English: change the ":::important[Prerequisites]" admonition title to a German equivalent (e.g., "Voraussetzungen") and similarly change the ":::warning[Warnings]" title to German (e.g., "Warnungen") so the user-facing labels are localized; update the two occurrences that use the bracketed titles in the MDX (look for the literal strings ":::important[Prerequisites]" and ":::warning[Warnings]" and replace the bracketed text with the German translations).i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx (1)
214-214: Translate admonition labels to Spanish for UI-language consistency.Line 214 and Line 222 keep
Prerequisites/Warningsin English. Consider Spanish labels to match the rest of the localized page.Proposed patch
-:::important\[Prerequisites] +:::important\[Requisitos previos] ... -:::warning\[Warnings] +:::warning\[Advertencias]Also applies to: 222-222
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx` at line 214, Replace the English admonition labels with their Spanish equivalents to match the localized page: change the admonition header token :::important[Prerequisites] to :::important[Requisitos] (and similarly update :::warning[Warnings] to :::warning[Advertencias] or :::warning[Advertencia] as appropriate), ensuring the bracketed label text is translated while leaving the admonition type tokens (:::important, :::warning) intact.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx (1)
82-82: Line 82 is redundant with Line 63.
This note repeats the same requirement sentence and doesn’t add new context.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx` at line 82, The sentence "Para ejecutar %%VMs|vm%% en Unraid, tu sistema debe cumplir con los siguientes requisitos:" is duplicated; remove the redundant instance (the repeated sentence) so only the original remains, ensuring surrounding paragraphs and heading structure in overview-and-system-prep.mdx remain unchanged and no extra blank lines are introduced.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx (1)
322-324: Consider deduplicating the repeated session bullets.This list repeats the same points already covered in the previous tip block; trimming or replacing with a distinct caution would improve flow.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx` around lines 322 - 324, The three bullets ("Si regularmente tienes sesiones de terminal abiertas.", "Para prevenir que las sesiones SSH olvidadas retrasen el apagado.", "Para limpieza automatizada durante el apagado.") are duplicate of the previous tip block; remove or replace them with a single distinct caution that summarizes the intent (e.g., a one-line note about closing SSH sessions before shutdown or enabling automatic session cleanup) so the content isn’t repetitive—edit the unclean-shutdowns.mdx bullet list to either delete those three lines or consolidate them into one unique cautional sentence.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md (1)
43-43: Add a stable heading anchor using MDX-safe syntax for consistency with other translated release notes.The heading should include an explicit anchor to maintain URL stability:
Suggested fix
-### Fehlerbehebungen und Verbesserungen +### Fehlerbehebungen und Verbesserungen {/* `#bug-fixes-and-improvements` */}This aligns with the coding guideline for translated documentation: prefer Docusaurus's MDX-safe comment syntax for explicit heading anchors.
🤖 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/6.12.6.md` at line 43, The heading "### Fehlerbehebungen und Verbesserungen" lacks an explicit MDX-safe anchor; add an MDX-safe comment anchor immediately before that heading (using Docusaurus/MDX comment syntax) containing a stable, URL-friendly slug (e.g., a lowercase, hyphenated anchor derived from "Fehlerbehebungen und Verbesserungen") so the translated release notes have a consistent, explicit heading anchor.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
257-257: Trim repeated RAM-limit wording and fix French ordinal typography.Line 257 repeats the same sentence from Line 248 almost verbatim; consider a shorter reminder here. Also prefer
un huitième(or1/8e) over1/8ème.Suggested edit
-Unraid limite automatiquement %%ZFS|zfs%% à utiliser une portion raisonnable de la RAM de votre système (généralement 1/8ème de la RAM totale). Cela permet à %%ZFS|zfs%% de bien fonctionner sans affecter les conteneurs Docker, les %%VMs|vm%% ou l'OS Unraid. +Rappel : Unraid limite automatiquement l’ARC de %%ZFS|zfs%% à environ un huitième de la RAM totale, pour préserver les ressources Docker, %%VMs|vm%% et système.🤖 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/advanced-configurations/optimize-storage/zfs-storage.mdx` at line 257, The paragraph duplicates the prior sentence about RAM limits for %%ZFS|zfs%% and uses the non‑preferred ordinal "1/8ème"; replace the duplicated sentence with a concise reminder (one short sentence) referencing %%ZFS|zfs%% and %%VMs|vm%% only as needed, and change "1/8ème" to either "un huitième" or "1/8e" (e.g., "Unraid limite automatiquement %%ZFS|zfs%% à environ un huitième de la RAM afin de préserver les conteneurs Docker, les %%VMs|vm%% et l'OS.").i18n/fr/docusaurus-plugin-content-docs/current/API/partials/manage-api-keys-gui.mdx (1)
5-5: Optional FR wording polish for formal docs tone.Line 5 could read slightly more formally as
autorisationsinstead ofpermissions.Proposed wording tweak
-- Gérer les permissions et rôles. +- Gérer les autorisations et rôles.🤖 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/API/partials/manage-api-keys-gui.mdx` at line 5, Replace the informal French word "permissions" with the more formal "autorisations" in the string "Gérer les permissions et rôles." so it reads "Gérer les autorisations et rôles."; locate that exact phrase in the document (the line containing "Gérer les permissions et rôles.") and update it accordingly.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 66ca8cf9-2e28-40b2-ba80-b4cc3567b7b5
📒 Files selected for processing (300)
i18n/de/docusaurus-plugin-content-docs/current/API/cli.mdxi18n/de/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/de/docusaurus-plugin-content-docs/current/API/index.mdxi18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdxi18n/de/docusaurus-plugin-content-docs/current/API/partials/get-started-v72.mdxi18n/de/docusaurus-plugin-content-docs/current/API/partials/manage-api-keys-gui.mdxi18n/de/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/_category_.jsoni18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/partials/flash-drive-selection-guidance.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/partials/webgui-boot-device-labels.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/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/system-administration/_category_.jsoni18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/linux.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/macos.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/windows.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdxi18n/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/system-administration/secure-your-server/secure-your-outgoing-comms.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/_category_.jsoni18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/tpm-licensing-faq.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/_category_.jsoni18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/adding-disks-to-array.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.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/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-read.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-xfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-zfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-between-pools-using-mover.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-command-line.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/managing-and-customizing-containers.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdxi18n/es/docusaurus-plugin-content-docs/current/API/cli.mdxi18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/es/docusaurus-plugin-content-docs/current/API/index.mdxi18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdxi18n/es/docusaurus-plugin-content-docs/current/API/partials/get-started-v72.mdxi18n/es/docusaurus-plugin-content-docs/current/API/partials/manage-api-keys-gui.mdxi18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/_category_.jsoni18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/partials/flash-drive-selection-guidance.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/partials/webgui-boot-device-labels.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/system-administration/_category_.jsoni18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/linux.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/macos.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/windows.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdxi18n/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/system-administration/secure-your-server/secure-your-outgoing-comms.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdxi18n/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/security-fundamentals.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.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/system-administration/secure-your-server/wireguard.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/_category_.jsoni18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/tpm-licensing-faq.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/_category_.jsoni18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/adding-disks-to-array.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/overview.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/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/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-read.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-xfs.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-zfs.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-between-pools-using-mover.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-command-line.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/managing-and-customizing-containers.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdxi18n/fr/docusaurus-plugin-content-docs/current/API/cli.mdxi18n/fr/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/fr/docusaurus-plugin-content-docs/current/API/index.mdxi18n/fr/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdxi18n/fr/docusaurus-plugin-content-docs/current/API/partials/get-started-v72.mdxi18n/fr/docusaurus-plugin-content-docs/current/API/partials/manage-api-keys-gui.mdxi18n/fr/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/_category_.jsoni18n/fr/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/partials/flash-drive-selection-guidance.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/partials/webgui-boot-device-labels.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/system-administration/_category_.jsoni18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/linux.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/macos.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/windows.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdxi18n/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/system-administration/secure-your-server/secure-your-outgoing-comms.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/_category_.jsoni18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/tpm-licensing-faq.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/updating-unraid/index.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/_category_.jsoni18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/adding-disks-to-array.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/overview.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/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/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-read.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-xfs.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-zfs.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-between-pools-using-mover.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-command-line.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/managing-and-customizing-containers.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/cli.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/index.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/partials/get-started-v72.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/partials/manage-api-keys-gui.mdxi18n/ja/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/_category_.jsoni18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/download_list.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/partials/flash-drive-selection-guidance.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/partials/webgui-boot-device-labels.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.4.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.5.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.mdi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/_category_.jsoni18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/linux.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/macos.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/partials/wake-on-lan/windows.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdxi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/_category_.jsoni18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
| ### Speicher | ||
|
|
||
| #### ZFS RAIDZ-Erweiterung {/* #raidz-expansion */} | ||
| #### ZFS RAIDZ-Erweiterung {/\* #raidz-expansion \*/} |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Check if the file exists and examine lines around 30 and 46
if [ -f "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md" ]; then
echo "=== File found, checking line count ==="
wc -l "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md"
echo -e "\n=== Context around line 30 ==="
sed -n '28,32p' "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md" | cat -A
echo -e "\n=== Context around line 46 ==="
sed -n '44,48p' "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md" | cat -A
else
echo "File not found"
fiRepository: unraid/docs
Length of output: 826
🏁 Script executed:
# Search for other malformed heading anchors in the file
echo "=== All lines with malformed heading anchors {/\* ... \*/} ==="
grep -n '{/\\' "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md"
echo -e "\n=== All lines with correct heading anchors {/* ... */} ==="
grep -n '{/\*' "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md" | grep -v '{/\\' || echo "None found"Repository: unraid/docs
Length of output: 336
Fix malformed heading anchor syntax to comply with Docusaurus MDX standards for translated docs.
Lines 30 and 46 contain escaped forward slashes and asterisks ({/\* ... \*/}) which breaks MDX rendering. Use the proper MDX-safe comment syntax: {/* #anchor */}.
Suggested fix
-#### ZFS RAIDZ-Erweiterung {/\* `#raidz-expansion` \*/}
+#### ZFS RAIDZ-Erweiterung {/* `#raidz-expansion` */}
-#### Ext2/3/4-, NTFS- und exFAT-Unterstützung {/\* `#ext234-ntfs-and-exfat-support` \*/}
+#### Ext2/3/4-, NTFS- und exFAT-Unterstützung {/* `#ext234-ntfs-and-exfat-support` */}🤖 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.0.md`
at line 30, The heading "ZFS RAIDZ-Erweiterung" uses an MDX comment with escaped
characters ({/\* `#raidz-expansion` \*/}) which breaks rendering; locate that
heading and the second occurrence of the same anchor (both instances referencing
`#raidz-expansion`) and replace the malformed comment with the MDX-safe form {/*
`#raidz-expansion` */} so the anchor comment is valid in translated MDX files.
| %%Tailscale|tailscale%% Exit-Nodes bieten eine sichere und moderne Möglichkeit, den ausgehenden Datenverkehr Ihres Unraid-Servers über ein anderes Gerät in Ihrem %%Tailnet|tailnet%% zu leiten. Diese Einrichtung bietet die Sicherheit eines %%VPN|vpn-tunnel%% und nutzt zugleich das benutzerfreundliche Mesh-Netzwerk von %%Tailscale|tailscale%%. Sie eignet sich daher ideal für Benutzer, die verschlüsselten ausgehenden Datenverkehr ohne die Komplexität herkömmlicher %%VPN|vpn-tunnel%%s wünschen. | ||
|
|
||
| :::tip[Wann Sie Tailscale Exit-Nodes verwenden sollten] | ||
| :::tip[When Sie Tailscale Exit-Nodes verwenden sollten] |
Contributor
There was a problem hiding this comment.
Fix language mixing in German translation.
The tip header mixes English ("When") with German text. The German word "Wann" should be used instead to maintain language consistency in this German localization file.
🌍 Proposed fix for the translation
-:::tip[When Sie Tailscale Exit-Nodes verwenden sollten]
+:::tip[Wann Sie Tailscale Exit-Nodes verwenden sollten]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| :::tip[When Sie Tailscale Exit-Nodes verwenden sollten] | |
| :::tip[Wann Sie Tailscale Exit-Nodes verwenden sollten] |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx`
at line 79, The tip header string ":::tip[When Sie Tailscale Exit-Nodes
verwenden sollten]" mixes English and German; update that literal to use German
"Wann" instead of "When" so it reads ":::tip[Wann Sie Tailscale Exit-Nodes
verwenden sollten]" (preserve the surrounding tip block syntax and
capitalization exactly as in the original).
Comment on lines
+152
to
+155
| Appliance-%%VMs|vm%% sind dafür ausgelegt, bestimmte Software auszuführen, und erlauben oft nicht die Installation zusätzlicher Pakete, wie des %%QEMU|qemu%% %%Guest Agent|guest-agent%%. Das bedeutet, dass kein Ruhezustand verfügbar ist, sodass Sie sich auf eine korrekte Timeout-Konfiguration verlassen müssen. | ||
|
|
||
| ::: | ||
|
|
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx | sed -n '145,160p'Repository: unraid/docs
Length of output: 1301
Remove the duplicated paragraph and orphaned admonition closer.
Line 150 closes the :::note block. The duplicate paragraph at line 152 plus the standalone ::: at line 154 leaves this section structurally unbalanced and will break MDX rendering.
Proposed fix
- Appliance-%%VMs|vm%% sind dafür ausgelegt, bestimmte Software auszuführen, und erlauben oft nicht die Installation zusätzlicher Pakete, wie des %%QEMU|qemu%% %%Guest Agent|guest-agent%%. Das bedeutet, dass kein Ruhezustand verfügbar ist, sodass Sie sich auf eine korrekte Timeout-Konfiguration verlassen müssen.
-
- :::📝 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
| Appliance-%%VMs|vm%% sind dafür ausgelegt, bestimmte Software auszuführen, und erlauben oft nicht die Installation zusätzlicher Pakete, wie des %%QEMU|qemu%% %%Guest Agent|guest-agent%%. Das bedeutet, dass kein Ruhezustand verfügbar ist, sodass Sie sich auf eine korrekte Timeout-Konfiguration verlassen müssen. | |
| ::: |
🤖 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/unclean-shutdowns.mdx`
around lines 152 - 155, Remove the duplicated paragraph "Appliance-%%VMs|vm%%
sind dafür ausgelegt..." and the orphaned closing admonition marker ":::",
ensuring the original :::note block is properly closed only once; locate the
duplicated text and the standalone ":::", delete the duplicate paragraph and the
extra ":::", and leave the correctly paired :::note ... ::: structure intact so
MDX rendering is balanced.
Comment on lines
+16
to
+21
| :::note[Connect el acceso al panel es diferente] | ||
|
|
||
| Iniciar sesión en el [panel de Unraid Connect](https://connect.myunraid.net/) **no** expone por sí mismo tu %%WebGUI|web-gui%% a Internet. El acceso al panel usa una conexión iniciada por el servidor con acceso restringido a la API para las funciones compatibles de Connect. **Unraid Connect Remote Access** es una función अलग? | ||
|
|
||
| ::: | ||
|
|
Contributor
There was a problem hiding this comment.
Critical: Hindi text artifact in Spanish document.
Line 18 contains Hindi text that appears to be a translation error or placeholder:
**Unraid Connect Remote Access** es una función अलग?
"अलग?" is Hindi for "different?" — this is clearly not intended content and needs to be removed or replaced with proper Spanish text.
Suggested fix
-**Unraid Connect Remote Access** es una función अलग?
+**Unraid Connect Remote Access** es una función separada que expone tu %%WebGUI|web-gui%% a Internet.📝 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
| :::note[Connect el acceso al panel es diferente] | |
| Iniciar sesión en el [panel de Unraid Connect](https://connect.myunraid.net/) **no** expone por sí mismo tu %%WebGUI|web-gui%% a Internet. El acceso al panel usa una conexión iniciada por el servidor con acceso restringido a la API para las funciones compatibles de Connect. **Unraid Connect Remote Access** es una función अलग? | |
| ::: | |
| :::note[Connect el acceso al panel es diferente] | |
| Iniciar sesión en el [panel de Unraid Connect](https://connect.myunraid.net/) **no** expone por sí mismo tu %%WebGUI|web-gui%% a Internet. El acceso al panel usa una conexión iniciada por el servidor con acceso restringido a la API para las funciones compatibles de Connect. **Unraid Connect Remote Access** es una función separada que expone tu %%WebGUI|web-gui%% a Internet. | |
| ::: |
🤖 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-connect/remote-access.mdx`
around lines 16 - 21, Remove the stray Hindi token "अलग?" from the note block
that currently reads "**Unraid Connect Remote Access** es una función अलग?" and
replace it with the correct Spanish phrasing (e.g., remove the word or change to
"diferente?" or better wording appropriate to the note). Update the note block
marked by :::note[Connect el acceso al panel es diferente] so the sentence with
the bold title "**Unraid Connect Remote Access**" is valid Spanish and contains
no non-Spanish characters or stray words.
| - Mejora: mejores ajustes predeterminados para los vdevs ZFS RAIDZ | ||
|
|
||
| #### Soporte para Ext2/3/4, NTFS y exFAT {/* #ext234-ntfs-and-exfat-support */} | ||
| #### Soporte para Ext2/3/4, NTFS y exFAT {/\* #ext234-ntfs-and-exfat-support \*/} |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Check if the file exists and view the content around line 45
if [ -f "i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md" ]; then
echo "=== File exists. Content around line 45 ==="
sed -n '40,50p' "i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md" | cat -n
else
echo "File not found at specified path"
fiRepository: unraid/docs
Length of output: 1111
🏁 Script executed:
# List the actual directory structure to verify the path
find i18n -type f -name "7.2.0.md" 2>/dev/null | head -20Repository: unraid/docs
Length of output: 455
🏁 Script executed:
# Search for any anchor syntax issues in MDX/MD files
rg '{/\\\*' --type md --type mdx -n 2>/dev/null | head -20Repository: unraid/docs
Length of output: 37
🏁 Script executed:
# Look for the specific anchor pattern in the entire i18n/es directory
rg 'ext234-ntfs-and-exfat-support' i18n/es/ -n 2>/dev/nullRepository: unraid/docs
Length of output: 481
🏁 Script executed:
# Check if there are any build configuration files that indicate how .md files are processed
find . -maxdepth 2 -name "docusaurus.config.*" -o -name "sidebars.*" | head -10Repository: unraid/docs
Length of output: 92
🏁 Script executed:
# Search for any build error logs or references to this specific anchor issue
rg 'render.*crash|build.*blocker|ext234-ntfs' -i 2>/dev/null | head -20Repository: unraid/docs
Length of output: 1779
🏁 Script executed:
# Check how other translated files in the i18n directory handle anchors
rg '### .+ {/\*.*\*/}' i18n/ --type md --type mdx | head -10Repository: unraid/docs
Length of output: 163
🏁 Script executed:
# Look for the correct anchor syntax being used elsewhere in the codebase
rg '### .+ {/\* #' --type md --type mdx | head -10Repository: unraid/docs
Length of output: 159
🏁 Script executed:
# Examine docusaurus.config.ts to understand how translated files are processed
head -50 docusaurus.config.tsRepository: unraid/docs
Length of output: 2337
🏁 Script executed:
# Check if the main English file has similar anchor syntax
rg 'ext234-ntfs-and-exfat-support' docs/ --type md --type mdx -B 1Repository: unraid/docs
Length of output: 83
🏁 Script executed:
# Look at how many files have this malformed escape pattern across the codebase
rg '{/\\\*.*\\\*/}' --type md --type mdx -cRepository: unraid/docs
Length of output: 145
🏁 Script executed:
# Check the original English docs file for the same section
find docs/ -name "7.2.0.md" -o -name "7.2.0.mdx" | xargs cat 2>/dev/null | grep -A 5 -B 5 "ext234-ntfs-and-exfat"Repository: unraid/docs
Length of output: 37
🏁 Script executed:
# Look at the actual English file and get the line with the anchor
rg 'Ext2/3/4.*NTFS.*exFAT' docs/ -A 2 -B 2Repository: unraid/docs
Length of output: 1899
🏁 Script executed:
# Count how many translated files have the escaped slash pattern
find i18n -name "7.2.0.md" | xargs grep -l '/\\\*' | wc -lRepository: unraid/docs
Length of output: 57
🏁 Script executed:
# Check what anchor syntax patterns exist in the translated docs
find i18n -name "*.md" -o -name "*.mdx" | xargs grep -h '{.*#[a-z]' | sort | uniq -c | sort -rn | head -15Repository: unraid/docs
Length of output: 704
Fix malformed MDX anchor syntax: remove backslash escaping.
Line 45 uses {/\* #ext234-ntfs-and-exfat-support \*/} with incorrectly escaped comment delimiters. Per coding guidelines for translated MDX/MD files, use {/* #ext234-ntfs-and-exfat-support */} without escaping.
Suggested fix
-#### Soporte para Ext2/3/4, NTFS y exFAT {/\* `#ext234-ntfs-and-exfat-support` \*/}
+#### Soporte para Ext2/3/4, NTFS y exFAT {/* `#ext234-ntfs-and-exfat-support` */}This same issue exists in multiple translated files (ja, fr, de). The malformed anchor breaks the intended anchor target, affecting cross-file links to this section.
📝 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
| #### Soporte para Ext2/3/4, NTFS y exFAT {/\* #ext234-ntfs-and-exfat-support \*/} | |
| #### Soporte para Ext2/3/4, NTFS y exFAT {/* `#ext234-ntfs-and-exfat-support` */} |
🤖 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.0.md`
at line 45, Replace the malformed MDX anchor `{/\*
`#ext234-ntfs-and-exfat-support` \*/}` with the correct JSX comment anchor `{/*
`#ext234-ntfs-and-exfat-support` */}` in the "#### Soporte para Ext2/3/4, NTFS y
exFAT" header (search for the exact anchor string
"#ext234-ntfs-and-exfat-support"); apply the same replacement in the
corresponding translated files (ja, fr, de) so the anchor target is valid for
cross-file links.
| 1. Reinstale los controladores %%VirtIO|virtio%% desde el ISO. | ||
| 2. Busque actualizaciones de Windows, que pueden proporcionar controladores más recientes. | ||
| 3. Visite la página de [Controladores Red Hat VirtIO](https://docs.fedoraproject.org/en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/) para las últimas versiones. | ||
| ::: |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify admonition fence balance in the reviewed file (read-only).
file="$(fd -i 'vm-conversion-and-migration.mdx' | head -n1)"
python - <<'PY'
from pathlib import Path
import sys
p = Path("""'"$file"'""")
if not p.exists():
print("File not found")
sys.exit(1)
stack = 0
for i, line in enumerate(p.read_text(encoding="utf-8").splitlines(), 1):
s = line.strip()
if s.startswith(":::"):
if s == ":::": stack -= 1
else: stack += 1
print(f"{i}: {s} -> stack={stack}")
print(f"Final stack={stack}")
print("Expected: final stack == 0 and never negative.")
PYRepository: unraid/docs
Length of output: 70
🏁 Script executed:
find . -name "*vm-conversion-and-migration*" -type fRepository: unraid/docs
Length of output: 799
🏁 Script executed:
sed -n '450,470p' ./i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx | cat -nRepository: unraid/docs
Length of output: 965
🏁 Script executed:
python - <<'PY'
from pathlib import Path
import sys
p = Path("./i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx")
if not p.exists():
print("File not found")
sys.exit(1)
lines = p.read_text(encoding="utf-8").splitlines()
stack = 0
issues = []
for i, line in enumerate(lines, 1):
s = line.strip()
if s.startswith(":::"):
if s == ":::":
stack -= 1
else:
stack += 1
if i >= 450 and i <= 470:
print(f"{i}: {s} -> stack={stack}")
if stack < 0:
issues.append(f"Line {i}: Stack goes negative (closing fence without opening)")
print(f"\nFinal stack={stack}")
if stack > 0:
print(f"ERROR: {stack} unclosed admonition fence(s)")
elif stack < 0:
print(f"ERROR: More closing fences than opening fences")
else:
print("OK: All admonition fences are balanced")
if issues:
print("\nIssues found:")
for issue in issues:
print(f" {issue}")
PYRepository: unraid/docs
Length of output: 290
Remove the unmatched admonition fence at line 460.
The standalone ::: is an unpaired closing fence without a corresponding opening fence, which breaks MDX parsing/rendering.
🛠️ Proposed fix
- :::📝 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
| ::: |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx`
at line 460, Remove the stray closing admonition fence ":::” that appears alone
(the unmatched delimiter) so the MDX has paired admonition fences; locate the
standalone ":::” token in the document (the lone closing admonition fence) and
delete it so all admonition blocks are properly opened and closed.
Comment on lines
+117
to
+121
| 1. Presione **Windows + R** para abrir el cuadro de diálogo Ejecutar, escriba `services.msc` y presione Enter. | ||
| 2. Haga clic en **Elija qué hacen los botones de encendido**. | ||
| 3. Haga doble clic en **Windows Search**, cambie el **Tipo de inicio** a **Deshabilitado** y haga clic en **OK**. | ||
| 4. Desmarque **Activar inicio rápido** en **Configuraciones de apagado**. | ||
| 5. Haga clic en **Guardar cambios**. |
Contributor
There was a problem hiding this comment.
Instructions are incorrect and mixed from different procedures.
The steps in this <details> section are inconsistent with the stated goal of disabling Windows Search indexing:
- Step 1 opens
services.msc(correct for disabling Windows Search) - Step 2 says "Haga clic en Elija qué hacen los botones de encendido" — this is a power options instruction, not applicable in Services
- Step 4 mentions "Desmarque Activar inicio rápido" — this belongs to the Fast Startup/Hibernation procedure, not Windows Search
It appears instructions from multiple procedures were incorrectly merged.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx`
around lines 117 - 121, Las instrucciones mezclan procedimientos diferentes;
actualice la sección para que sólo describa cómo deshabilitar el servicio
"Windows Search" desde servicios.msc: elimine la línea errónea "Haga clic en
Elija qué hacen los botones de encendido" y la línea sobre "Activar inicio
rápido", y reemplácelas por pasos claros: abrir Ejecutar → escribir services.msc
→ localizar "Windows Search" → hacer doble clic en "Windows Search" → cambiar
"Tipo de inicio" a "Deshabilitado" → detener el servicio si está en ejecución →
hacer clic en "OK" (puede omitir "Guardar cambios" ya que no aplica aquí).
Asegúrese de que las referencias a "Windows Search" y "services.msc" permanecen
en el texto para localizar el fragmento.
Comment on lines
138
to
+149
| #### Habilitar modo de energía de alto rendimiento | ||
|
|
||
| Windows Search indexing continuously scans your %%virtual machine|vm%%'s storage to catalog files for faster search results. However, on a %%virtual machine|vm%%, this can cause unnecessary disk I/O, slow down performance, and increase wear on your physical storage, especially SSDs in your [cache pool](../manage-storage/cache-pools.mdx). | ||
| La indexación de Windows Search analiza continuamente el almacenamiento de su %%virtual machine|vm%% para catalogar archivos y ofrecer resultados de búsqueda más rápidos. Sin embargo, en una %%virtual machine|vm%%, esto puede causar E/S de disco innecesaria, ralentizar el rendimiento y aumentar el desgaste de su almacenamiento físico, especialmente de los SSD de su [cache pool](../manage-storage/cache-pools.mdx). | ||
|
|
||
| #### Cómo desactivar la indexación de Windows | ||
| <details> | ||
| <summary><strong>Cómo desactivar la indexación de Windows</strong> - Haz clic para expandir/colapsar</summary> | ||
|
|
||
| 1. Presione **Windows + R** para abrir el cuadro de diálogo Ejecutar, escriba `services.msc` y presione Enter. | ||
| 2. En la ventana de Servicios, desplácese hacia abajo, haga clic derecho en **Windows Search** y luego seleccione **Detener**. | ||
| 3. Haga doble clic en **Windows Search**, cambie el **Tipo de inicio** a **Deshabilitado** y haga clic en **OK**. | ||
| 1. Presione **Windows + R** para abrir el cuadro de diálogo Ejecutar, escriba `services.msc` y presione Enter. | ||
| 2. En la ventana de Servicios, desplácese hacia abajo, haga clic derecho en **Windows Search** y luego seleccione **Detener**. | ||
| 3. Haga doble clic en **Windows Search**, cambie el **Tipo de inicio** a **Deshabilitado** y haga clic en **OK**. | ||
|
|
||
| </details> |
Contributor
There was a problem hiding this comment.
Heading does not match content.
The heading at line 138 is "#### Habilitar modo de energía de alto rendimiento" (Enable High Performance Power Mode), but the content at lines 140-148 describes disabling Windows Search indexing. This is a content mismatch that will confuse readers.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx`
around lines 138 - 149, The section heading "#### Habilitar modo de energía de
alto rendimiento" does not match the content which explains how to disable
Windows Search indexing (see the details block with "<summary><strong>Cómo
desactivar la indexación de Windows</strong>"). Fix by replacing the heading
text with a matching heading such as "#### Desactivar la indexación de Windows"
(or, if you intended to document high‑performance power mode instead, replace
the details block with steps for enabling high performance power mode); update
the heading string "#### Habilitar modo de energía de alto rendimiento" or the
details content accordingly so they are consistent.
Comment on lines
+206
to
+229
| #### Cómo habilitar el modo de energía de alto rendimiento | ||
|
|
||
| Si estás teniendo problemas con el audio HDMI en una %%VM|vm%% de Windows que usa %%GPU passthrough|gpu-passthrough%% (lo cual ocurre frecuentemente con tarjetas gráficas NVIDIA), habilitar las Interrupciones Señaladas por Mensaje (MSI) podría ayudar. MSI mejora la gestión de interrupciones para los dispositivos pasantes. | ||
|
|
||
| #### Cómo habilitar las interrupciones MSI | ||
| <details> | ||
| <summary><strong>Cómo habilitar las interrupciones MSI</strong> - Haz clic para expandir/colapsar</summary> | ||
|
|
||
| :::caution | ||
| Haz una copia de seguridad de tu %%VM|vm%% antes de realizar cualquier cambio en el registro. Las modificaciones incorrectas pueden causar inestabilidad en el sistema. | ||
| ::: | ||
| :::caution | ||
| Haz una copia de seguridad de tu %%VM|vm%% antes de realizar cualquier cambio en el registro. Las modificaciones incorrectas pueden causar inestabilidad en el sistema. | ||
| ::: | ||
|
|
||
| 1. **Verifique la capacidad de MSI:** | ||
| - Inicie su %%VM|vm%% con %%GPU passthrough|gpu-passthrough%% habilitado. | ||
| - Accede a Unraid a través de [WebTerminal o SSH](../../system-administration/advanced-tools/command-line-interface.mdx). | ||
| - Ejecute el comando `lspci -v -s 01:00.0` (reemplace `01:00.0` con la dirección PCI de su GPU). | ||
| - Busque la línea: `Capacidades: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+`. | ||
| 1. **Verifique la capacidad de MSI:** | ||
| - Inicie su %%VM|vm%% con %%GPU passthrough|gpu-passthrough%% habilitado. | ||
| - Accede a Unraid a través de [WebTerminal o SSH](../../system-administration/advanced-tools/command-line-interface.mdx). | ||
| - Ejecute el comando `lspci -v -s 01:00.0` (reemplace `01:00.0` con la dirección PCI de su GPU). | ||
| - Busque la línea: `Capacidades: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+`. | ||
|
|
||
| 2. **Habilitar MSI en Windows:** | ||
| - Si MSI muestra `Enable-`, sigue [la guía de Microsoft](https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/enabling-message-signaled-interrupts-in-the-registry) o usa la [herramienta de modo MSI](https://forums.guru3d.com/threads/windows-line-based-vs-message-signaled-based-interrupts-msi-tool.378044/) para modificar la configuración del registro de Windows. | ||
| - Reinicie el %%VM|vm%% después de hacer los cambios. | ||
| 2. **Habilitar MSI en Windows:** | ||
| - Si MSI muestra `Enable-`, sigue [la guía de Microsoft](https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/enabling-message-signaled-interrupts-in-the-registry) o usa la [herramienta de modo MSI](https://forums.guru3d.com/threads/windows-line-based-vs-message-signaled-based-interrupts-msi-tool.378044/) para modificar la configuración del registro de Windows. | ||
| - Reinicie el %%VM|vm%% después de hacer los cambios. | ||
|
|
||
| Para obtener más detalles técnicos, consulta [explicación de las interrupciones VFIO](https://vfio.blogspot.com/2014/09/vfio-interrupts-and-how-to-coax-windows.html). | ||
| Para obtener más detalles técnicos, consulta [explicación de las interrupciones VFIO](https://vfio.blogspot.com/2014/09/vfio-interrupts-and-how-to-coax-windows.html). | ||
|
|
||
| </details> |
Contributor
There was a problem hiding this comment.
Heading does not match section content.
Line 206 has heading "#### Cómo habilitar el modo de energía de alto rendimiento" (How to enable high performance power mode), but the actual content starting at line 208 discusses HDMI audio troubleshooting with MSI interrupts. This appears to be a copy-paste error during content reorganization.
🧰 Tools
🪛 LanguageTool
[style] ~214-~214: Se recomienda emplear una alternativa al verbo comodín ‘realizar’.
Context: ...a de seguridad de tu %%VM|vm%% antes de realizar cualquier cambio en el registro. Las mo...
(REALIZAR)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx`
around lines 206 - 229, The section heading "#### Cómo habilitar el modo de
energía de alto rendimiento" does not match the content about enabling MSI for
HDMI audio/GPU passthrough; change the heading to accurately reflect the content
(e.g., "#### Cómo habilitar las interrupciones MSI para solucionar HDMI/Audio en
VM con GPU passthrough") or move the MSI content under the correct "MSI"
heading; update the heading text in the file so it aligns with the MSI
troubleshooting steps and ensure any anchor or links referencing the old heading
are adjusted accordingly.
| Unraid supports %%ZFS|zfs%% for any storage pool. You can create a new %%ZFS|zfs%% pool, import one from another system, or use Unraid’s unique hybrid %%ZFS|zfs%% setup: add a %%ZFS|zfs%%-formatted disk directly to the Unraid %%array|array%% (not a pool) and combine %%ZFS|zfs%% features with Unraid’s %%parity|parity%% protection. | ||
|
|
||
| :::info[Example] | ||
| :::info\[Example] |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cat -n i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx | sed -n '30,40p'Repository: unraid/docs
Length of output: 878
🏁 Script executed:
cat -n i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx | sed -n '345,355p'Repository: unraid/docs
Length of output: 1285
🌐 Web query:
Docusaurus MDX admonition syntax title brackets
💡 Result:
In Docusaurus MDX, the admonition syntax uses square brackets [] for the optional title. The format is :::type[title]content:::. For example: md :::note[Your Title with some Markdown syntax!] Some content with some Markdown syntax. ::: Titles support Markdown syntax like bold, italics, and inline code. This renders with the specified title above the content. Without brackets, no custom title is used (defaults to the type label like "note"). This works in both Markdown and MDX files.
Citations:
- 1: https://docusaurus.io/docs/markdown-features/admonitions
- 2: https://docusaurus.io/docs/3.3.2/markdown-features/admonitions
- 3: https://master--docusaurus-2.netlify.app/docs/markdown-features/admonitions
- 4: https://docusaurus.io/docs/2.x/markdown-features/admonitions
- 5: http://docusaurus.io/pt-BR/docs/next/markdown-features/admonitions
Fix malformed admonition headers to prevent MDX parsing errors.
Line 35 uses an escaped opening bracket (:::info\[Example]) which breaks the title syntax. Line 351 has unbalanced brackets within the title (:::tip[Planning [en avant]). Both must follow Docusaurus admonition format: :::type[title] with balanced brackets.
Suggested fixes
-:::info\[Example]
+:::info[Exemple]-:::tip[Planning [en avant]
+:::tip[Planification en avance]🧰 Tools
🪛 LanguageTool
[typographical] ~35-~35: Une espace est requise.
Context: ...raid’s %%parity|parity%% protection. :::info[Example] Vous pouvez utiliser les...
(DEUX_POINTS_ESPACE)
🤖 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/advanced-configurations/optimize-storage/zfs-storage.mdx`
at line 35, Fix the malformed MDX admonitions: replace the escaped opening
bracket `:::info\[Example]` with a proper admonition header `:::info[Example]`,
and fix the unbalanced nested brackets in `:::tip[Planning [en avant]` by
removing or converting the inner square brackets (e.g., `:::tip[Planning (en
avant)]` or `:::tip[Planning — en avant]`) so the title uses balanced square
brackets; ensure both `:::info[...]` and `:::tip[...]` follow the exact
`:::type[title]` format with no unescaped/extra square brackets.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
unraid-docs | b162a00 | Apr 24 2026, 06:16 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit
Documentation Updates
UI/UX Improvements