Conversation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThis pull request updates internationalized documentation across German, Spanish, French, and Chinese locales. Key changes include terminology standardization (replacing "flash device" with "boot device"), new documentation pages for internal boot FAQs and boot device security, release notes for Unraid 7.2.4 and 7.3.0-beta.1, and comprehensive onboarding documentation for new Unraid 7.3+ features. Most changes are content-focused with consistent formatting and anchor adjustments throughout. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes ✨ 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: 31
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
♻️ Duplicate comments (4)
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx (4)
144-144: Anchor removal follows the same link-stability risk as noted above.🤖 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/using-unraid-to/create-virtual-machines/vm-setup.mdx` at line 144, The note "Anchor removal follows the same link-stability risk as noted above." is duplicated under the "## 高级选项" heading; remove the duplicate instance so the guidance appears only once (keep the original earlier occurrence), updating the content under the "## 高级选项" section in vm-setup.mdx to eliminate the repeated sentence.
29-29: Anchor removal follows the same link-stability risk as noted above.🤖 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/using-unraid-to/create-virtual-machines/vm-setup.mdx` at line 29, The change removed or altered the anchor for the section titled "## 创建您自己的虚拟机", which creates the same link-stability risk noted earlier; restore the original anchor (or add an explicit HTML anchor/id) for the "创建您自己的虚拟机" heading so existing links remain stable, and ensure any anchor text/ID matches the previous value or follows the project's anchor naming convention.
459-459: Anchor removal follows the same link-stability risk as noted above.🤖 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/using-unraid-to/create-virtual-machines/vm-setup.mdx` at line 459, The comment is duplicated under the "### 扩展vDisk" heading; remove the duplicate note so the anchor-stability warning appears only once (or consolidate both instances into a single, clearly worded sentence) and ensure the remaining text references the anchor/link stability risk consistently; update the content under "### 扩展vDisk" to keep only the single, consolidated warning about link-stability risk.
424-424: Anchor removal follows the same link-stability risk as noted above.🤖 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/using-unraid-to/create-virtual-machines/vm-setup.mdx` at line 424, The heading "### 停留在UEFI shell" currently lacks a stable anchor which risks link breakage when headings are edited; add an explicit, stable anchor for this section (e.g., an MDX/HTML id like `#uefi-shell`) so links remain stable even if the visible heading text changes, by inserting a persistent anchor immediately before or as part of the "停留在UEFI shell" heading (reference the heading text "停留在UEFI shell" to locate where to add the anchor).
🧹 Nitpick comments (3)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md (1)
26-26: Use a consistent arrow glyph in UI paths.Line 26 uses
->while Line 62 uses→. Consider standardizing (prefer→) for consistency.Also applies to: 62-62
🤖 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/6.12.5.md` at line 26, Replace the inconsistent ASCII arrow in the UI path with the preferred glyph: change "Herramientas -> Syslog" (the "->" occurrence in the string "'espejo syslog en flash', ver syslog-previous en Herramientas -> Syslog, y en diagnósticos") to use the Unicode arrow "→" to match the other occurrence on the page; ensure any other "->" occurrences in this markdown file are similarly normalized to "→" for consistency.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx (1)
68-68: Consider using an ASCII slug for the tabvalueattribute.Tab
values can be persisted into URL search parameters; when that feature is enabled, accented characters in the value will be percent-encoded in the URL (e.g.?tab=pr%C3%A9f%C3%A9r%C3%A9). Using an ASCII slug keeps URLs clean and matches the idiomatic pattern from Docusaurus examples.♻️ Proposed refactor
- <TabItem value="préféré" label="Méthode préférée" default> + <TabItem value="preferred" label="Méthode préférée" default>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx` at line 68, The TabItem uses a non-ASCII value "préféré" which will be percent-encoded in URLs; change the value to an ASCII slug (e.g. value="prefere" or "preferred") while keeping label="Méthode préférée" and the default attribute as-is, and update any code or links that reference the old value ("préféré") to the new ASCII slug so persisted tab parameters and examples continue to work cleanly.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-xfs.mdx (1)
12-12: English text in German locale file.Line 12 is in English while the rest of the file (lines 1–8) remains in German. If this is intentional (e.g., standardizing parity warnings in English across all locales), it would be helpful to add a brief comment or ensure consistency. Otherwise, this should be translated to German.
🤖 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-check-cli-xfs.mdx` at line 12, The sentence "Running this command on an %%array|array%% disk outside of **%%Maintenance Mode|maintenance-mode%%** will invalidate %%parity|parity%%." is in English inside a German locale file; either translate it to German or annotate why it must remain English. Replace that line with a German translation that preserves the placeholders/formatting (keep %%array|array%%, %%Maintenance Mode|maintenance-mode%% as bold where present, and %%parity|parity%%) or add a brief inline comment stating the English parity warning is intentionally left untranslated for consistency.
ℹ️ Review info
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (221)
i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.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/optimize-storage/zfs-storage.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/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/what-is-unraid.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.mdi18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.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/system-administration/advanced-tools/command-line-interface.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/maintain-and-update/partials/backup-using-webgui.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.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/security-fundamentals.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/common-issues/data-recovery.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-btrfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-xfs.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/diagnostics/capture-diagnostics-and-logs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.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/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/customize-your-experience/multi-language-support.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.jsoni18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.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/fs-check-cli-btrfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-xfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-zfs.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-btrfs.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/move-array-to-pool.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.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/partials/troubleshoot-device-limit.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.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/community-applications.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/programmatic-api-key-management.mdxi18n/es/docusaurus-plugin-content-docs/current/API/upcoming-features.mdxi18n/es/docusaurus-plugin-content-docs/current/contribute/style-guide.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-os/advanced-configurations/optimize-storage/zfs-storage.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.mdi18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/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/maintain-and-update/partials/backup-using-webgui.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.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/wireguard.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/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/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/customize-your-experience/multi-language-support.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.jsoni18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.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/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/shares.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.mdi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/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/maintain-and-update/changing-the-flash-device.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/troubleshooting/faq.mdxi18n/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/vm-setup.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.jsoni18n/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/removing-disks-from-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/shares.mdxi18n/zh/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.mdi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.mdi18n/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/system-administration/secure-your-server/securing-your-connection.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.jsoni18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
💤 Files with no reviewable changes (1)
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
Comment on lines
+48
to
+49
| ::: | ||
|
|
Contributor
There was a problem hiding this comment.
Stray ::: will break page rendering.
The :::important block is already closed at line 46. The new ::: at line 48 is an orphaned closing directive with no matching opening. In Docusaurus MDX v2 this will either fail to build or silently wrap all subsequent content into an unclosed admonition, corrupting the rest of the page.
🐛 Proposed fix — remove the stray directive
:::
-
-:::
### Herunterladen und entpacken🤖 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/create-your-bootable-media.mdx`
around lines 48 - 49, There is an orphaned closing admonition directive (":::")
after the already-closed ":::important" block that will break MDX rendering;
remove the stray ":::" so the ":::important" block has a single matching closing
delimiter and verify no other unmatched ":::"/admonition markers remain in the
same file (look for the ":::important" opening/closing and the extra standalone
":::").
...-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
Show resolved
Hide resolved
Comment on lines
+21
to
25
| Einige Nutzer berichten von sporadischen Problemen mit Time Machine und Netzlaufwerken auf macOS Sequoia. Sollte es bei Ihnen zu Backup-Fehlern kommen, ziehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid.net/community/apps?q=time+machine#r) als Alternative zu nutzen. | ||
|
|
||
| :::caution[Before Sie beginnen] | ||
| Stellen Sie sicher, dass **%%SMB|samba%%** im %%WebGUI|web-gui%% aktiviert ist: | ||
|
|
Contributor
There was a problem hiding this comment.
Duplicated paragraph and unclosed admonition block.
Line 21 duplicates the macOS Sequoia warning from line 17. Lines 23–24 open a :::caution[Before Sie beginnen] block that is never closed before the ## Erstellen einer Time Machine-Freigabe heading on line 26. This will cause the heading and subsequent content to render inside the caution block.
Additionally, line 23 has a mixed-language title (Before Sie beginnen).
Proposed fix — remove duplicated paragraph and unclosed block
-Einige Nutzer berichten von sporadischen Problemen mit Time Machine und Netzlaufwerken auf macOS Sequoia. Sollte es bei Ihnen zu Backup-Fehlern kommen, ziehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid.net/community/apps?q=time+machine#r) als Alternative zu nutzen.
-
-:::caution[Before Sie beginnen]
-Stellen Sie sicher, dass **%%SMB|samba%%** im %%WebGUI|web-gui%% aktiviert ist:
-
## Erstellen einer Time Machine-Freigabe📝 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
| Einige Nutzer berichten von sporadischen Problemen mit Time Machine und Netzlaufwerken auf macOS Sequoia. Sollte es bei Ihnen zu Backup-Fehlern kommen, ziehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid.net/community/apps?q=time+machine#r) als Alternative zu nutzen. | |
| :::caution[Before Sie beginnen] | |
| Stellen Sie sicher, dass **%%SMB|samba%%** im %%WebGUI|web-gui%% aktiviert ist: | |
| ## Erstellen einer Time Machine-Freigabe |
🧰 Tools
🪛 LanguageTool
[grammar] ~21-~21: Entferne ein Leerzeichen
Context: ...ommen, ziehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~21-~21: Entferne ein Leerzeichen
Context: ...iehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid.net/com...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 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/apple-time-machine.mdx`
around lines 21 - 25, Remove the duplicated macOS Sequoia warning paragraph (the
repeated sentence about sporadic Time Machine issues) and fix the unclosed
admonition by changing the mixed-language title token `:::caution[Before Sie
beginnen]` to a German title like `:::caution[Bevor Sie beginnen]` and add a
closing `:::` before the `## Erstellen einer Time Machine-Freigabe` heading so
the caution block is properly terminated.
Comment on lines
+28
to
+29
| :::Vorsicht[Bevor Sie beginnen] | ||
|
|
Contributor
There was a problem hiding this comment.
Invalid admonition keyword :::Vorsicht.
Docusaurus admonition keywords must be in English (note, tip, info, caution, danger, warning, important). :::Vorsicht will not render as an admonition block. This should be :::caution.
Proposed fix
-:::Vorsicht[Bevor Sie beginnen]
+:::caution[Bevor Sie beginnen]📝 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
| :::Vorsicht[Bevor Sie beginnen] | |
| :::caution[Bevor Sie beginnen] | |
🤖 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/apple-time-machine.mdx`
around lines 28 - 29, Replace the non-English admonition keyword used in the MDX
admonition header (the line starting with ":::Vorsicht") with the supported
Docusaurus keyword ":::caution" so the block renders as an admonition; update
the admonition starter in the file's content to use "caution" instead of
"Vorsicht" (no other structural changes needed).
Comment on lines
+104
to
+106
| ## **Verhinderung von versehentlichem Verlust:** Reduzieren Sie das Risiko von Datenverlusten beim Formatieren oder Ersetzen von Geräten. | ||
|
|
||
| Wenn Ihr Speicherbedarf wächst, möchten Sie vielleicht Ihren Cache-Pool durch das Hinzufügen zusätzlicher Festplatten erweitern. Dieser Prozess ermöglicht Ihnen, sowohl die Kapazität als auch die Leistung zu erhöhen und gleichzeitig den Datenschutz durch RAID-Konfigurationen zu gewährleisten. | ||
| Um eine Festplatte zu einem %%BTRFS|btrfs%%-Pool hinzuzufügen: |
Contributor
There was a problem hiding this comment.
Bullet-point text incorrectly used as H2 heading.
Line 104 uses a bullet-point description as a section heading:
## **Verhinderung von versehentlichem Verlust:** Reduzieren Sie das Risiko von Datenverlusten beim Formatieren oder Ersetzen von Geräten.
This was originally a list item (see line 58) and has been incorrectly promoted to a heading during the Crowdin sync. This will break the page's table of contents and section structure. It should be replaced with the intended heading (likely something like ## Festplatten zu einem Pool hinzufügen / "Adding disks to a pool").
🤖 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/cache-pools.mdx`
around lines 104 - 106, The current H2 "## **Verhinderung von versehentlichem
Verlust:** Reduzieren Sie das Risiko von Datenverlusten beim Formatieren oder
Ersetzen von Geräten." was incorrectly promoted from a bullet and breaks the
TOC; replace this heading with the intended section title (e.g., "## Festplatten
zu einem Pool hinzufügen" or "## Hinzufügen von Festplatten zu einem Pool") and
restore the original bullet text as a list item where it belongs (the
descriptive sentence currently following the heading "Um eine Festplatte zu
einem %%BTRFS|btrfs%%-Pool hinzuzufügen:" should remain as supporting copy, not
the H2). Ensure the new H2 matches locale style and keeps the subsequent
instructional content under it.
Comment on lines
+178
to
+190
| :::tip[Optimizing 硬盘数量 | ||
|
|
||
| 这提供了两个主要优点： | ||
|
|
||
| **优化配置示例：** | ||
|
|
||
| - **RAIDZ1**: 3、5 或 9 个硬盘（数据盘 = 2、4 或 8） | ||
| - **RAIDZ2**: 4、6 或 10 个硬盘（数据盘 = 2、4 或 8） | ||
| - **RAIDZ3**: 5、9 或 17 个硬盘（数据盘 = 2、6 或 14） | ||
|
|
||
| 请注意，这些优化是可选的 - 上述建议适用于大多数使用情况。 | ||
|
|
||
| ::: |
Contributor
There was a problem hiding this comment.
Malformed admonition title — missing closing ] will cause an MDX parse error.
Line 178 reads :::tip[Optimizing 硬盘数量 without a closing bracket. Docusaurus MDX requires the syntax :::tip[Title]. This will either fail to parse or render the entire tip body as raw text.
🛠️ Proposed fix
-:::tip[Optimizing 硬盘数量
+:::tip[Optimizing 硬盘数量]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| :::tip[Optimizing 硬盘数量 | |
| 这提供了两个主要优点： | |
| **优化配置示例：** | |
| - **RAIDZ1**: 3、5 或 9 个硬盘（数据盘 = 2、4 或 8） | |
| - **RAIDZ2**: 4、6 或 10 个硬盘（数据盘 = 2、4 或 8） | |
| - **RAIDZ3**: 5、9 或 17 个硬盘（数据盘 = 2、6 或 14） | |
| 请注意，这些优化是可选的 - 上述建议适用于大多数使用情况。 | |
| ::: | |
| :::tip[Optimizing 硬盘数量] | |
| 这提供了两个主要优点： | |
| **优化配置示例：** | |
| - **RAIDZ1**: 3、5 或 9 个硬盘（数据盘 = 2、4 或 8） | |
| - **RAIDZ2**: 4、6 或 10 个硬盘（数据盘 = 2、4 或 8） | |
| - **RAIDZ3**: 5、9 或 17 个硬盘（数据盘 = 2、6 或 14） | |
| 请注意，这些优化是可选的 - 上述建议适用于大多数使用情况。 | |
| ::: |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 178 - 190, The admonition opening token `:::tip[Optimizing 硬盘数量` is
missing the closing bracket and will break MDX parsing; update the admonition
header by adding the closing `]` so it reads `:::tip[Optimizing 硬盘数量]` (preserve
the existing content block and closing `:::`) to restore a valid Docusaurus MDX
admonition.
Comment on lines
+65
to
+67
| :::注意 在你替换之前 | ||
|
|
||
| 在更换当前闪存设备之前，请考虑检查其错误： | ||
| :::note 在你替换之前 |
Contributor
There was a problem hiding this comment.
Duplicate admonition opener — :::注意 is invalid syntax.
Line 65 uses :::注意 在你替换之前 which is not a valid Docusaurus admonition type, immediately followed by the valid :::note 在你替换之前 on Line 67. The :::注意 line should be removed.
Proposed fix
-:::注意 在你替换之前
-
:::note 在你替换之前📝 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 在你替换之前 | |
| :::note 在你替换之前 |
🤖 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/system-administration/maintain-and-update/changing-the-flash-device.mdx`
around lines 65 - 67, Remove the invalid duplicate admonition opener by deleting
the line that reads ":::注意 在你替换之前" so only the valid admonition ":::note 在你替换之前"
remains; ensure there are no extra blank lines or duplicate openers around the
remaining ":::note 在你替换之前" block.
| --- | ||
|
|
||
| ## 重新格式化缓存驱动器 {#creating-a-file-system-formatting} | ||
| ## 重新格式化缓存驱动器 |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Search for cross-file references to the removed anchors
rg -n "reformatting-cache-drives|reformatting.cache|converting-to-a-new-file-system|converting.to.new.file" \
--type-add 'mdx:*.mdx' --type mdx --type md -C2Repository: unraid/docs
Length of output: 18366
Cross-document links to removed anchor found—these links are now broken.
The anchor #converting-to-a-new-file-system-type (from line 187, ## 转换到新的文件系统类型) is still being referenced by multiple documents across the repository:
docs/unraid-os/system-administration/secure-your-server/securing-your-data.mdxdocs/unraid-os/release-notes/7.0.0.md,7.2.0.md,7.2.1.mdi18n/zh/,i18n/fr/,i18n/es/,i18n/de/localized versions of the above
No references to #reformatting-cache-drives (from line 140) were found. Restore line 187 or update all cross-document links pointing to the file-systems page.
🤖 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/using-unraid-to/manage-storage/file-systems.mdx`
at line 140, The cross-document links reference the removed anchor
`#converting-to-a-new-file-system-type` (heading "## 转换到新的文件系统类型") but the file
now only contains "## 重新格式化缓存驱动器" (anchor `#reformatting-cache-drives`),
breaking links; either restore the original heading/anchor "## 转换到新的文件系统类型"
(re-add the section or its anchor ID in the file-systems.mdx) or update every
external reference (in files listed like securing-your-data.mdx and the release
notes and their i18n counterparts) to point to the new anchor
(`#reformatting-cache-drives`) so all cross-document links resolve.
| --- | ||
|
|
||
| ## 更改文件系统类型 {#changing-a-file-system-type} | ||
| ## 更改文件系统类型 |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, verify the file exists and get its size
wc -l "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx"Repository: unraid/docs
Length of output: 163
🏁 Script executed:
# Read the file to check the relevant lines
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '85,100p'Repository: unraid/docs
Length of output: 634
🏁 Script executed:
# Check line 102 (link change)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '95,110p'Repository: unraid/docs
Length of output: 771
🏁 Script executed:
# Check line 163 (anchor removed) and surrounding context
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '158,168p'Repository: unraid/docs
Length of output: 194
🏁 Script executed:
# Check line 230 (reference to removed anchor)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '225,235p'Repository: unraid/docs
Length of output: 377
🏁 Script executed:
# Check line 410 (anchor removed)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '405,415p'Repository: unraid/docs
Length of output: 570
🏁 Script executed:
# Check line 93 (reference to removed anchor)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '88,98p'Repository: unraid/docs
Length of output: 478
🏁 Script executed:
# Check line 433 (anchor removed)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '428,438p'Repository: unraid/docs
Length of output: 314
🏁 Script executed:
# Check line 451 (reference to removed anchor) and line 483 (duplicate heading)
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '446,456p'Repository: unraid/docs
Length of output: 413
🏁 Script executed:
# Check for duplicate heading around line 483
cat -n "i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx" | sed -n '478,488p'Repository: unraid/docs
Length of output: 302
🏁 Script executed:
# Search for cross-file references to the removed anchors across the entire codebase
rg -n "changing-a-file-system-type|using-the-unassigned-devices-plugins|checking-a-file-system" \
--type-add 'mdx:*.mdx' --type mdx --type mdRepository: unraid/docs
Length of output: 3662
🏁 Script executed:
# Verify the cache-pools.mdx file exists and check for btrfs-pools anchor
find . -name "cache-pools.mdx" -type fRepository: unraid/docs
Length of output: 542
Anchor removal breaks three intra-document links.
The explicit English anchors removed from these three headings are still referenced within this file:
| Removed anchor (heading line) | Broken link (referencing line) |
|---|---|
{#changing-a-file-system-type} on line 163 |
[更改文件系统类型](#changing-a-file-system-type) at line 230 |
{#using-the-unassigned-devices-plugins} on line 410 |
[Unassigned Devices](#using-the-unassigned-devices-plugins) at line 93 |
{#checking-a-file-system} on line 433 |
[文件系统检查](#checking-a-file-system) at line 451 |
After removal, Docusaurus will auto-generate IDs from the Chinese heading text (URL-encoded), so none of the three English-slug links will resolve. Additionally, ### 检查文件系统 appears twice—at line 433 (changed) and line 483 (unchanged). Without the explicit anchor on line 433, Docusaurus will auto-deduplicate them as #检查文件系统 and #检查文件系统-1, making it impossible for the link at line 451 to reliably reach the intended section.
Restore the explicit English anchors on all three headings:
🐛 Proposed fix — restore removed anchors
-## 更改文件系统类型
+## 更改文件系统类型 {`#changing-a-file-system-type`}-### 使用未分配设备插件
+### 使用未分配设备插件 {`#using-the-unassigned-devices-plugins`}-### 检查文件系统
+### 检查文件系统 {`#checking-a-file-system`}Also applies to: 410-410, 433-433
🤖 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/using-unraid-to/manage-storage/file-systems.mdx`
at line 163, Restore the three explicit English anchors that were removed so
existing intra-document links keep working: re-add the anchor tokens
{`#changing-a-file-system-type`}, {`#using-the-unassigned-devices-plugins`}, and
{`#checking-a-file-system`} to their respective headings (the "更改文件系统类型",
"Unassigned Devices" heading, and the first "检查文件系统" heading) so links like
[更改文件系统类型](`#changing-a-file-system-type`), [Unassigned
Devices](`#using-the-unassigned-devices-plugins`), and
[文件系统检查](`#checking-a-file-system`) resolve correctly and avoid Docusaurus
auto-deduplication.
| --- | ||
|
|
||
| ### 分配方法 {#allocation-method} | ||
| ### 分配方法 |
Contributor
There was a problem hiding this comment.
Removing explicit anchors breaks existing internal fragment links.
{#allocation-method} (line 283) and {#split-level} (line 362) are referenced by explicit #allocation-method and #split-level fragment links on lines 100 and 101 respectively. After removal, Docusaurus generates slugs from the Chinese header text (e.g., #分配方法, #分级水平), which no longer match those link targets.
🐛 Restore the explicit anchors
-### 分配方法
+### 分配方法 {`#allocation-method`}-### 分级水平
+### 分级水平 {`#split-level`}Also applies to: 362-362
🤖 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/using-unraid-to/manage-storage/shares.mdx`
at line 283, Restore the explicit anchor IDs so existing internal fragment links
keep working: re-add the anchor tokens {`#allocation-method`} and {`#split-level`}
to their corresponding headers (the "分配方法" and "分级水平" headers) so the internal
links referencing `#allocation-method` and `#split-level` resolve correctly; ensure
the header lines include those exact anchor IDs immediately after the header
text.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
unraid-docs | b3eaca8 | Mar 22 2026, 01:12 PM |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 13
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 (2)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx (1)
121-124:⚠️ Potential issue | 🟡 MinorDoppelte Überschrift/Einleitung in „Wartungserwartungen“ bereinigen
Der Abschnitt „Wartungserwartungen“ samt Einleitung steht bereits bei Lines 121-124 und wird bei Lines 136-139 erneut wiederholt. Das wirkt wie ein unbeabsichtigtes Duplikat.
Proposed fix
-### Wartungserwartungen - -Entwickler, die Anwendungen in Community Applications veröffentlichen, werden erwartet, dass sie ihre Projekte pflegen, um die Kompatibilität und Zuverlässigkeit für die Unraid-Community sicherzustellen. Dieser Abschnitt umreißt die laufenden Verantwortlichkeiten, die zur Aufrechterhaltung der Qualität der verfügbaren Anwendungen beitragen.Also applies to: 136-139
🤖 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/run-docker-containers/community-applications.mdx` around lines 121 - 124, Remove the duplicated "## Wartungserwartungen" header and its introductory paragraph by keeping the first occurrence and deleting the repeated block starting at the second "## Wartungserwartungen"; specifically locate the duplicate header text "## Wartungserwartungen" and the following introductory paragraph that repeats the same content (the paragraph describing developer maintenance responsibilities) and remove that second instance so only the original header and intro remain.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx (1)
64-68:⚠️ Potential issue | 🟡 MinorDuplicate heading.
Lines 64 and 66 contain identical
**Windows 7 oder höher:**headings. Remove one of them.🐛 Proposed fix
-**Windows 7 oder höher:** - **Windows 7 oder höher:** - Rechtsklicken Sie auf `make_bootable` und wählen Sie **Als Administrator ausführen**.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx` around lines 64 - 68, Remove the duplicate markdown heading "**Windows 7 oder höher:**" (the repeated heading string shown in the diff) so the section only contains a single occurrence followed by the bullet about running `make_bootable` as administrator; ensure surrounding spacing/formatting remains consistent after removal to avoid creating an accidental merged line or malformed list.
♻️ Duplicate comments (12)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx (1)
321-321:⚠️ Potential issue | 🔴 CriticalRestore the explicit anchor to prevent breaking existing links.
The explicit anchor
{#installation}was removed from the "Instalación" heading. Multiple files across different language versions contain links tofaq.mdx#installation, which will break when Docusaurus auto-generates a Spanish anchor (likely#instalación).🔗 Restore the stable anchor
-## Instalación +## Instalación {`#installation`}🤖 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/faq.mdx` at line 321, The explicit anchor for the Spanish heading was removed, breaking existing links to faq.mdx#installation; restore the stable anchor by updating the heading token "## Instalación" back to include the explicit ID (i.e., change the heading to include "{`#installation`}") so the anchor remains "installation" (use the exact ID "installation" to match links that reference faq.mdx#installation).i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md (2)
13-18:⚠️ Potential issue | 🔴 CriticalTranslate the known issues content to Spanish.
These lines contain English content that should be translated for Spanish readers.
🌐 Suggested Spanish translations
-See [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) for issues reported by other testers. +Consulta [Unraid OS Prerelease (Bugs & Feedback)](https://product.unraid.net/b/unraid-os-prerelease-bugs-feedback) para ver problemas reportados por otros probadores. -Critical: In 7.3.0-beta.1, non-encrypted XFS pools can fail to mount, causing all drives in the pool to appear unmountable. See [7.3.0 beta1 - (non-encrypted) xfs pool all drives are un-mountable](https://product.unraid.net/p/7-3-0-beta1-non-encrypted-xfs-pool-all-drives-are-un-mountanble). -Important: If you are running 7.3.0-beta.1 and format an XFS volume on a 4Kn disk (a disk that reports 4096-byte sectors), that newly formatted volume will not mount after the fix for the issue above is applied. +Crítico: En 7.3.0-beta.1, los pools XFS no cifrados pueden fallar al montar, causando que todas las unidades del pool aparezcan como no montables. Consulta [7.3.0 beta1 - (non-encrypted) xfs pool all drives are un-mountable](https://product.unraid.net/p/7-3-0-beta1-non-encrypted-xfs-pool-all-drives-are-un-mountanble). +Importante: Si estás ejecutando 7.3.0-beta.1 y formateas un volumen XFS en un disco 4Kn (un disco que reporta sectores de 4096 bytes), ese volumen recién formateado no se montará después de aplicar la corrección del problema anterior. -ReiserFS is no longer supported in modern Linux kernels; you must migrate off ReiserFS before upgrading to this release. See [Converting to a new file system type](/unraid-os/using-unraid-to/manage-storage/file-systems/) for details. +ReiserFS ya no es compatible con los kernels Linux modernos; debes migrar desde ReiserFS antes de actualizar a esta versión. Consulta [Convertir a un nuevo tipo de sistema de archivos](/unraid-os/using-unraid-to/manage-storage/file-systems/) para más detalles.🤖 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` around lines 13 - 18, Translate the English "See [Unraid OS Prerelease (Bugs & Feedback)]..." paragraph, the two bullets beginning "Critical: In 7.3.0-beta.1, non-encrypted XFS pools..." and "Important: If you are running 7.3.0-beta.1..." and the final sentence starting "ReiserFS is no longer supported..." into Spanish, preserving links and formatting; update the Spanish text to accurately convey the same warnings (including mentions of "7.3.0-beta.1", "XFS", "4Kn", and "ReiserFS") and keep the same bullet structure and link targets so the content reads naturally for Spanish readers.
43-43:⚠️ Potential issue | 🔴 CriticalTranslate this English sentence to Spanish.
This line contains English text that should be translated for Spanish readers.
🌐 Suggested Spanish translation
-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). +Para cambiar proactivamente a licencias basadas en TPM, consulta [¿Cómo puedo cambiar de licencias basadas en flash a licencias basadas en TPM?](/unraid-os/troubleshooting/tpm-licensing-faq/#tpm).🤖 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 43, The English sentence "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)." should be replaced with its Spanish translation; update the line in the document to: "Para cambiar proactivamente al licenciamiento basado en TPM, consulte [¿Cómo puedo pasar del licenciamiento en flash al licenciamiento basado en TPM?](/unraid-os/troubleshooting/tpm-licensing-faq/#tpm)." Ensure the link target remains unchanged and punctuation (inverted question mark) is included.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md (1)
9-9:⚠️ Potential issue | 🟠 MajorTranslate the remaining English guidance in upgrade/onboarding lines.
Line 9 and Line 37 are still English in this French release-note page.
Also applies to: 37-37
🤖 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` at line 9, Translate the remaining English guidance strings on the French release notes page: replace the English sentence "For step-by-step instructions, see [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)?" (present around Line 9) and the English text at the other occurrence (around Line 37) with their correct French equivalents, keeping the same Markdown link targets and formatting (i.e., maintain the [Upgrading Unraid] and [license] link labels and URLs but localize the surrounding text into French).i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (2)
149-149:⚠️ Potential issue | 🟡 MinorUse real Markdown lines/items here instead of literal
\n.At Line 149 and Line 160, those escapes will render as raw text, so the checklist will not break into separate entries.
🛠️ Proposed fix
-✅ 设置 USB 闪存驱动器为主要启动设备。\n✅ 配置存储控制器为通过 SATA 连接的 **%%AHCI|ahci%%** 模式。\n✅ 将控制器设置为 **%%HBA 模式|hba-mode%%** （不是 **%%RAID|raid%%**）。\n✅ 禁用 **安全启动**，因为 Unraid OS 不支持此功能。 +- ✅ 设置 USB 闪存驱动器为主要启动设备。 +- ✅ 配置存储控制器为通过 SATA 连接的 **%%AHCI|ahci%%** 模式。 +- ✅ 将控制器设置为 **%%HBA 模式|hba-mode%%** （不是 **%%RAID|raid%%**）。 +- ✅ 禁用 **安全启动**，因为 Unraid OS 不支持此功能。-✅ 调整启动顺序为：**Forced-FDD**、**USB-HDD**、**USB-ZIP**。\n✅ 禁用 USB 2.0/3.0 支持。\n✅ 切换任何快速启动功能。\n✅ 切换 USB 键盘支持。 +- ✅ 调整启动顺序为：**Forced-FDD**、**USB-HDD**、**USB-ZIP**。 +- ✅ 禁用 USB 2.0/3.0 支持。 +- ✅ 切换任何快速启动功能。 +- ✅ 切换 USB 键盘支持。Also applies to: 160-160
🤖 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/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 149, Replace the literal "\n" escapes in the checklist string with actual Markdown list lines so each item becomes its own line (e.g., start four separate lines each beginning with "✅ 设置 USB 闪存驱动器为主要启动设备。" / "✅ 配置存储控制器为通过 SATA 连接的 **%%AHCI|ahci%%** 模式。" / "✅ 将控制器设置为 **%%HBA 模式|hba-mode%%** （不是 **%%RAID|raid%%）。" / "✅ 禁用 **安全启动**，因为 Unraid OS 不支持此功能。" ), ensuring the checklist renders as separate entries; make the same change for the duplicate occurrence that currently contains "\n".
12-12:⚠️ Potential issue | 🟠 MajorFinish localizing the remaining English blocks before merge.
This
i18n/zhpage still contains English-only content at Line 12, Line 36, Lines 51-113, Lines 116-117, Lines 134-135, Lines 153-154, and Lines 165-167. The new### 高级设置bullets were missed too, so the page is still mixed-language for Chinese readers.Also applies to: 36-36, 51-113, 116-117, 134-135, 153-154, 165-167
🤖 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/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 12, This page still contains multiple English fragments—translate all remaining English-only text into Chinese: replace the sentence containing "Multi-language support" and the link text pointing to that page, localize the inline placeholder "%%WebGUI|web-gui%%" into an appropriate Chinese term, and translate every English block referenced in the review (the long paragraph blocks and any lists between the previously noted sections), including the newly added "### 高级设置" bullets that were left in English; ensure link targets and markdown headings remain intact but their visible text is fully localized and run a quick pass to remove any leftover English phrases or duplicate blocks.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx (1)
98-99:⚠️ Potential issue | 🔴 CriticalRemove the orphaned
:::marker.The
:::infoblock already closes on Line 97. This extra marker will render as stray text or break MDX parsing.Proposed fix
::: - -:::🤖 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/getting-started/set-up-unraid/configure-your-array.mdx` around lines 98 - 99, Remove the orphaned closing marker ':::' that follows the ':::info' block (the extra standalone ':::' after the ':::info' block) so the MDX block is correctly closed only once; find the stray ':::' token and delete it to prevent stray text or MDX parse errors.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx (2)
91-93:⚠️ Potential issue | 🔴 CriticalRemove the duplicate heading/anchor.
The same
#manual-keyfile-installheading now appears twice back-to-back, so one anchor will be dropped and links to this section become unreliable.Proposed fix
### Wie installiere ich meine Lizenzschlüssel-Datei manuell auf meinem USB-Flash-Gerät? {`#manual-keyfile-install`} -#### Wie installiere ich meine Lizenzschlüssel-Datei manuell auf meinem USB-Flash-Gerät? {`#manual-keyfile-install`} - 1. Stellen Sie sicher, dass Sie ein aktuelles Backup Ihres USB-Laufwerks haben. Verwenden Sie [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) (empfohlen) oder die lokale Backup-Option unter ***Main → Flash → Flash Backup***.🤖 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/licensing-faq.mdx` around lines 91 - 93, Duplicate section heading/anchor "#manual-keyfile-install" appears twice; remove the redundant one so the anchor is unique. Edit the mdx content and delete the second occurrence of "#### Wie installiere ich meine Lizenzschlüssel-Datei manuell auf meinem USB-Flash-Gerät? {`#manual-keyfile-install`}" (or the duplicate block immediately following the H3) leaving a single heading with that anchor, then verify internal links pointing to `#manual-keyfile-install` still resolve.
57-61:⚠️ Potential issue | 🟠 MajorRestore the OEM-specific answer here.
These three identical sentences just repeat the generic purchase path, so the reseller/OEM FAQ no longer answers the question in its own heading.
🤖 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/licensing-faq.mdx` around lines 57 - 61, The section currently contains three identical lines ("Sie können eine Lizenz über die %%WebGUI|web-gui%% oder durch den Erwerb eines Aktivierungscodes auf der [Unraid-Website](https://unraid.net/pricing) erwerben.") which removed the OEM/reseller-specific answer; revert those duplicate lines and restore the original OEM-specific FAQ content under the reseller/OEM heading, replacing the three repeats with the OEM-specific text (keeping any MDX tokens like %%WebGUI|web-gui%% if relevant) and ensure the answer clearly addresses reseller activation, OEM activation codes or reseller contact steps that were originally intended.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (3)
162-165:⚠️ Potential issue | 🟠 MajorTranslate the BIOS warning block.
The first sentence inside this
:::importantblock is still English, so a high-importance troubleshooting warning is only partially localized.Proposed fix
:::important -Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible. +Muchas placas base limitan la selección del dispositivo de arranque a 12 discos duros. Si tu unidad flash USB se reconoce como un disco duro, es posible que no puedas arrancar desde ella después de instalar 12 discos físicos. Configura la BIOS para tratar la unidad flash como un dispositivo extraíble siempre que sea posible. Si utiliza un HBA adicional, es posible desactivar el soporte de INT 13h para evitar que sus unidades conectadas aparezcan en la lista de dispositivos de arranque; esto le ayudará a mantenerse dentro del límite de 12 discos. :::🤖 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/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 162 - 165, The important warning block contains an English sentence that must be translated into Spanish; replace the English sentence "Many motherboards limit boot device selection to 12 hard drives. If your USB flash drive is recognized as a hard drive, you may not be able to boot from it after installing 12 physical hard drives. Configure the BIOS to treat the flash drive as a removable device whenever possible." with an equivalent Spanish translation (keeping the same meaning and tone) inside the existing :::important block so it reads fully in Spanish alongside the existing sentence about INT 13h support; update the same block (the important admonition) to ensure both sentences are consistently localized.
83-83:⚠️ Potential issue | 🟡 MinorTranslate these FAQ pointers.
Both pointers are still English inside the new Spanish onboarding flow, so the section reads half-localized.
Proposed fix
- If you have questions about device counts or mirrored boot, see the [Internal Boot FAQ (7.3+)](./internal-boot-faq.mdx), which also includes video walkthroughs. For TPM-based licensing questions, see the [TPM Licensing FAQ (7.3+)](../../troubleshooting/tpm-licensing-faq.mdx). + Si tienes preguntas sobre el número de dispositivos o el arranque en espejo, consulta las [Preguntas frecuentes sobre arranque interno (7.3+)](./internal-boot-faq.mdx), que también incluye guías en vídeo. Para preguntas sobre licencias basadas en TPM, consulta las [Preguntas frecuentes sobre licencias TPM (7.3+)](../../troubleshooting/tpm-licensing-faq.mdx). @@ -For internal boot questions, see the [Internal Boot FAQ (7.3+)](./internal-boot-faq.mdx). +Para preguntas sobre el arranque interno, consulta las [Preguntas frecuentes sobre arranque interno (7.3+)](./internal-boot-faq.mdx).Also applies to: 110-110
🤖 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/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` at line 83, Replace the two English FAQ link texts in the sentence that currently reads "Internal Boot FAQ (7.3+)" and "TPM Licensing FAQ (7.3+)" with their Spanish translations (e.g., "Preguntas frecuentes sobre arranque interno (7.3+)" and "Preguntas frecuentes sobre licencias TPM (7.3+)") in the MDX content so the onboarding flow is fully localized; update both occurrences (the link text strings "Internal Boot FAQ (7.3+)" and "TPM Licensing FAQ (7.3+)") while keeping the existing relative link targets intact.
147-152:⚠️ Potential issue | 🟠 MajorFix the checklist rendering and finish the Spanish translation.
The literal
\nwill render verbatim, and the advanced checklist items are still English.Proposed fix
-✅ Establecer el dispositivo de arranque primario en la unidad flash USB.\n✅ Configurar el controlador de almacenamiento al modo **%%AHCI|ahci%%** con conexiones SATA.\n✅ Configurar el controlador en modo **%%HBA|hba-mode%%** (no **%%RAID|raid%%**).\n✅ Desactivar **Arranque Seguro** ya que no es compatible con Unraid OS. +✅ Establece la unidad flash USB como dispositivo de arranque principal.\ +✅ Configura el controlador de almacenamiento en modo **%%AHCI|ahci%%** con conexiones SATA.\ +✅ Configura el controlador en modo **%%HBA|hba-mode%%** (no **%%RAID|raid%%**).\ +✅ Desactiva **Arranque Seguro**, ya que no es compatible con Unraid OS. @@ -✅ Enable **%%hardware virtualization|hvm%%** features (e.g., **%%Intel VT-x|intel-vt-x%%** or **%%AMD-V|amd-v%%**) for **%%virtual machines (VMs)|vm%%**.\ -✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs. +✅ Habilita las funciones de **%%virtualización de hardware|hvm%%** (por ejemplo, **%%Intel VT-x|intel-vt-x%%** o **%%AMD-V|amd-v%%**) para las **%%máquinas virtuales (VM)|vm%%**.\ +✅ Habilita la compatibilidad con **%%IOMMU|iommu%%** (Intel VT-d o AMD-Vi) para asignar dispositivos PCI a las VM. @@ -✅ Ajustar el orden de arranque a: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\n✅ Deshabilitar el soporte USB 2.0/3.0.\n✅ Alternar cualquier característica de Arranque Rápido.\n✅ Alternar el soporte para teclado USB. +✅ Ajusta el orden de arranque a: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\ +✅ Deshabilita el soporte USB 2.0/3.0.\ +✅ Alterna cualquier función de Arranque Rápido.\ +✅ Alterna la compatibilidad con teclado USB.Also applies to: 158-158
🤖 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/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 147 - 152, Remove the literal "\n" in the checklist (it currently renders verbatim) and convert the remaining English advanced items to Spanish while preserving the translation tokens (e.g., %%hardware virtualization|hvm%%, %%Intel VT-x|intel-vt-x%%, %%AMD-V|amd-v%%, %%virtual machines (VMs)|vm%%, %%IOMMU|iommu%%). Specifically, change the lines starting with "✅ Enable **%%hardware virtualization|hvm%%**..." and "✅ Enable **%%IOMMU|iommu%%**..." to proper Spanish wording (e.g., "✅ Habilitar ..." or equivalent) and ensure the trailing backslash used for a line break is removed or replaced with a real newline so the checklist renders correctly; apply the same fixes to the duplicate occurrence referenced (line with the same content at 158).
🟡 Minor comments (14)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md-7-10 (1)
7-10:⚠️ Potential issue | 🟡 MinorTranslate the upgrade instruction block to German
Line 9 is still in English inside a German release-note page, which breaks localization consistency.
✏️ Proposed fix
## Upgrade -For step-by-step instructions, see [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)? +Eine Schritt-für-Schritt-Anleitung finden Sie unter [Unraid aktualisieren](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Fragen zu Ihrer [Lizenz](/unraid-os/troubleshooting/licensing-faq/)?🤖 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.4.md` around lines 7 - 10, The "## Upgrade" block is still in English; translate the header and the two sentences into German while preserving the Markdown links and URLs (keep [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/) and [license](/unraid-os/troubleshooting/licensing-faq/) targets unchanged). Replace "## Upgrade" with its German equivalent, translate "For step-by-step instructions, see Upgrading Unraid." and "Questions about your license?" into German, and ensure punctuation and link formatting remain intact in the "Upgrade" section.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx-87-88 (1)
87-88:⚠️ Potential issue | 🟡 MinorDoppelten Support-Absatz entfernen
Der Satz in Line 87 ist in Line 104 identisch wiederholt. Bitte eine Instanz entfernen, um Redundanz zu vermeiden.
Proposed fix
-Diese Ressourcen verbinden Sie mit Community-Foren und Entwicklerdiskussionen, wo Sie Hilfe finden, Probleme beheben und auf dem Laufenden bleiben können.Also applies to: 104-104
🤖 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/run-docker-containers/community-applications.mdx` around lines 87 - 88, Remove the duplicate support paragraph by deleting one of the identical sentences "Diese Ressourcen verbinden Sie mit Community-Foren und Entwicklerdiskussionen, wo Sie Hilfe finden, Probleme beheben und auf dem Laufenden bleiben können." (appears twice); keep a single instance, ensure surrounding paragraph breaks and punctuation remain correct, and run a quick preview to confirm no extra blank line or formatting change was introduced in community-applications.mdx.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx-63-63 (1)
63-63:⚠️ Potential issue | 🟡 MinorTerminologie auf „Boot-Laufwerk“ vereinheitlichen
Line 63 verwendet noch „Flash-Laufwerk“, obwohl Ziel-Link und PR-Ziel auf „Boot“-Terminologie umgestellt sind. Bitte konsistent auf „Boot-Laufwerk“ wechseln.
Proposed fix
-Bevor Sie installieren, sollten Sie in Erwägung ziehen, Ihr Flash-Laufwerk zu sichern, um Ihre Konfiguration zu schützen. Siehe [Sichern Sie Ihr Flash-Laufwerk](/unraid-os/system-administration/secure-your-server/secure-your-boot-drive/) für Sicherungsanweisungen. +Bevor Sie installieren, sollten Sie in Erwägung ziehen, Ihr Boot-Laufwerk zu sichern, um Ihre Konfiguration zu schützen. Siehe [Sichern Sie Ihr Boot-Laufwerk](/unraid-os/system-administration/secure-your-server/secure-your-boot-drive/) für Sicherungsanweisungen.🤖 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/run-docker-containers/community-applications.mdx` at line 63, Replace the remaining use of the term "Flash-Laufwerk" with "Boot-Laufwerk" in the sentence that reads "Bevor Sie installieren, sollten Sie in Erwägung ziehen, Ihr Flash-Laufwerk zu sichern..." and update the link text "[Sichern Sie Ihr Flash-Laufwerk](/unraid-os/system-administration/secure-your-server/secure-your-boot-drive/)" to "[Sichern Sie Ihr Boot-Laufwerk](/unraid-os/system-administration/secure-your-server/secure-your-boot-drive/)" so the terminology matches the PR target and the linked page.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx-16-16 (1)
16-16:⚠️ Potential issue | 🟡 MinorHeading reverted to English in German locale file.
This section heading was previously in German ("Zuweisung von Parity- und Datenlaufwerken") but is now in English. This creates inconsistency with other German headings in the document (e.g., lines 22, 64, 78). If this is intentional for anchor stability, consider keeping the German visible text while preserving the English anchor ID.
🤖 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 16, The heading "## Assign Parity and Data disks {`#assign-parity-and-data-disks`}" is in English in a German locale file — restore the visible text to German while keeping the existing anchor for link stability by changing the heading to the German phrase (e.g., "## Zuweisung von Parity- und Datenlaufwerken {`#assign-parity-and-data-disks`}"); update the visible heading text only and do not alter the anchor ID to preserve existing links/references (locate the header line containing "assign-parity-and-data-disks" and replace the English visible text).i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx-59-59 (1)
59-59:⚠️ Potential issue | 🟡 MinorRemove duplicated sentences introduced by the update.
Line 59, Line 148, Line 170, and Line 206 repeat the exact previous sentence and should be deleted to avoid redundant content.
Proposed cleanup
- Puede comprar una licencia a través del %%WebGUI|web-gui%% o obteniendo un código de activación en el [sitio web de Unraid](https://unraid.net/pricing). ... - "Ilimitado" se refiere al número máximo de dispositivos de almacenamiento que puedes conectar a tu servidor Unraid, según tu nivel de licencia. ... - No, no necesitas volver a comprar tu licencia si falla tu dispositivo USB. ... - Las claves de registro de prueba de Unraid duran 30 días y se pueden extender dos veces por 14 días adicionales cada vez. Después de dos extensiones de prueba, no se pueden conceder más extensiones. Para solicitar una extensión, debes detener el array, navegar a la página **Herramientas > Registro** y hacer clic en "Solicitar extensión".Also applies to: 148-148, 170-170, 206-206
🤖 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/licensing-faq.mdx` at line 59, The document contains duplicated sentences: "Puede comprar una licencia a través del %%WebGUI|web-gui%% o obteniendo un código de activación en el [sitio web de Unraid](https://unraid.net/pricing)." Remove the repeated occurrences (the ones at the mentioned lines) so only the single intended instance remains; search for that exact sentence in licensing-faq.mdx and delete the duplicate entries while preserving surrounding punctuation and spacing.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx-59-59 (1)
59-59:⚠️ Potential issue | 🟡 MinorRemove accidental duplicated sentences.
Lines 59, 148, 170, and 206 repeat the immediately preceding sentence verbatim, which reads like a merge/Crowdin duplication artifact.
Also applies to: 148-148, 170-170, 206-206
🤖 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/troubleshooting/licensing-faq.mdx` at line 59, The file contains accidental duplicated sentences (e.g., the sentence "Vous pouvez acheter une licence via le %%WebGUI|web-gui%% ou en obtenant un code d'activation sur le [site Unraid](https://unraid.net/pricing)." at line 59 and identical duplicates at lines 148, 170, and 206); remove the repeated duplicate occurrences so each sentence appears only once, leaving the original intended sentence in place in the MDX content (search for the exact sentence text to locate and delete the extra copies).i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx-10-10 (1)
10-10:⚠️ Potential issue | 🟡 MinorLocalize remaining English/mixed-language section titles.
Line 10 and Line 57 still contain English/mixed wording in a French page.
Proposed fix
-## Backups {`#backups`} +## Sauvegardes {`#backups`} @@ -:::important[Reducing risques de sécurité] +:::important[Réduction des risques de sécurité]Also applies to: 57-57
🤖 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/secure-your-server/secure-your-boot-drive.mdx` at line 10, Translate the remaining English/mixed section titles into French: replace the header "## Backups {`#backups`}" with a French equivalent (e.g., "## Sauvegardes {`#sauvegardes`}") and update the anchor id accordingly, and do the same for the other English/mixed section title at line 57; also search and update any internal links or references that point to the old anchor ids ("#backups") so they reference the new id ("#sauvegardes") to keep cross-links working.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx-12-12 (1)
12-12:⚠️ Potential issue | 🟡 MinorLocalize the section heading text to French.
Line 12 is still English. You can keep the existing anchor for backward compatibility while translating the heading.
Proposed fix
-## Back up your boot device {`#back-up-your-flash-device`} +## Sauvegarder votre périphérique de démarrage {`#back-up-your-flash-device`}🤖 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/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx` at line 12, Translate the English heading "## Back up your boot device {`#back-up-your-flash-device`}" into French while preserving the existing anchor for backward compatibility; replace the line with the French heading "## Sauvegardez votre périphérique de démarrage {`#back-up-your-flash-device`}" (keeping the same heading level and anchor token).i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx-16-18 (1)
16-18:⚠️ Potential issue | 🟡 MinorRe-localize the section heading and fix French article usage.
Line 16 is English in a French page, and Line 18 should use “dans l’Unraid %%WebGUI|web-gui%%”.
Proposed fix
-## Assign Parity and Data disks {`#assign-parity-and-data-disks`} +## Assigner les disques de parité et de données {`#assign-parity-and-data-disks`} @@ -Vous utiliserez l’onglet **Principal** dans le Unraid %%WebGUI|web-gui%% pour assigner et vérifier les périphériques, y compris les affectations de %%array|array%% et de pool ainsi que tous les périphériques non assignés et votre périphérique de démarrage (clé USB par défaut). +Vous utiliserez l’onglet **Principal** dans l’Unraid %%WebGUI|web-gui%% pour assigner et vérifier les périphériques, y compris les affectations de %%array|array%% et de pool ainsi que tous les périphériques non assignés et votre périphérique de démarrage (clé USB par défaut).🤖 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/getting-started/set-up-unraid/configure-your-array.mdx` around lines 16 - 18, The section heading "Assign Parity and Data disks" is English on a French page and the following sentence should use the correct French article; replace the English heading with a French translation (e.g., "Affecter les disques de parité et de données") and update the sentence to use "dans l’Unraid %%WebGUI|web-gui%%" instead of the current phrasing; ensure you update the heading token and the sentence containing "Vous utiliserez l’onglet **Principal**" so it reads correctly in French with the %%WebGUI|web-gui%% token.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx-114-132 (1)
114-132:⚠️ Potential issue | 🟡 MinorGive this walkthrough a non-BIOS heading.
These steps are about signing in to Unraid.net and installing a trial key, but they currently live under the first
Recomendaciones para el BIOSsection until the real BIOS section starts at Line 136. That makes the page outline and TOC misleading.🤖 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/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 114 - 132, This walkthrough about signing in to Unraid.net and installing a trial key is currently nested under the BIOS recommendations section; extract the entire steps block (the numbered steps, both image divs, and the :::important note referencing Tools → Registration and the %%WebGUI|web-gui%% token) and move it out from under the "Recomendaciones para el BIOS" section into its own non-BIOS heading such as "Inicia sesión y obtiene clave de licencia" (use the same heading level as neighboring sections), ensuring the content, images, and tokens remain unchanged and the new heading appears before the actual BIOS section so the page outline/TOC reflects the correct structure.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx-16-18 (1)
16-18:⚠️ Potential issue | 🟡 MinorTranslate this new section back into Simplified Chinese.
The heading, overview sentence, and boot-device bullet were added in English, so this localized page now switches languages mid-flow. Line 18 also reintroduces
Maininstead of主页面, which no longer matches the Chinese WebGUI wording.Based on learnings, 在Unraid简体中文界面中，"Main"标签页/按钮被翻译为"主页面"，中文文档应使用"主页面"而非英文"Main"以保持与实际用户界面的一致性。
Also applies to: 32-32
🤖 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/getting-started/set-up-unraid/configure-your-array.mdx` around lines 16 - 18, Translate the added English section into Simplified Chinese: localize the heading "Assign Parity and Data disks {`#assign-parity-and-data-disks`}" and the overview sentence into Chinese, replace the UI label "Main" with the Chinese "主页面" everywhere in that sentence, and translate the boot-device fragment "your boot device (USB flash by default)" into Chinese (e.g., "启动设备（默认 USB 闪存）") so the page remains fully in Chinese and matches the Unraid CN WebGUI wording.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx-12-12 (1)
12-12:⚠️ Potential issue | 🟡 MinorLocalize this subsection title.
This new heading is still English, so it stands out in the German page and sidebar.
🤖 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/complete-your-post-setup-essentials.mdx` at line 12, The English subsection heading "## Back up your boot device {`#back-up-your-flash-device`}" must be localized to German; replace the visible text with a proper German translation (e.g., "## Sichern Sie Ihr Boot‑Gerät") and update the anchor id to a matching German slug (e.g., "{`#sichern-sie-ihr-boot-geraet`}") so the sidebar and internal links remain consistent; ensure only the heading line in the file is changed and keep the MDX heading syntax intact.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx-16-16 (1)
16-16:⚠️ Potential issue | 🟡 MinorLocalize this section heading.
The page is Spanish, but this new H2 is still English, so the TOC and section entry point no longer match the locale.
Proposed fix
-## Assign Parity and Data disks {`#assign-parity-and-data-disks`} +## Asigna discos de paridad y datos {`#assign-parity-and-data-disks`}🤖 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/getting-started/set-up-unraid/configure-your-array.mdx` at line 16, Heading "Assign Parity and Data disks" is still in English; replace it with a Spanish localized heading (e.g., "Asignar discos de paridad y datos") and update the anchor slug {`#assign-parity-and-data-disks`} to a matching Spanish slug (for example {`#asignar-discos-paridad-datos`}); also scan for any in-page links or TOC entries that reference the old anchor and update them to the new Spanish slug so the section entry point and TOC remain correct.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx-12-12 (1)
12-12:⚠️ Potential issue | 🟡 MinorLocalize this subsection title.
This heading is still English, so it stands out in the Spanish page and sidebar.
🤖 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/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx` at line 12, The subsection heading "Back up your boot device {`#back-up-your-flash-device`}" is still in English; replace it with a Spanish localized heading (for example "Haz una copia de seguridad de tu dispositivo de arranque") and update the anchor slug accordingly (e.g., {`#haz-una-copia-de-seguridad-de-tu-dispositivo-de-arranque`} or a shorter Spanish slug) so the title and sidebar appear in Spanish; ensure the translated text replaces the exact string "Back up your boot device" and update the anchor token "{`#back-up-your-flash-device`}" to the new Spanish slug in the same line.
🧹 Nitpick comments (2)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md (1)
13-17: Unify terminology for prior-release referencesLine 13 uses
Release Notes, while Line 17 usesRelease-Notizen. Consider using one term consistently to improve readability and translation quality.🤖 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.4.md` around lines 13 - 17, The two references to the prior release use inconsistent terminology—"[7.2.3 Release Notes]" and "[Release-Notizen 7.2.3]"—so update them to the same German term for consistency; edit the link text in both occurrences (the link labeled "[7.2.3 Release Notes](/unraid-os/release-notes/7.2.3/)" and the link labeled "[Release-Notizen 7.2.3](/unraid-os/release-notes/7.2.3/)") to the chosen consistent phrase (e.g., "Release-Notizen 7.2.3") while keeping the URLs intact, and verify the surrounding heading "### Rückschritte {`#rolling-back`}" still reads naturally with the unified term.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)
112-114: Clarify section structure: this heading no longer matches its content.The first “Recommandations pour le BIOS” section now introduces Unraid.net licensing steps. Consider renaming this heading (or moving the block) to avoid duplicate/conflicting section titles.
🤖 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/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 112 - 114, The heading "Recommandations pour le BIOS" no longer matches the paragraph about Unraid.net license keys; update the MDX by either renaming the heading to something like "Licence Unraid.net" or moving the license paragraph into an appropriate "Licence" or "Activation" section so the heading and content align; look for the heading text "Recommandations pour le BIOS" and the nearby Unraid.net license sentence to make the change and ensure there are no duplicate/conflicting section titles afterward.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 5935f74c-a47a-495c-ab4e-1d41d62e65ff
📒 Files selected for processing (40)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.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/release-notes/7.2.4.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/secure-your-server/secure-your-boot-drive.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdxi18n/de/docusaurus-theme-classic/footer.jsoni18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/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/release-notes/7.2.4.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/secure-your-server/secure-your-boot-drive.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/using-unraid-to/run-docker-containers/community-applications.mdxi18n/es/docusaurus-theme-classic/footer.jsoni18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/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/release-notes/7.2.4.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/secure-your-server/secure-your-boot-drive.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/using-unraid-to/run-docker-containers/community-applications.mdxi18n/fr/docusaurus-theme-classic/footer.jsoni18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
✅ Files skipped from review due to trivial changes (11)
- i18n/de/docusaurus-theme-classic/footer.json
- i18n/es/docusaurus-theme-classic/footer.json
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx
- i18n/fr/docusaurus-theme-classic/footer.json
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
- i18n/fr/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/system-administration/secure-your-server/secure-your-boot-drive.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
- i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
🚧 Files skipped from review as they are similar to previous changes (2)
- i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx
- i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
Comment on lines
+14
to
17
| Sichern Sie Ihr Unraid-Boot-Gerät immer nach bedeutenden Konfigurationsänderungen. Regelmäßige Backups werden *dringend* empfohlen. | ||
|
|
||
| Um Ihr Flash-Gerät zu sichern, gehen Sie zum **Main** Tab, wählen Sie das Gerät aus und klicken Sie auf **Flash Backup**. | ||
| Um Ihr Boot-Gerät zu sichern, gehen Sie zum **Main**-Tab, wählen Sie das Gerät aus und klicken Sie auf **Boot Device Backup**. | ||
|
|
Contributor
There was a problem hiding this comment.
Use the existing Flash backup UI labels in this step.
Boot Device Backup reads like a renamed action, but the backup flow users actually follow is still the Flash backup feature. If this wording stays, the instruction path in the doc no longer matches the WebGUI.
Proposed fix
-Um Ihr Boot-Gerät zu sichern, gehen Sie zum **Main**-Tab, wählen Sie das Gerät aus und klicken Sie auf **Boot Device Backup**.
+Um Ihr Boot-Gerät zu sichern, gehen Sie zum **Main**-Tab, wählen Sie **Flash device** aus und klicken Sie auf **FLASH BACKUP**.📝 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
| Sichern Sie Ihr Unraid-Boot-Gerät immer nach bedeutenden Konfigurationsänderungen. Regelmäßige Backups werden *dringend* empfohlen. | |
| Um Ihr Flash-Gerät zu sichern, gehen Sie zum **Main** Tab, wählen Sie das Gerät aus und klicken Sie auf **Flash Backup**. | |
| Um Ihr Boot-Gerät zu sichern, gehen Sie zum **Main**-Tab, wählen Sie das Gerät aus und klicken Sie auf **Boot Device Backup**. | |
| Sichern Sie Ihr Unraid-Boot-Gerät immer nach bedeutenden Konfigurationsänderungen. Regelmäßige Backups werden *dringend* empfohlen. | |
| Um Ihr Boot-Gerät zu sichern, gehen Sie zum **Main**-Tab, wählen Sie **Flash device** aus und klicken Sie auf **FLASH BACKUP**. | |
🤖 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/complete-your-post-setup-essentials.mdx`
around lines 14 - 17, The text currently directs users to click "Boot Device
Backup", which mislabels the existing UI; update the copy to use the actual
Flash backup UI labels and navigation so it matches the WebGUI (e.g., mention
Main tab → Flash device → FLASH BACKUP and refer to it as "Flash Backup" or
"FLASH BACKUP" rather than "Boot Device Backup"), and clarify that the Flash
backup produces a ZIP that includes OS + configuration compatible with the USB
Flash Creator "Use custom" restore flow; edit the strings in this document (the
lines referencing "Boot Device Backup" and the surrounding instructions) to
reflect those exact UI labels and the compatibility note.
Comment on lines
+137
to
+142
| - Sie behalten Ihre Lizenz und können Ihre aktuelle Version des Unraid OS auf unbestimmte Zeit verwenden. | ||
| - Sie erhalten keine neuen Funktionsupdates oder großen Versionsupgrades. | ||
| - Sie bleiben berechtigt, Patch-Releases und Sicherheitsupdates innerhalb derselben Minor-Version zu erhalten (z.B. 7.1.x, wenn Ihre Lizenz bei 7.1.0 abgelaufen ist). | ||
| - Sobald eine neue Minor-Version veröffentlicht wird (z.B. 7.2.0), werden nur Sicherheitsupdates für die vorherige Minor-Version bereitgestellt. | ||
| - Wenn eine Version das Ende ihres Lebenszyklus (EOL) erreicht, werden keine weiteren Updates bereitgestellt. | ||
| - Sie können die Verlängerungsgebühr jederzeit zahlen, um wieder Zugriff auf die neuesten Updates zu erhalten. |
Contributor
There was a problem hiding this comment.
This section no longer answers the prerelease question.
These bullets are a copy of the “license not extended” section above and never mention Beta/RC access, so the Vorabversionen FAQ is now misleading.
🧰 Tools
🪛 LanguageTool
[grammar] ~137-~137: Ergänze ein Satzzeichen
Context: ... können Ihre aktuelle Version des Unraid OS auf unbestimmte Zeit verwenden. - Sie...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_UNRAIDDASHOS)
[style] ~139-~139: Drei aufeinanderfolgende Sätze beginnen mit dem gleichen Wort. Evtl. können Sie den Satz umformulieren, zum Beispiel, indem Sie ein Synonym nutzen.
Context: ...updates oder großen Versionsupgrades. - Sie bleiben berechtigt, Patch-Releases und ...
(GERMAN_WORD_REPEAT_BEGINNING_RULE)
[grammar] ~139-~139: Ergänze ein Leerzeichen
Context: ...lb derselben Minor-Version zu erhalten (z.B. 7.1.x, wenn Ihre Lizenz bei 7.1.0 abg...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)
🤖 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/licensing-faq.mdx`
around lines 137 - 142, The "Vorabversionen" FAQ currently duplicates the
"license not extended" bullets and doesn't address prerelease (Beta/RC) access;
replace or edit the bullet list under the Vorabversionen section so it
explicitly states the prerelease policy (e.g., whether users with
expired/unenforced licenses can or cannot access Betas/RCs, any exceptions, and
how to regain access), updating the bullets that mirror the "Lizenz nicht
verlängert" content and referencing the section header "Vorabversionen" and the
existing bullet items to ensure the wording clarifies Beta/RC access rules and
differs from the other license-not-extended paragraph.
Comment on lines
+152
to
+160
| | Lizenzstufe | %%Parity\|parity%%-Protected %%Array\|array%% | Benannte Pools | Geräte pro Pool | Gesamte Speichergeräte | | ||
| | ------------ | --------------------------------------------- | -------------- | --------------- | ---------------------- | | ||
| | Starter | Bis zu 6 | 1 | Bis zu 6 | 6 | | ||
| | Unbeschränkt | Up to 30 (28 data + 2 %%parity\|parity%%) | Bis zu 35 | Bis zu 60 | Unbegrenzt\* | | ||
| | Lebenslang | Up to 30 (28 data + 2 %%parity\|parity%%) | Bis zu 35 | Bis zu 60 | Unbegrenzt\* | | ||
|
|
||
| </div> | ||
|
|
||
| - _„Unbegrenzt“ bedeutet, dass Sie nicht durch die Lizenz, sondern durch Hardware- und Betriebssystemeinschränkungen begrenzt sind. Zusätzliche Speichermedien können für virtuelle Maschinen, nicht zugewiesene Geräte oder andere Unraid-Funktionen verwendet werden._ | ||
| \* *"Unbegrenzt" bedeutet, dass Sie nicht durch die Lizenz, sondern durch Hardware- und Betriebssystemeinschränkungen begrenzt sind. Zusätzliche Speichermedien können für virtuelle Maschinen, nicht zugewiesene Geräte oder andere Unraid-Funktionen verwendet werden.* |
Contributor
There was a problem hiding this comment.
Update the per-pool limit for Unbeschränkt/Lebenslang.
The table still says Bis zu 60 devices per pool, which is stale for current licenses and makes this translated limits table factually wrong.
Proposed fix
-| Unbeschränkt | Up to 30 (28 data + 2 %%parity\|parity%%) | Bis zu 35 | Bis zu 60 | Unbegrenzt\* |
-| Lebenslang | Up to 30 (28 data + 2 %%parity\|parity%%) | Bis zu 35 | Bis zu 60 | Unbegrenzt\* |
+| Unbeschränkt | Bis zu 30 (28 Daten + 2 %%parity\|parity%%) | Bis zu 35 | Bis zu 200 | Unbegrenzt\* |
+| Lebenslang | Bis zu 30 (28 Daten + 2 %%parity\|parity%%) | Bis zu 35 | Bis zu 200 | Unbegrenzt\* |📝 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
| | Lizenzstufe | %%Parity\|parity%%-Protected %%Array\|array%% | Benannte Pools | Geräte pro Pool | Gesamte Speichergeräte | | |
| | ------------ | --------------------------------------------- | -------------- | --------------- | ---------------------- | | |
| | Starter | Bis zu 6 | 1 | Bis zu 6 | 6 | | |
| | Unbeschränkt | Up to 30 (28 data + 2 %%parity\|parity%%) | Bis zu 35 | Bis zu 60 | Unbegrenzt\* | | |
| | Lebenslang | Up to 30 (28 data + 2 %%parity\|parity%%) | Bis zu 35 | Bis zu 60 | Unbegrenzt\* | | |
| </div> | |
| - _„Unbegrenzt“ bedeutet, dass Sie nicht durch die Lizenz, sondern durch Hardware- und Betriebssystemeinschränkungen begrenzt sind. Zusätzliche Speichermedien können für virtuelle Maschinen, nicht zugewiesene Geräte oder andere Unraid-Funktionen verwendet werden._ | |
| \* *"Unbegrenzt" bedeutet, dass Sie nicht durch die Lizenz, sondern durch Hardware- und Betriebssystemeinschränkungen begrenzt sind. Zusätzliche Speichermedien können für virtuelle Maschinen, nicht zugewiesene Geräte oder andere Unraid-Funktionen verwendet werden.* | |
| | Lizenzstufe | %%Parity\|parity%%-Protected %%Array\|array%% | Benannte Pools | Geräte pro Pool | Gesamte Speichergeräte | | |
| | ------------ | --------------------------------------------- | -------------- | --------------- | ---------------------- | | |
| | Starter | Bis zu 6 | 1 | Bis zu 6 | 6 | | |
| | Unbeschränkt | Bis zu 30 (28 Daten + 2 %%parity\|parity%%) | Bis zu 35 | Bis zu 200 | Unbegrenzt\* | | |
| | Lebenslang | Bis zu 30 (28 Daten + 2 %%parity\|parity%%) | Bis zu 35 | Bis zu 200 | Unbegrenzt\* | | |
| </div> | |
| \* *"Unbegrenzt" bedeutet, dass Sie nicht durch die Lizenz, sondern durch Hardware- und Betriebssystemeinschränkungen begrenzt sind. Zusätzliche Speichermedien können für virtuelle Maschinen, nicht zugewiesene Geräte oder andere Unraid-Funktionen verwendet werden.* |
🧰 Tools
🪛 LanguageTool
[style] ~154-~154: Stilistisch kann es schöner sein, Doppelungen ganzer Phrasen in einem Satz zu vermeiden.
Context: ... | 1 | Bis zu 6 | 6 | | Unbeschränkt...
(DOPPELUNGEN_PHRASEN)
[style] ~155-~155: Bei bestimmten Textarten und Formulierungen bietet es sich an, eine deutschsprachige Alternative zu benutzen.
Context: ... | | Unbeschränkt | Up to 30 (28 data + 2 %%parity|parity%%) ...
(ALTERNATIVEN_FUER_ANGLIZISMEN)
[style] ~156-~156: Bei bestimmten Textarten und Formulierungen bietet es sich an, eine deutschsprachige Alternative zu benutzen.
Context: ...begrenzt* | | Lebenslang | Up to 30 (28 data + 2 %%parity|parity%%) ...
(ALTERNATIVEN_FUER_ANGLIZISMEN)
[grammar] ~159-~159: Korrigiere die Fehler
Context: ... | Unbegrenzt* | * *"Unbegrenzt" bedeutet, dass Sie nicht...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~160-~160: Ersetze das Satzzeichen
Context: ... | Unbegrenzt* | * *"Unbegrenzt" bedeutet, dass Sie nicht durch die Lize...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
🤖 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/licensing-faq.mdx`
around lines 152 - 160, Update the per-pool device limit in the table rows for
the "Unbeschränkt" and "Lebenslang" license entries from "Bis zu 60" to "Bis zu
200" (the columns showing devices per pool and any related English snippets like
"Up to 30..." may remain unchanged except where the per-pool cell currently
reads "Bis zu 60"); edit the table cells in licensing-faq.mdx for the rows
labeled "Unbeschränkt" and "Lebenslang" so the "Geräte pro Pool" column reflects
"Bis zu 200" and ensure any adjacent explanatory note about limits still
applies.
Comment on lines
+14
to
+20
| Haz siempre una copia de seguridad de tu dispositivo de arranque de Unraid después de realizar cambios significativos en la configuración. Se recomiendan *encarecidamente* las copias de seguridad regulares. | ||
|
|
||
| Para respaldar tu dispositivo flash, ve a la pestaña **Principal**, selecciona el dispositivo y haz clic en **Copia de seguridad Flash**. | ||
| Para hacer una copia de seguridad de tu dispositivo de arranque, ve a la pestaña **Principal**, selecciona el dispositivo y haz clic en **Copia de seguridad del dispositivo de arranque**. | ||
|
|
||
| :::warning | ||
|
|
||
| Guarda copias de seguridad fuera del %%array|array%% de Unraid para un fácil acceso si el %%array|array%% no está operativo. [Obtén más información sobre la gestión de dispositivos flash aquí](../../system-administration/maintain-and-update/changing-the-flash-device.mdx). | ||
| Guarda copias de seguridad fuera del %%array|array%% de Unraid para facilitar el acceso si el %%array|array%% no está operativo. [Obtén más información sobre la gestión del dispositivo de arranque aquí](../../system-administration/maintain-and-update/changing-the-flash-device.mdx). |
Contributor
There was a problem hiding this comment.
Keep the click path aligned with the existing Flash backup UI.
The prose can say dispositivo de arranque, but the action users click is still the Flash backup feature. Renaming that control here makes the WebGUI path harder to follow.
Based on learnings, Unraid's flash backup feature (accessed via Main tab → Flash device → FLASH BACKUP) creates complete installation ZIP files that include both the Unraid OS and user configuration. These backup ZIPs are compatible with the USB Flash Creator's "Use custom" option for restoring to new flash devices.
🧰 Tools
🪛 LanguageTool
[style] ~14-~14: Se recomienda emplear una alternativa al verbo comodín ‘realizar’.
Context: ...sitivo de arranque de Unraid después de realizar cambios significativos en la configurac...
(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/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx`
around lines 14 - 20, Replace the UI action text "Copia de seguridad del
dispositivo de arranque" with the exact label used in the WebGUI (FLASH BACKUP)
so the click path matches the interface; keep "dispositivo de arranque" in the
explanatory prose if desired, but ensure the clickable control is referred to as
"FLASH BACKUP" (or "FLASH BACKUP (Copia de seguridad)" if you want bilingual) in
the sentence that describes navigating Main → Flash device → ... so users can
find the control in the UI.
|
|
||
| ## Actualización | ||
|
|
||
| For step-by-step instructions, see [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)? |
Contributor
There was a problem hiding this comment.
Translate this English sentence to Spanish.
This line contains English text within a Spanish release notes document. Spanish readers will encounter mixed-language content.
🌐 Suggested Spanish translation
-For step-by-step instructions, see [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)?
+Para obtener instrucciones paso a paso, consulta [Actualizar Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). ¿Preguntas sobre tu [licencia](/unraid-os/troubleshooting/licensing-faq/)?📝 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
| For step-by-step instructions, see [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)? | |
| Para obtener instrucciones paso a paso, consulta [Actualizar Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). ¿Preguntas sobre tu [licencia](/unraid-os/troubleshooting/licensing-faq/)? |
🧰 Tools
🪛 LanguageTool
[grammar] ~9-~9: Cambia la palabra o signo.
Context: ...maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/trouble...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~9-~9: Cambia la palabra o signo.
Context: ...nd-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooti...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~9-~9: Cambia la palabra o signo.
Context: ...ate/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/li...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
[grammar] ~9-~9: Cambia la palabra o signo.
Context: ...grading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-f...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
🤖 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.4.md`
at line 9, Translate the English sentence "For step-by-step instructions, see
[Upgrading
Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/).
Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)?" into
Spanish and replace the existing line in the release notes; keep the links and
their markdown text intact (e.g., preserve "[Upgrading Unraid]" and "[license]")
so the URLs remain unchanged and produce a natural Spanish sentence such as
"Para instrucciones paso a paso, consulte [Actualizar
Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/).
¿Preguntas sobre su [licencia](/unraid-os/troubleshooting/licensing-faq/)?"
ensuring punctuation and question mark usage are correct.
Comment on lines
+155
to
+156
| | Desatado | Hasta 30 (28 datos + 2 %%paridad\|parity%%) | Hasta 35 | Hasta 60 | Ilimitado\* | | ||
| | De por Vida | Hasta 30 (28 datos + 2 %%paridad\|parity%%) | Hasta 35 | Hasta 60 | Ilimitado\* | |
Contributor
There was a problem hiding this comment.
Update per-pool limits for Unleashed/Lifetime to current value.
Line 155 and Line 156 still show Hasta 60 dispositivos por pool. This should be updated to 200 to match current licensing limits.
Proposed fix
-| Desatado | Hasta 30 (28 datos + 2 %%paridad\|parity%%) | Hasta 35 | Hasta 60 | Ilimitado\* |
-| De por Vida | Hasta 30 (28 datos + 2 %%paridad\|parity%%) | Hasta 35 | Hasta 60 | Ilimitado\* |
+| Desatado | Hasta 30 (28 datos + 2 %%paridad\|parity%%) | Hasta 35 | Hasta 200 | Ilimitado\* |
+| De por Vida | Hasta 30 (28 datos + 2 %%paridad\|parity%%) | Hasta 35 | Hasta 200 | Ilimitado\* |Based on learnings: As of Unraid 7.2.1, the maximum devices per pool limit for Unleashed and Lifetime licenses is 200.
🤖 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/licensing-faq.mdx`
around lines 155 - 156, Update the per-pool device limits for the
Unleashed/Lifetime license rows by replacing the "Hasta 60" value with "Hasta
200" in the table cells for the rows labeled "Desatado" and "De por Vida" (the
cells currently showing "Hasta 60" should become "Hasta 200") so the table
reflects the current 7.2.1 licensing limits.
|
|
||
| ## Mise à niveau | ||
|
|
||
| For step-by-step instructions, see [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)? |
Contributor
There was a problem hiding this comment.
Translate the upgrade guidance line to French.
Line 9 is still English in a French release-note page, which breaks localization consistency.
Proposed fix
-For step-by-step instructions, see [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)?
+Pour des instructions étape par étape, consultez [Mettre à niveau Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Des questions sur votre [licence](/unraid-os/troubleshooting/licensing-faq/) ?📝 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
| For step-by-step instructions, see [Upgrading Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)? | |
| Pour des instructions étape par étape, consultez [Mettre à niveau Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/). Des questions sur votre [licence](/unraid-os/troubleshooting/licensing-faq/) ? |
🤖 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.4.md`
at line 9, The French release-notes page still contains the English sentence
"For step-by-step instructions, see [Upgrading
Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/).
Questions about your [license](/unraid-os/troubleshooting/licensing-faq/)?" —
replace that entire sentence with a French translation while keeping the same
markdown link targets; for example use "Pour des instructions étape par étape,
consultez [Mise à niveau
d'Unraid](/unraid-os/system-administration/maintain-and-update/upgrading-unraid/).
Des questions concernant votre
[licence](/unraid-os/troubleshooting/licensing-faq/) ?" and ensure this change
is made in
i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
where the original English sentence appears.
| - **Plus grand que 2 To** : Utilise toujours un partitionnement GPT | ||
|
|
||
| - À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB pour les dispositifs rotatifs et à 1MiB pour les dispositifs non rotatifs, quel que soit le style de partition.\n -- Toujours [sauvegarder votre clé USB](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups) avant de commencer ce processus de conversion. | ||
| - À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB pour les dispositifs rotatifs et à 1MiB pour les dispositifs non rotatifs, quel que soit le style de partition.\n -- Toujours [sauvegarder votre clé USB](/unraid-os/system-administration/secure-your-server/secure-your-boot-drive/#backups) avant de commencer ce processus de conversion. |
Contributor
There was a problem hiding this comment.
Fix malformed Markdown in Line 272 (literal \n + broken list nesting).
Line 272 currently mixes escaped newline text and a double-hyphen fragment, which will likely render as broken content instead of a proper bullet/sub-bullet.
Proposed fix
-- À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB pour les dispositifs rotatifs et à 1MiB pour les dispositifs non rotatifs, quel que soit le style de partition.\n -- Toujours [sauvegarder votre clé USB](/unraid-os/system-administration/secure-your-server/secure-your-boot-drive/#backups) avant de commencer ce processus de conversion.
+- À partir d'Unraid OS 6.9, la partition 1 commence à 32 KiB pour les dispositifs rotatifs et à 1 MiB pour les dispositifs non rotatifs, quel que soit le style de partition.
+ - Toujours [sauvegarder votre clé USB](/unraid-os/system-administration/secure-your-server/secure-your-boot-drive/#backups) avant de commencer ce processus de conversion.🧰 Tools
🪛 LanguageTool
[typographical] ~272-~272: Ces deux traits d’union peuvent être associés pour former un tiret.
Context: ...quel que soit le style de partition.\n -- Toujours [sauvegarder votre clé USB](/u...
(TIRET)
🤖 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/troubleshooting/faq.mdx`
at line 272, The line containing the literal "\n --" in the sentence beginning
"À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB..." is malformed
Markdown; replace the escaped newline and double-hyphen fragment with proper
Markdown structure by ending the sentence and putting the "Toujours [sauvegarder
votre clé
USB](/unraid-os/system-administration/secure-your-server/secure-your-boot-drive/#backups)
avant de commencer ce processus de conversion." on its own as either a new
paragraph or a proper bullet/sub-bullet so the link renders correctly.
| ### Comment installer manuellement mon fichier de clé de licence sur mon périphérique USB ? {#manual-keyfile-install} | ||
|
|
||
| #### Méthode manuelle (hors ligne) | ||
| #### Comment installer manuellement mon fichier de clé de licence sur mon périphérique USB ? {#manual-keyfile-install} |
Contributor
There was a problem hiding this comment.
Remove the duplicate manual-keyfile-install heading/anchor.
Line 93 repeats the same section title and explicit anchor already defined at Line 91, creating an ID collision risk.
Proposed fix
-#### Comment installer manuellement mon fichier de clé de licence sur mon périphérique USB ? {`#manual-keyfile-install`}📝 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
| #### Comment installer manuellement mon fichier de clé de licence sur mon périphérique USB ? {#manual-keyfile-install} |
🤖 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/troubleshooting/licensing-faq.mdx`
at line 93, There's a duplicate section heading/anchor "#### Comment installer
manuellement mon fichier de clé de licence sur mon périphérique USB ?
{`#manual-keyfile-install`}" causing an ID collision; remove the second occurrence
(the repeated heading/anchor) so only the original "manual-keyfile-install"
anchor remains and update surrounding content if needed to preserve flow; ensure
no other duplicate IDs exist in the file.
Comment on lines
+152
to
+157
| | Niveau de Licence | %%Parité\|parity%%-Protégé %%Tableau\|array%% | Pools Nommés | Périphériques par Pool | Total des Dispositifs de Stockage | | ||
| | ----------------- | ---------------------------------------------- | ------------ | ---------------------- | --------------------------------- | | ||
| | Débutant | Jusqu’à 6 | 1 | Jusqu’à 6 | 6 | | ||
| | Libéré | Jusqu'à 30 (28 données + 2 %%parity\|parity%%) | Jusqu’à 35 | Jusqu’à 60 | Illimité\* | | ||
| | À Vie | Jusqu'à 30 (28 données + 2 %%parity\|parity%%) | Jusqu’à 35 | Jusqu’à 60 | Illimité\* | | ||
|
|
Contributor
There was a problem hiding this comment.
Update per-pool device limits for Unleashed/Lifetime.
The table still lists “Jusqu’à 60” devices per pool for Unleashed and Lifetime, but current limits should be 200.
Proposed fix
-| Libéré | Jusqu'à 30 (28 données + 2 %%parity\|parity%%) | Jusqu’à 35 | Jusqu’à 60 | Illimité\* |
-| À Vie | Jusqu'à 30 (28 données + 2 %%parity\|parity%%) | Jusqu’à 35 | Jusqu’à 60 | Illimité\* |
+| Libéré | Jusqu'à 30 (28 données + 2 %%parity\|parity%%) | Jusqu’à 35 | Jusqu’à 200 | Illimité\* |
+| À Vie | Jusqu'à 30 (28 données + 2 %%parity\|parity%%) | Jusqu’à 35 | Jusqu’à 200 | Illimité\* |Based on learnings: As of Unraid 7.2.1, the maximum devices per pool limit for Unleashed and Lifetime licenses is 200 (increased from previous limits of 60 in 6.12 and 120 in later versions).
📝 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
| | Niveau de Licence | %%Parité\|parity%%-Protégé %%Tableau\|array%% | Pools Nommés | Périphériques par Pool | Total des Dispositifs de Stockage | | |
| | ----------------- | ---------------------------------------------- | ------------ | ---------------------- | --------------------------------- | | |
| | Débutant | Jusqu’à 6 | 1 | Jusqu’à 6 | 6 | | |
| | Libéré | Jusqu'à 30 (28 données + 2 %%parity\|parity%%) | Jusqu’à 35 | Jusqu’à 60 | Illimité\* | | |
| | À Vie | Jusqu'à 30 (28 données + 2 %%parity\|parity%%) | Jusqu’à 35 | Jusqu’à 60 | Illimité\* | | |
| | Niveau de Licence | %%Parité\|parity%%-Protégé %%Tableau\|array%% | Pools Nommés | Périphériques par Pool | Total des Dispositifs de Stockage | | |
| | ----------------- | ---------------------------------------------- | ------------ | ---------------------- | --------------------------------- | | |
| | Débutant | Jusqu'à 6 | 1 | Jusqu'à 6 | 6 | | |
| | Libéré | Jusqu'à 30 (28 données + 2 %%parity\|parity%%) | Jusqu'à 35 | Jusqu'à 200 | Illimité\* | | |
| | À Vie | Jusqu'à 30 (28 données + 2 %%parity\|parity%%) | Jusqu'à 35 | Jusqu'à 200 | Illimité\* | |
🤖 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/troubleshooting/licensing-faq.mdx`
around lines 152 - 157, Update the per-pool device limit cells in the licensing
table: change the "Périphériques par Pool" value for the "Libéré" and "À Vie"
rows from "Jusqu’à 60" to "Jusqu’à 200" to reflect the Unleashed/Lifetime limit;
locate the table rows containing the unique row identifiers "Libéré" and "À Vie"
and edit their corresponding "Périphériques par Pool" column entries
accordingly.
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
Localization