New Crowdin updates #379
New Crowdin updates #379
Conversation
|
Warning Rate limit exceeded@elibosley has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 2 minutes and 50 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (179)
📝 WalkthroughWalkthroughUpdates localized German and Spanish documentation across many areas: API, setup, storage/array management, system administration, troubleshooting, VMs/containers, Unraid Connect, release notes, and new account management pages; primarily content, formatting, reorganization, and new MDX files (no code/behavioral changes). Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 119
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (44)
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (3)
148-179: Duplicate section: "Lizenzverwaltung" appears twice.The section heading "Lizenzverwaltung" (License Management) is defined at line 148 and again at line 168 with different content blocks. The first instance (lines 148–164) covers dashboard customization via tabs; the second (lines 168–179) covers license key management. These are distinct topics that should have separate, uniquely-named section headings.
Consolidate these sections by renaming one of them. For example:
- ## Lizenzverwaltung + ## Anpassung der Benutzeroberfläche Die Verwaltung Ihrer Lizenzen in Unraid Connect ist einfach. Unter dem Abschnitt **Meine Schlüssel** können Sie:Then retain only one "Lizenzverwaltung" section for the actual license key management (lines 168–179).
208-230: Duplicate uninstallation instructions and fragmented structure.Lines 208–214 contain uninstallation consequences without a section header, and lines 217–224 repeat nearly identical content under the "Deinstallation des Plugins" heading. Additionally, the text fragments at lines 200 and 208 ("Wenn Sie sich abmelden:" and "Wenn Sie das Unraid Connect Plugin deinstallieren:") appear orphaned, suggesting incomplete section consolidation during localization sync.
Remove the duplicate block (lines 208–214) and ensure the content under "Deinstallation des Plugins" (lines 217–224) is the single source of truth. Also, consolidate the orphaned text fragments by integrating them into proper section headers or removing them if redundant:
- Wenn Sie sich abmelden: - - --- - - ## Abmeldung + ## Abmeldung Sie können sich jederzeit von Unraid Connect abmelden über ***Einstellungen → Verwaltungszugriff → Unraid Connect → Kontostatus***, indem Sie auf die **Abmelden**-Schaltfläche klicken. - - Wenn Sie das Unraid Connect Plugin deinstallieren: - - - Alle Flash-Backup-Dateien werden deaktiviert und von Ihrem lokalen Flash-Laufwerk gelöscht. - - Cloud-Backups sind zur Entfernung von Unraid-Servern markiert; sie werden für 30 Tage aufbewahrt, danach werden sie dauerhaft gelöscht. Für eine sofortige Löschung, [deaktivieren Sie Flash-Backup](./automated-flash-backup.mdx), bevor Sie es deinstallieren. - - Der Fernzugriff wird deaktiviert. Stellen Sie sicher, dass Sie alle zugehörigen Portweiterleitungsregeln von Ihrem Router entfernen. - - Ihr Server wird von Unraid.net abgemeldet.
181-202: Fragmented section structure with broken flow.Lines 181–202 show disjointed content: line 181 introduces language settings ("Um die Spracheinstellung zu ändern:"), followed by a horizontal rule (line 183), then the actual "Sprachlokalisierung" section (line 185), followed by more text, another rule, and finally "Abmeldung" (line 204). The orphaned introductory text at line 181 should either be removed or properly integrated into the "Sprachlokalisierung" section.
Remove the orphaned text and consolidate the section:
- Um die Spracheinstellung zu ändern: - - --- - ## Sprachlokalisierungi18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx (1)
110-114: Duplication: Troubleshooting content repeated in caution block.Lines 110–114 repeat the troubleshooting paragraph from line 92. This redundancy should be removed—keep only one version. If this caution block is the authoritative location, remove or consolidate line 92; otherwise, consolidate into the caution block.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx (2)
108-118: Duplicate section: "Wiederherstellung von einem verlorenen Flash-Gerät ohne Backup" appears twice.Lines 108-118 and 139-177 both define the same section, though at different heading levels (### vs ##). Consolidate into a single section to avoid redundancy and confusion.
Also applies to: 139-177
139-177: Mixed English and German content in recovery section.Lines 143-177 contain significant English text interspersed with German, including:
- Line 145: "Never assign a data disk as a %%parity drive|parity-drives%%" (English)
- Lines 149-155: Mix of English ("Parity drives," "do not have," "do not mount") and inline German references
- Line 162: "Note the serial numbers..." (English)
- Line 166: "Go to Tools → New Config" (English)
This German localization file should have all instructional text in German. Translate these sections to German or determine if this is intentionally mixed-language documentation.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (1)
38-52: Clarify misplaced content in "Laufwerktests und Überwachung" section.Lines 40 contains text about Windows/PuTTY that appears out of context for a section titled "Drive Tests and Monitoring" (Laufwerktests und Überwachung). This content reappears at line 30 in the tip block, suggesting it was incorrectly placed or duplicated during reorganization.
Please verify the intended content for this section. If the PuTTY guidance should not appear here, remove lines 40–43.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx (1)
62-121: Critical: Duplicate and incomplete troubleshooting sections. The troubleshooting details contain duplicates and incomplete entries that degrade user experience:
- Lines 68-77 vs. 99-109: "VMs zeigen 'Kann Schnittstellen-MTU nicht abrufen' oder Netzwerkfehler" appears twice, identically.
- Lines 79-87 vs. 111-115: "VNC-Zugriff auf VMs funktioniert nicht oder ist langsam" appears twice; the second occurrence (lines 111-115) is truncated and omits critical steps about network bridge configuration and VM Manager settings.
- Lines 89-97 vs. 117-121: "VM wird nicht booten (EFI-Shell erscheint)" appears twice; the second occurrence (lines 117-121) is an incomplete fragment.
These duplicates create confusion and the incomplete sections leave users without full guidance. Remove the duplicate entries and ensure all troubleshooting content is complete and consistent.
Remove lines 99-121 and replace with clean, non-duplicated troubleshooting sections:
</details> -<details> - <summary><strong>VMs zeigen "Kann Schnittstellen-MTU nicht abrufen" oder Netzwerkfehler</strong> - Klicken zum Expandieren/Reduzieren</summary> - - Wenn Sie %%OVMF|ovmf%%-basierte %%VMs|vm%% in älteren Unraid-Versionen erstellt haben, könnten Sie auf eine EFI-Shell stoßen. Sie können die %%VM|vm%% starten, indem Sie die folgenden Befehle eingeben: - - 1. Geben Sie `fs0:` ein. - 2. Geben Sie dann `cd efi/boot` ein. - 3. Schließlich geben Sie `bootx64.efi` ein. - - Wenn `fs0:` nicht funktioniert, können Sie stattdessen `fs1:` versuchen. Wenn weiterhin Probleme auftreten, besuchen Sie bitte das [Unraid-Forum](https://forums.unraid.net/) für Unterstützung. -</details> - -<details> - <summary><strong>VNC-Zugriff auf VMs funktioniert nicht oder ist langsam</strong> - Klicken zum Expandieren/Reduzieren</summary> - - Um dieses Problem zu lösen, bearbeiten Sie die %%VM|vm%% im %%WebGUI|web-gui%% und klicken Sie auf **Anwenden**, ohne Änderungen vorzunehmen. Diese Aktion aktualisiert den Maschinentyp auf die neueste unterstützte Version. -</details> - -<details> - <summary><strong>VM wird nicht booten (EFI-Shell erscheint)</strong> - Klicken zum Expandieren/Reduzieren</summary> - - Wenn Sie %%OVMF|ovmf%%-basierte %%VMs|vm%% in älteren Unraid-Versionen erstellt haben, könnten Sie auf eine EFI-Shell stoßen. Sie können die %%VM|vm%% starten, indem Sie die folgenden Befehle eingeben: -</details> ---i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)
51-77: Fix incorrect section heading: First "BIOS-Empfehlungen" should be "Registrieren Sie Ihren Lizenzschlüssel".The German file has a structural error caused by a localization mistake. Lines 51–73 are labeled "## BIOS-Empfehlungen" but contain license key registration content (Getting Started, account creation, trial key, license management). This section should match the English source heading at line 51: "## Register your license key."
The actual BIOS checklist correctly appears at line 75 as "## BIOS-Empfehlungen," but the incorrect first heading creates a duplicate and misaligned structure.
Rename the heading at line 51 to reflect its license-key focus (e.g., "## Registrieren Sie Ihren Lizenzschlüssel") to align with the English source and remove the semantic duplication.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx (2)
56-75: Restructure confusing RAM overclocking section.The section duplicates the header "Risiken der Übertaktung:" (lines 56 and 65) with unclear organization:
- Line 56: Bold header
- Lines 58–61: Caution block with "Fehlerbehebung"
- Line 65: Header repeated
- Lines 67–70: Risk list
The logical flow is muddled. Consider consolidating into a single "Risiken der Übertaktung" section with the risk list directly following, and place the troubleshooting tip/caution in a better-positioned block (e.g., after the risks or in a separate subsection).
189-189: Translate untranslated English content.Line 189 contains English text in a German localization file: "Consider running extended %%SMART|smart%% tests for suspect drives."
Translate to German to maintain localization consistency.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/managing-and-customizing-containers.mdx (1)
116-164: Refactor: Remove duplicated "Volume-Mappings" section and reorganize misplaced content.This section has significant structural issues:
Lines 140–152 and 156–164 are near-duplicates: Both repeat the heading "Volume-Mappings innerhalb eines Containers" and the intro about container-path vs. host-path (lines 142 and 158 are identical).
Health status indicators (🟢, 🟡, ⚪) at lines 144–146 are misplaced: These describe container health states and logically belong in the "Gesundheitsindikator" section (line 116), not within volume-mappings. Moving them back will clarify the structure.
User Scripts scheduling content at line 160 disrupts flow: This bridges into the "Planung von Start und Stopp" section (line 190), creating a confusing intermediate state.
Suggested reorganization:
- Keep the "Gesundheitsindikator" section (lines 116–139) and ensure health status indicators stay there.
- Consolidate "Volume-Mappings innerhalb eines Containers" into a single, non-repeated section (lines 140–152 or 156–164, not both).
- Move the User Scripts content to the dedicated "Planung von Start und Stopp" section (line 190) where it logically belongs.
- Remove the duplicate section header and intro.
This will improve clarity and eliminate redundancy.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-zfs.mdx (1)
21-28: Remove duplicate reference text.Lines 23-24 and lines 27-28 contain identical text about referencing the ZFS storage documentation. The duplicate at the end (lines 27-28) should be removed, as the info block already provides this reference.
:::info Für eine umfassende Anleitung zu %%ZFS|zfs%% Dateisystemen besuchen Sie den speziellen [ZFS-Speicherabschnitt](../../../advanced-configurations/optimize-storage/zfs-storage.mdx). ::: - - Für eine umfassende Anleitung zu %%ZFS|zfs%% Dateisystemen besuchen Sie den speziellen [ZFS-Speicherabschnitt](../../../advanced-configurations/optimize-storage/zfs-storage.mdx).i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdx (1)
22-26: Remove duplicate introductory sentence.The introductory line at line 22 ("Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen:") is repeated identically at line 26, immediately before the attributes table. This appears to be unintended duplication introduced during content restructuring.
Apply this diff to remove the duplicate:
## Wie Unraid SMART nutzt Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen: Für eine genauere Betrachtung der Daten eines Laufwerks von %%SMART|smart%%, klicken Sie auf dessen Namen im **Main**-Tab der Unraid %%WebGUI|web-gui%%. -Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen: - | **ID** | **Attribut** | **Was es bedeutet** | **Wann man besorgt sein sollte / Maßnahmen, die zu ergreifen sind** |i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (1)
92-104: Duplicate section headers and redundant content structure.The documentation now has two sections with similar naming and content:
- Lines 92–94: "Backups-Verschlüsselung" discussing encryption status
- Lines 99–104: "Datenschutz und Sicherheit" section with subsection "Backups-Verschlüsselung" (101–103) repeating nearly identical encryption information
Additionally, lines 23–45 already contain a "Datenerfassung und Datenschutz" collapsible section, creating structural redundancy.
Consolidate the privacy and security sections to eliminate duplication and improve clarity.
Consider restructuring as:
- ## Backups-Verschlüsselung - - Derzeit werden Flash-Backups ohne Verschlüsselung in der Cloud gespeichert. Vorsichtshalber werden sensible Daten - einschließlich aller Benutzer- und Root-Passwörter sowie alle %%WireGuard|wireguard%%-Schlüssel - nie im Backup enthalten. - - ... - - ## Datenschutz und Sicherheit - - ### Backups-Verschlüsselung - - Derzeit werden Flash-Backups ohne Verschlüsselung in der Cloud gespeichert. Vorsichtshalber werden sensible Daten - einschließlich aller Benutzer- und Root-Passwörter sowie alle %%WireGuard|wireguard%%-Schlüssel - nie im Backup enthalten. + + ## Datenschutz und Sicherheit + + ### Backups-Verschlüsselung + + Derzeit werden Flash-Backups ohne Verschlüsselung in der Cloud gespeichert. Vorsichtshalber werden sensible Daten - einschließlich aller Benutzer- und Root-Passwörter sowie alle %%WireGuard|wireguard%%-Schlüssel - nie im Backup enthalten.i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx (2)
50-62: Resolve duplicate section heading structure.Lines 50 and 54 both define
Benutzeroberflächenverbesserungenat different heading levels (### vs ##). The section at line 50 appears to be a subset of completed/in-progress items, while line 54 covers planned features. Clarify the intent: either consolidate into a single section with appropriate subsections, or rename one to avoid confusion.
104-117: Resolve duplicate "Plugin-System" section and clarify semantic organization.Lines 104 and 109 define
Plugin-Systemat different heading levels (### vs ##). Additionally, the bullets at lines 106–107 describe storage share operations, not plugin system features. Either relocate these bullets to the "Freigabeverwaltung" section or clarify the intended structure.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx (1)
52-56: Critical: English content in German section.Line 54 contains English text about Mover logging that must be translated to German. Additionally, lines 54–56 appear to duplicate the system shutdown guidance from lines 47–50, creating redundancy.
Replace lines 54–56 with corrected German content (removing duplication):
-By default, diagnostics are automatically anonymized. If you enable %%Mover|mover%% logging under ***Settings → Scheduler → Mover Settings***, the %%syslog|syslog%% will include details about files the %%Mover|mover%% processes. It's best to allow %%Mover|mover%% logging only when troubleshooting specific %%Mover|mover%%-related issues, as it may reveal file paths and names. - -When your system shuts down gracefully, the session log is saved automatically to the flash drive. You can access it after rebooting by going to ***Tools → Syslog → syslog-previous***. This log is also included in diagnostics on the next boot. However, if the system crashes, the system log will be lost. In these cases, enabling %%syslog|syslog%% mirroring to the flash or using a remote %%syslog server|syslog-server%% is recommended to preserve logs for troubleshooting. +Standardmäßig werden Diagnosen automatisch anonymisiert. Wenn Sie das %%Mover|mover%% Protokollieren unter ***Einstellungen → Scheduler → Mover-Einstellungen*** aktivieren, werden die %%syslog|syslog%% Details über die vom %%Mover|mover%% verarbeiteten Dateien enthalten. Es ist am besten, das %%Mover|mover%% Protokollieren nur bei der Fehlerbehebung spezifischer %%Mover|mover%%-bezogener Probleme zu aktivieren, da es Dateipfade und Namen offenbaren kann.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx (3)
415-427: Translate English paragraphs in "Eingeschlossene oder ausgeschlossene Laufwerke" section.Lines 415-427 contain untranslated English content describing included/excluded disk behavior:
-Unraid first checks any included disks, then looks at excluded disks to determine where to store a file. After that, it uses the %%split level|split-level%% and %%allocation method|allocation-method%% to select an appropriate disk. +Unraid prüft zunächst alle eingeschlossenen Festplatten und prüft dann ausgeschlossene Festplatten, um zu bestimmen, wo eine Datei gespeichert werden soll. Danach wird das %%Split-Level|split-level%% und die %%Zuweisungsmethode|allocation-method%% verwendet, um eine geeignete Festplatte auszuwählen. -The settings for %%included and excluded disks|included-or-excluded-disks%% only affect where new files can be saved. Any existing files in folders that match your share name will still be accessible for reading, even if they're on a different disk. +Die Einstellungen für %%Ein-/Ausgeschlossene Laufwerke|included-or-excluded-disks%% beeinflussen nur, wo neue Dateien gespeichert werden können. Alle vorhandenen Dateien in Ordnern, die Ihrem Freigabennamen entsprechen, sind weiterhin lesbar zugänglich, auch wenn sie sich auf einem anderen Laufwerk befinden.
480-480: Translate introductory paragraph about disk shares.The paragraph describing disk shares remains in English:
-Disk shares are simply individual drives or %%pools|cache-pool%% of drives within your Unraid system that can be accessed over the network. By default, these shares are turned off, but you can easily enable them in the ***Settings → Global Share Settings*** section. +Laufwerksfreigaben sind einfach einzelne Laufwerke oder %%Pools|cache-pool%% von Laufwerken in Ihrem Unraid-System, auf die über das Netzwerk zugegriffen werden kann. Standardmäßig sind diese Freigaben deaktiviert, können aber einfach in der ***Einstellungen → Globale Freigabeeinstellungen***-Sektion aktiviert werden.
490-493: Translate English content in disk share access description.Lines 490-493 contain untranslated English describing how to access disk shares:
-Once you enable them, you'll notice disk shares in the Unraid GUI under a section labeled **Disk Shares** in the **Shares** tab. Each drive in your %%array|array%% can be accessed like this: +Sobald Sie diese aktivieren, sehen Sie Laufwerksfreigaben in der Unraid-GUI unter einem Abschnitt mit der Bezeichnung **Laufwerksfreigaben** auf der Registerkarte **Freigaben**. Auf jedes Laufwerk in Ihrem %%array|array%% kann wie folgt zugegriffen werden: -- **Pools of drives:** If you have multiple drives grouped together, they will show up as `/mnt/pool-name`. The most common %%pools|cache-pool%% is called `cache`, but you can name your %%pools|cache-pool%% however you like. +- **Laufwerk-Pools:** Wenn Sie mehrere Laufwerke zusammen gruppiert haben, werden sie als `/mnt/pool-name` angezeigt. Der häufigste %%Pool|cache-pool%% wird `cache` genannt, aber Sie können Ihre %%Pools|cache-pool%% beliebig benennen.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx (1)
173-237: Remove duplicate "Verlorene Array-Konfiguration" section and fully translate to German.The section "Verlorene Array-Konfiguration" appears twice in this file (lines 173 and 223). Additionally, both sections contain English text mixed throughout despite this being German documentation—the opening paragraphs, steps 3 and 7 in the second section, and various inline content are not translated. Delete the duplicate section and ensure the retained version is completely translated to German.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx (2)
95-114: Remove duplicate boot phase sections (6 and 7).Sections for "WebGUI" and "Array" are defined twice in the document. Lines 96–102 (WebGUI) and 105–114 (Array) duplicate the expanded content already present at lines 73–84 and 87–93. The second set of blocks (96–114) should be removed.
This appears to be an artifact of the Crowdin localization merge. The expanded versions (lines 73–93) contain the updated content marked with
~and should be retained. Remove the duplicate blocks:-<details> - <summary><strong>6. WebGUI</strong> - Zum Erweitern/Kollabieren klicken</summary> - - Die webbasiertem Verwaltungsoberfläche wird verfügbar und ermöglicht die Fernadministration und -konfiguration Ihres Servers. - - - Die %%WebGUI|web-gui%% startet an diesem Punkt. - - Die Datei `config/go` auf dem Flash-Gerät kann Benutzerbefehle vor oder nach dem Start der %%WebGUI|web-gui%% ausführen. -</details> - -<details> - <summary><strong>7. Array</strong> - Zum Erweitern/Kollabieren klicken</summary> - - Speichergeräte werden eingehängt und verfügbar gemacht, was den Bootvorgang abschließt. Hier werden Ihre Daten zugänglich. - - - Wenn Autostart aktiviert ist, beginnt das %%array|array%% hier; andernfalls ist ein manueller Start erforderlich. - - Laufwerke werden als `/dev/diskX` und `/mnt/cache` (falls vorhanden) eingehängt. - - Freigaben werden im Netzwerk als `/mnt/user/sharename` verfügbar. - - Docker-Container starten in der auf der Docker-Seite angegebenen Reihenfolge mit anpassbaren Verzögerungen. - - Automatisch startende virtuelle Maschinen (%%VMs|vm%%) werden ebenfalls gestartet. -</details>
149-151: Remove duplicate content and translate English text to German.Line 149 contains the same information in German as line 151, which is in English. This creates semantic duplication and a language inconsistency in a German localization file. Remove line 151 entirely (or translate it to German if the intent was to provide additional detail).
Wenn Ihr Unraid-Bootlaufwerk ausfällt und Sie keinen aktuellen Backup oder kein Wissen darüber haben, welche Laufwerke Parität sind, können Sie Ihr System wiederherstellen, indem Sie Unraids Fähigkeit nutzen, Datenträger anhand ihrer Dateisysteme zu erkennen. %%Paritätslaufwerke|parity-drives%% haben kein gültiges Dateisystem, was sie unterscheidbar macht. -Unraid identifies data drives by detecting existing valid file systems. %%Parity drives|parity-drives%%, which lack a file system, appear unmountable. This characteristic allows you to distinguish %%parity drives|parity-drives%% from data drives after booting with a new flash device. -i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx (1)
12-39: Fix orphan block delimiter and verify bracket matching.Line 18 contains a stray
:::delimiter that disrupts the markdown block structure. The note block closes properly at line 16, but line 18 introduces an unmatched closing delimiter before the tip block begins at line 20.Additionally, LanguageTool flagged potential unpaired brackets at line 14, though the markdown link syntax appears syntactically correct. However, verify the rendered output to ensure the link displays properly.
Suggested fix:
::: -::: :::tipi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/shares-primary-storage-612.mdx (1)
15-25: Remove duplicate content and fix mixed-language text.The file contains clear structural issues:
Duplicate heading and content (lines 15-19 repeated at 21-24):
- Lines 15-19:
**Sekundärspeicher-Dropdown:**with bullet points- Lines 21-24: Identical
**Sekundärspeicher-Dropdown:**with same bullet points- Remove one duplicate section
Mixed-language text (line 25):
- Line 25 ends with English:
If the primary storage is the **Array**, **None** and any eligible %%pools|cache-pool%% are available.- This should be translated to German for consistency
Suggested fix:
**Sekundärspeicher-Dropdown:** - **None:** Kein Sekundärspeicher ist für die Freigabe festgelegt (optional). - Wenn der Primärspeicher ein %%pool|cache-pool%% ist, stehen **None**, **Array** und **Ein anderer Pool** zur Verfügung. - Sie können jeden benannten %%pool|cache-pool%% oder das %%array|array%% wählen. -**Sekundärspeicher-Dropdown:** - -- **None:** Kein Sekundärspeicher ist für die Freigabe festgelegt (optional). -- Wenn der Primärspeicher ein %%pool|cache-pool%% ist, stehen **None**, **Array** und **Ein anderer Pool** zur Verfügung. -- If the primary storage is the **Array**, **None** and any eligible %%pools|cache-pool%% are available. +- Wenn der Primärspeicher das %%array|array%% ist, stehen **None** und alle verfügbaren %%pools|cache-pool%% zur Verfügung.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx (1)
319-324: Fix unpaired brackets in info header (line 319).The info block header at line 319 contains nested brackets:
:::info[Why [Migrieren?]. Remove nesting or rephrase to avoid MDX parsing errors.-:::info[Why [Migrieren?] +:::info[Warum migrieren?]i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx (1)
99-130: Remove duplicate section header and consolidate conflicting content.Lines 99–108 and 110–130 both define section "3. Erstellen und starten Sie die VM" with similar but different content. This is a merge or editing error that will confuse users. The longer version (lines 110–130) appears more complete and should be retained; the shorter version (lines 99–108) should be removed.
The first version (lines 99–108) contains minimal steps:
- VM console access via VNC
- SMB Local Master setting
The second version (lines 110–130) is more comprehensive:
- Server name and description setup
- Display theme customization
- SMB Local Master setting
- UPS passthrough configuration
- Array startup and Community Applications installation
- System updates
Recommended fix: Delete lines 99–109 (the entire first details block).
- <details> - <summary><strong>3. Erstellen und starten Sie die VM</strong> - Zum Ein-/Ausklappen klicken</summary> - - Sobald die %%VM|vm%% läuft, richten Sie es wie einen physischen Unraid-Server ein: - - 1. Greifen Sie auf das %%WebGUI|web-gui%% der %%VM|vm%% zu unter `http://[VM-IP]`. - 2. Gehen Sie zu ***Einstellungen → Identifikation***: - 3. Klicken Sie auf der **VMs**-Registerkarte auf das Unraid %%VM|vm%%-Symbol und wählen **Start mit Konsole (%%VNC|vnc-session%%)**. - 4. Gehen Sie zu ***Einstellungen → %%SMB|samba%% Einstellungen → Arbeitsgruppeneinstellungen*** und stellen **Lokaler Master** auf *Nein*, um Konflikte zu vermeiden. - </details> - <details> <summary><strong>3. Erstellen und starten Sie die VM</strong> - Zum Ein-/Ausklappen klicken</summary> ...i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx (1)
107-170: Remove duplicate sections and fix misplaced content in Performance Optimization.The Performance Optimization section (lines 103–170) contains multiple critical issues:
- Duplicate "Windows-Indizierung deaktivieren" sections (lines 107–119 and 138–143): Both have identical headers and overlapping steps.
- Duplicate "Automatische Festplattendefragmentierung deaktivieren" (lines 121–131 and 145–157): Exact duplicate header and similar content.
- Misplaced English text: Lines 109–110 and 135–136 contain identical English descriptions for Windows Search that appear to be untranslated or incorrectly merged content.
- Duplicate "Hochleistungsmodus aktivieren" (lines 133–143 and 158–171): Overlapping section headers.
Recommended structure:
Keep only one instance of each subsection. The sections should appear in this order without duplicates:
Windows-Indizierung deaktivieren (lines 107–119) → KEEP
Automatische Festplattendefragmentierung deaktivieren (lines 121–131) → KEEP
Hochleistungsmodus aktivieren (lines 133–143) → KEEP (move to line ~133)
Remove:
- Lines 138–143 (duplicate Windows-Indizierung)
- Lines 145–157 (duplicate Automatische Festplattendefragmentierung)
- Lines 158–171 (duplicate Hochleistungsmodus)
Additionally, fix untranslated/misplaced English text:
The English description at lines 109–110 and 135–136 ("Windows Search indexing continuously scans...") should either be translated to German or integrated into the correct section description. Currently, this text appears to be in the wrong location (part of the details block header context, not as standalone prose).
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx (1)
40-58: Remove duplicate section on parity error troubleshooting.Lines 40–46 and lines 51–58 contain substantially duplicated content. The section header "What to do if you encounter %%parity|parity%% errors" appears twice (lines 40 and 51), followed by similar introductions and numbered steps. Retain only one version to avoid confusion.
-<h4>What to do if you encounter %%parity|parity%% errors</h4> - -%%Parity|parity%% errors happen when the %%parity|parity%% information your system calculates doesn't match what's stored on your %%parity drives|parity-drives%%. This mismatch can arise from several issues, including: - -~ -- **Untersuchen Sie das Problem:** Beginnen Sie mit dem Überprüfen der %%SMART-Berichte|SMART-Reports%%, die detaillierte Informationen über den Gesundheitszustand Ihrer Festplatten bieten. Achten Sie auf Hinweise auf Festplatten- oder Verbindungsprobleme. -~ -- **Hilfe in unseren Foren suchen:** Wenn Sie das Problem nicht selbst lösen können, ziehen Sie in Betracht, Rat in den Unraid-Foren einzuholen. Die Community kann wertvolle Einblicke und Vorschläge basierend auf ihren Erfahrungen bieten. -~ -- **Führen Sie eine weitere Prüfung durch:** Nachdem Sie Hardwareprobleme behoben haben, ist es eine gute Idee, eine weitere %%parity check|parity-check%% durchzuführen, um sicherzustellen, dass alles wieder in Ordnung ist. -- Unsaubere Shutdowns oder unerwartete Systemabstürze - -When %%parity|parity%% errors occur, either the %%parity drives|parity-drives%% or the data disks could be out of sync. Ideally, a %%parity check|parity-check%% should report zero errors so everything functions correctly. -i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx (1)
71-71: English content block in Spanish-locale file must be translated.Line 71 contains a full English paragraph in a Spanish-locale document. This English text should be translated to Spanish to maintain locale consistency:
New devices will appear as *Unformatted* and cannot be used until formatted. Unraid defaults to the %%XFS|xfs%% filesystem for array devices. For %%cache pools|cache-pool%%, %%BTRFS|btrfs%% is always used by default when using auto mode, but you can choose your desired filesystem when adding devices to a pool. You can change the default filesystem for the array in ***Settings → System Settings → Disk Settings***.Please translate this paragraph to Spanish or confirm if this is an unintended merge from the English source.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdx (1)
80-80: Remove erroneous backslash from note admonition tag.Line 80 has an unnecessary backslash before the opening bracket in the note admonition syntax.
Apply this diff to fix the syntax error:
-:::note\[Optionally] +:::note[Optionally]The backslash escape is not valid in this context and may cause rendering issues.
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (2)
51-75: Remove duplicate section header.The "Recomendaciones para el BIOS" section header appears twice (lines 51 and 75). This creates a confusing structure where the same section appears to start twice.
Review the content organization: either consolidate the two sections or ensure they cover different topics. The first section (lines 52–74) appears to introduce the topic, while the second (lines 75–105) provides detailed guidelines. Consider:
- Removing the first header and incorporating its intro into the second section.
- Or renaming the first header to distinguish it from the detailed checklist that follows.
33-39: Remove duplicate password recommendation.Line 39 duplicates the recommendation text from line 33: "Recomendamos usar un gestor de contraseñas para el almacenamiento seguro." Remove the duplicate.
- Recomendamos usar un gestor de contraseñas para el almacenamiento seguro. - Única - Al menos 8 caracteres de longitud. (Aunque, la mejor práctica recomienda 12+ para las contraseñas más seguras) - Una mezcla de letras, números, y caracteres especiales - Recomendamos usar un gestor de contraseñas para el almacenamiento seguro.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx (1)
154-189: Duplicate section header confirmed: "Konfigurationen, die vermieden werden sollten" at lines 154 and 189 breaks document structure.The identical section header appears twice, creating a structural error. The first instance (line 154) introduces checklist guidance and the "Komplexe Netzwerke" subsection, while the second (line 189) precedes a configuration comparison table with no content between them. Either the second header should be removed or retitled to reflect its role as a configuration reference table.
Additionally, the DNS configuration items (lines 164–172) are presented as troubleshooting guidance with checkmarks (✅) indicating best practices, not configurations to avoid—their placement and framing should align with their actual purpose.
i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)
138-179: Rename first section header—incorrect duplicate.Line 148 contains a mismatch: the "Gestión de licencias" header should be renamed to reflect its content about dashboard customization (e.g., "Personalización del panel de control" or similar). The tabs below describe customizing banners, reorganizing tiles, and changing themes—not license management. The actual license management section begins at line 168 with the duplicate header.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx (1)
129-175: Duplicate "VPN-Tunneling-Zugriff für das System konfigurieren" headers with overlapping procedural content confirmed.Lines 145–157 and 158–175 both use the identical header "VPN-Tunneling-Zugriff für das System konfigurieren" but describe different configuration workflows:
- First section (lines 145–157): Ends with DNS leak testing via dnsleaktest.com
- Second section (lines 158–175): Uses IP address verification via whatismyipaddress.com with additional critical notes on DNS, updates, and tunnel limits
Additionally, the "Testen des Systemtunnels" section (line 176+) duplicates the Firefox installation and IP verification steps already present in the second section (lines 158–167).
Consolidate these sections into a single, unified procedure with distinct headings for each step (configuration vs. verification) to eliminate confusion and improve clarity.
i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx (1)
15-48: Add periods to bullet points and correct em-dash formatting.Three Spanish punctuation issues confirmed:
- Line 17: Replace hyphen " - " with proper em-dash (—) or en-dash (–)
- Line 44: Add period after "pre-7.2"
- Line 45: Add period after "localmente"
These bullet points are complete sentences in Spanish and require terminal punctuation.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx (2)
254-281: Mixed English and German in recovery guidance.Lines 254–281 mix English guidance ("This ensures you're using a valid SSL certificate...") with German instructions. While this may be intentional for technical clarity, please ensure consistency—either translate the English paragraph to German or mark it as an exception. See line 229 for similar issue.
211-212: Character encoding issue confirmed: lines 211-212 contain corrupted UTF-8 sequences for German umlauts.Lines 211-212 contain malformed UTF-8 bytes (
\xef\xbf\xbd, the replacement character) where German umlauts should be: "für" is corrupted tof\xef\xbf\xbdfcr, "gültig" tog\xef\xbf\xbdfclt, and "übereinstimmt" is similarly affected. Other sections of the file (lines 12, 20, 24–25, 30) correctly encode umlauts as valid UTF-8. Fix by replacing the corrupted sequences with correct UTF-8-encoded German characters.i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (1)
46-57: Duplicate heading and provider sections confirmed — consolidate and remove duplicates.The duplicate heading "Wann sollte der einfache Modus verwendet werden" appears at lines 46 and 52 with different content under each. Additionally, provider configuration sections are duplicated:
- Authentik: lines 372 and 400
- Okta: lines 386 and 414
This indicates a merge or sync artifact. Consolidate these sections by keeping only one version of each, and merge or clarify the distinct content under the duplicate headings if both perspectives are intended.
i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (3)
46-56: Remove duplicated "Modo Simple" section headers and consolidate content.Section headers are repeated:
- Line 46:
**Cuándo usar el Modo Simple:**- Line 52:
**Cuándo usar el Modo Simple:**(duplicate)- Line 76:
## Ejemplos de Modo Simple- Line 81:
### Ejemplos de Modo Simple(near-duplicate with different level)Consolidate these sections to avoid reader confusion.
Also applies to: 81-94
216-252: Consolidate duplicated "Testing Your Configuration" section.The section "✅ Probando Tu Configuración" appears twice:
- Lines 216–243 (first instance with image and testing steps)
- Lines 233–243 (second instance, overlapping)
This creates confusion about the correct testing procedure. Merge these into a single, coherent section with one clear set of steps.
350-425: Remove duplicated provider sections (Okta, Authentik).Multiple provider sections are duplicated:
- Okta: Appears at lines 386–398 and again at lines 414–424
- Authentik: Appears at lines 372–384 and again at lines 400–412
Consolidate each provider into a single section to eliminate redundancy and maintain a clear document structure.
| | | **Empfohlen für die meisten** | | | ||
|
|
||
| ## Einrichten des dynamischen Fernzugriffs | ||
| ## Verwendung von UPnP (Universal Plug and Play) |
There was a problem hiding this comment.
Duplicate section heading breaks document structure.
Lines 70 and 90 both define "## Verwendung von UPnP (Universal Plug and Play)"—this creates malformed Markdown with two identically-named sections that will cause issues with heading anchors, navigation, and table-of-contents generation.
One of these section headers needs to be renamed or restructured. Based on the content flow, line 90's section likely should have a distinct heading that clarifies it covers configuration steps (e.g., "## UPnP konfigurieren" or "## UPnP-Konfigurationsschritte").
Also applies to: 90-90
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
around lines 70 and 90, there are duplicate "## Verwendung von UPnP (Universal
Plug and Play)" headings; rename the second/line-90 heading to a distinct,
contextual title (e.g., "## UPnP konfigurieren" or "##
UPnP‑Konfigurationsschritte") so section anchors and TOC are unique, and update
any nearby cross-references if present to match the new heading.
| <div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}> | ||
|  | ||
|  | ||
| </div> |
There was a problem hiding this comment.
Standardize image path references.
Most image references have been updated to use web paths (/img/zfs1.png), but lines 88 and 113 still use the old local asset path format (./assets/zfs8.png and ./assets/zfs9.png). Update these to match the standardized /img/ format for consistency.
- 
+ and
- 
+ Also applies to: 61-63, 74-76, 93-95, 100-102, 116-118, 146-148, 152-154, 165-167, 205-207, 233-235, 250-252, 288-290, 299-301
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
lines 41-43 and also the ranges 61-63, 74-76, 88, 93-95, 100-102, 113, 116-118,
146-148, 152-154, 165-167, 205-207, 233-235, 250-252, 288-290, 299-301: replace
any image src values using the local asset path pattern (./assets/...) with the
standardized web path /img/ (e.g. ./assets/zfs8.png → /img/zfs8.png) so all
image references use the consistent /img/ prefix; update every occurrence in the
listed lines and verify the filenames remain unchanged.
| --- | ||
|
|
||
| \* *„%%WireGuard|wireguard%%“ und das „%%WireGuard|wireguard%%“-Logo sind eingetragene Warenzeichen von Jason A. Donenfeld.* | ||
| \* *"%%WireGuard|wireguard%%" und das "%%WireGuard|wireguard%%" Logo sind eingetragene Marken von Jason A. Donenfeld.* |
There was a problem hiding this comment.
Use German quotation marks for consistency with German typography conventions.
Line 126 currently uses straight quotation marks (") around "WireGuard". German typography typically uses guillemets („") or («») for quotation marks. LanguageTool flagged this as a punctuation issue. Verify the documentation's preferred quotation mark style and update accordingly for consistency.
🧰 Tools
🪛 LanguageTool
[grammar] ~126-~126: Ersetze das Satzzeichen
Context: ...en wie Systemtemperaturen an. --- * *"%%WireGuard|wireguard%%" und das "%%WireGuard|wireguard%%" Logo ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~126-~126: Ersetze das Satzzeichen
Context: ... * *"%%WireGuard|wireguard%%" und das "%%WireGuard|wireguard%%" Logo sind eingetragene Marken von Jason ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
around line 126, replace the straight ASCII double quotes around the localized
token and the logo token with German opening and closing quotation marks; e.g.
change "%%WireGuard|wireguard%%" und das "%%WireGuard|wireguard%%" Logo to
„%%WireGuard|wireguard%%“ und das „%%WireGuard|wireguard%%“ Logo so both
occurrences use German-style quotes for typographic consistency.
| Wenn Sie das %%WebGUI|web-gui%% zum ersten Mal aufrufen, werden Sie aufgefordert, ein starkes Passwort für den %%root user|root-user%% zu erstellen. | ||
|
|
||
| Stellen Sie sicher, dass Ihr Passwort ist: | ||
| Wir empfehlen die Verwendung eines Passwort-Managers zur sicheren Speicherung. |
There was a problem hiding this comment.
Remove duplicate password manager recommendation.
The same text appears twice in consecutive paragraphs (lines 33 and 39): "Wir empfehlen die Verwendung eines Passwort-Managers zur sicheren Speicherung." Remove one occurrence to avoid redundancy.
-Wir empfehlen die Verwendung eines Passwort-Managers zur sicheren Speicherung.
-
- - Einzigartig
+ - EinzigartigAlso applies to: 39-39
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
around lines 33 and 39, there is a duplicated sentence "Wir empfehlen die
Verwendung eines Passwort-Managers zur sicheren Speicherung." Remove one of the
two occurrences (keep the first or the second, whichever preserves paragraph
flow) so the recommendation appears only once and ensure surrounding punctuation
and spacing remain correct after deletion.
| Wenn Sie Anruftraces im Zusammenhang mit macvlan (oder unerklärliche Abstürze generell) erhalten, empfehlen wir als ersten Schritt, zu ***Einstellungen > Docker*** zu navigieren, in die **Erweiterte** Ansicht zu wechseln und **Docker-Benutzerdefinierter Netzwerktype** von **macvlan** auf **ipvlan** zu ändern. Dies ist die Standardkonfiguration, mit der Unraid seit der Version 6.11.5 ausgeliefert wurde und sollte für die meisten Systeme funktionieren. | ||
| Wenn Sie Anruftraces im Zusammenhang mit macvlan (oder unerklärliche Abstürze generell) erhalten, empfehlen wir als ersten Schritt, zu _**Einstellungen > Docker**_ zu navigieren, in die **Erweiterte** Ansicht zu wechseln und **Docker-Benutzerdefinierter Netzwerktype** von **macvlan** auf **ipvlan** zu ändern. Dies ist die Standardkonfiguration, mit der Unraid seit der Version 6.11.5 ausgeliefert wurde und sollte für die meisten Systeme funktionieren. | ||
|
|
||
| Bitte beachten Sie, dass einige Benutzer Probleme mit der Portweiterleitung von bestimmten Routern (Fritzbox) und eingeschränkter Funktionalität mit erweiterten Netzwerkverwaltungstools (Ubiquity) im IPvlan-Modus gemeldet haben. Wenn Sie betroffen sind, sehen Sie sich die alternative Lösung an, die seit Unraid [6.12.4](6.12.4.md#fix-for-macvlan-call-traces) verfügbar ist. |
There was a problem hiding this comment.
Address grammar and capitalization issues flagged by static analysis.
Static analysis has identified several language issues that should be corrected:
- Line 22: Brand name "Fritzbox" should use proper capitalization: "Fritz!Box" or "FRITZ!Box" (depending on which generation is intended)
- Line 32: Grammar verb selection issue. Context suggests the sentence may need restructuring for proper German grammar
- Line 36: Remove unnecessary whitespace before "Plugin"
Apply these corrections to improve document quality and consistency with German language standards.
Also applies to: 32-32, 36-36
🧰 Tools
🪛 LanguageTool
[uncategorized] ~22-~22: Meinten Sie „Fritz!Box“ oder „FRITZ!Box“ (= Router)?
Context: ...rtweiterleitung von bestimmten Routern (Fritzbox) und eingeschränkter Funktionalität mit...
(FRITZ_BOX)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
lines 22,32,36: change the brand "Fritzbox" to the correct capitalization
"FRITZ!Box" (or "Fritz!Box" if you intentionally prefer that variant) on line
22; on line 32 fix the verb/grammar by rephrasing for correct German
subject-verb agreement (for example restructure the sentence so the verb matches
the subject or convert to a passive/infinitive construction as appropriate); on
line 36 remove the stray whitespace before "Plugin" so the word is directly
adjacent to the preceding text. Ensure punctuation and capitalization follow
German conventions after each change.
| Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches / hot fixes: | ||
|
|
||
| - Un subconjunto de actualizaciones de seguridad, vea [esta publicación de blog](https://unraid.net/blog/cvd) para más detalles. Recomendamos actualizar a la última versión estable para obtener actualizaciones de seguridad adicionales. |
There was a problem hiding this comment.
Remove extra whitespace before bullet point.
LanguageTool flags unnecessary spaces between line 11's closing colon and line 13's bullet point. There should be a single newline, not a double space.
Apply this fix:
- Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches / hot fixes:
+ Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches / hot fixes:
- Un subconjunto de actualizaciones de seguridad, vea [esta publicación de blog](https://unraid.net/blog/cvd) para más detalles. Recomendamos actualizar a la última versión estable para obtener actualizaciones de seguridad adicionales.Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 LanguageTool
[grammar] ~11-~11: Elimina el espacio
Context: ...d**_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actual...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~11-~11: Elimina el espacio
Context: ...*_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actualiz...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~13-~13: Cambia la palabra o signo.
Context: ... - Un subconjunto de actualizaciones de seguridad, vea [esta publicación de blog](https://...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION)
🤖 Prompt for AI Agents
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.5.md
lines 11-13: there is an extra blank line between the sentence ending with a
colon and the bullet list, creating an unintended blank line; remove the blank
line so the colon line is immediately followed by a single newline and then the
bullet point (i.e., collapse the two consecutive newlines into one).
| ## Parches | ||
|
|
||
| Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite ***Herramientas → Parche de Unraid*** para obtener los siguientes parches / hot fixes: | ||
| Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches / hot fixes: |
There was a problem hiding this comment.
Address extra whitespace flagged by grammar check.
Line 62 has extra spacing flagged by LanguageTool. The context shows hot fixes: - with possible double spaces or trailing whitespace before the bullet list on line 64. Remove the extra space to maintain consistent markdown formatting.
-Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches / hot fixes:
+Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches / hot fixes:Note: Ensure there are no trailing spaces at the end of this line before the list items below.
Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 LanguageTool
[grammar] ~62-~62: Elimina el espacio
Context: ...d**_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actual...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~62-~62: Elimina el espacio
Context: ...*_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actualiz...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
around line 62, there is extra whitespace before the upcoming bullet list ("hot
fixes: -") flagged by the grammar checker; remove the extra space(s) and any
trailing spaces at the end of line 62 so the colon is followed directly by a
single newline and the list items start immediately on the next line with the
bullet indent preserved.
| #### Problemas debido a tarjetas de red Realtek | ||
|
|
||
| Los controladores Realtek incluidos en los últimos núcleos de Linux están causando problemas de red y estabilidad. Si tienes problemas y ***Herramientas > Dispositivos del sistema*** muestra que tienes un controlador ethernet Realtek, obtén el número de parte mostrado y busca en Community Apps para ver si hay un plugin de controlador Realtek para ese dispositivo. Para más información, consulta la [página de soporte para plugins de controladores Realtek](https://forums.unraid.net/topic/141349-plugin-realtek-r8125-r8168-and-r81526-drivers/). | ||
| Los controladores Realtek incluidos en los últimos núcleos de Linux están causando problemas de red y estabilidad. Si tienes problemas y _**Herramientas > Dispositivos del sistema**_ muestra que tienes un controlador ethernet Realtek, obtén el número de parte mostrado y busca en Community Apps para ver si hay un plugin de controlador Realtek para ese dispositivo. Para más información, consulta la [página de soporte para plugins de controladores Realtek](https://forums.unraid.net/topic/141349-plugin-realtek-r8125-r8168-and-r81526-drivers/). |
There was a problem hiding this comment.
Fix capitalization error flagged by grammar analysis.
Line 25 contains a lowercase orthography issue after "Realtek, obtén". Review and correct the capitalization per Spanish grammar rules.
The LanguageTool grammar checker flags this as requiring lowercase correction. Verify the appropriate capitalization for this phrase in standard Spanish usage.
🧰 Tools
🪛 LanguageTool
[grammar] ~25-~25: Corrige la minúscula.
Context: ...ma**_ muestra que tienes un controlador ethernet Realtek, obtén el número de parte mostr...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_LOWERCASE)
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
around line 25, fix the capitalization flagged after "Realtek, obtén" by
ensuring the word following the comma is in lowercase per Spanish orthography;
update the text so the verb is lowercase (keeping the accent) unless it is
intentionally a sentence start or proper noun.
| ## Parches | ||
|
|
||
| Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite ***Herramientas → Parche de Unraid*** para obtener los siguientes parches / hot fixes: | ||
| Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches / hot fixes: |
There was a problem hiding this comment.
Remove unnecessary spaces around forward slash.
Line 63 contains unnecessary spaces around the "/" in "parches / hot fixes". Adjust spacing to either "parches/hotfixes" (combined) or "parches/hot fixes" (no spaces around slash) for consistency with Spanish orthographic conventions.
LanguageTool flags two instances of unnecessary spacing on this line. The current formatting "parches / hot fixes:" deviates from standard Spanish style.
🧰 Tools
🪛 LanguageTool
[grammar] ~63-~63: Elimina el espacio
Context: ...d**_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actual...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~63-~63: Elimina el espacio
Context: ...*_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actualiz...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
around line 63, the phrase "parches / hot fixes" has unnecessary spaces around
the forward slash; remove the spaces so it reads either "parches/hotfixes"
(combined) or "parches/hot fixes" (no spaces around the slash) for consistent
Spanish formatting, and ensure the trailing colon remains.
| ## Parches | ||
|
|
||
| Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite ***Herramientas → Parche de Unraid*** para obtener los siguientes parches / hot fixes: | ||
| Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches / hot fixes: |
There was a problem hiding this comment.
Remove extra spaces around the slash separator.
Line 76 has unnecessary spaces around the forward slash in "parches / hot fixes". Per the LanguageTool grammar check, this should be either "parches/hot fixes" (no spaces) or "parches o hot fixes" (using "o" as conjunction in Spanish).
- Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches / hot fixes:
+ Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches/hot fixes:📝 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.
| Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches / hot fixes: | |
| Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches/hot fixes: |
🧰 Tools
🪛 LanguageTool
[grammar] ~76-~76: Elimina el espacio
Context: ...d**_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actual...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~76-~76: Elimina el espacio
Context: ...*_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actualiz...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
around line 76, remove the extra spaces surrounding the forward slash in
"parches / hot fixes"; replace with "parches/hot fixes" (no spaces) or
optionally change to "parches o hot fixes" if you prefer the conjunction —
update the sentence accordingly so spacing and punctuation follow Spanish style.
| Das Flash-Backup wurde entwickelt, um essentielle Konfigurationsdateien zu speichern und keine vollständige Kopie Ihres Flash-Laufwerks. Es sichert keine temporären Dateien (wie Protokolle) oder Anwendungs-Binaries. Plugin-Konfigurationen sind enthalten, aber Anwendungsdateien müssen beim Start neu heruntergeladen werden. Einzelne Dateien bis zu 10 MB werden gesichert; wenn das Gesamtbackup 100 MB überschreitet, wird es gelöscht und neu erstellt. | ||
|
|
||
| :::important | ||
| Backups schließen keine `config/shadow`- oder `config/smbpasswd`-Dateien ein. Benutzerkonten bleiben erhalten, aber Passwörter nicht. Sie müssen alle Benutzerpasswörter, einschließlich des Root-Passworts, nach der Wiederherstellung zurücksetzen. %%WireGuard|wireguard%%-Schlüssel sind ebenfalls ausgeschlossen. | ||
|
|
||
| So stellen Sie Ihre Konfiguration wieder her: | ||
|
|
||
| ::: | ||
|
|
||
| Das Flash-Backup wurde entwickelt, um essentielle Konfigurationsdateien zu speichern und keine vollständige Kopie Ihres Flash-Laufwerks. Es sichert keine temporären Dateien (wie Protokolle) oder Anwendungs-Binaries. Plugin-Konfigurationen sind enthalten, aber Anwendungsdateien müssen beim Start neu heruntergeladen werden. Einzelne Dateien bis zu 10 MB werden gesichert; wenn das Gesamtbackup 100 MB überschreitet, wird es gelöscht und neu erstellt. |
There was a problem hiding this comment.
Remove duplicate flash-backup scope content.
Lines 62 and 70 contain identical text describing the scope of flash backups. This duplication should be removed to maintain clarity and conciseness in the documentation.
- Das Flash-Backup wurde entwickelt, um essentielle Konfigurationsdateien zu speichern und keine vollständige Kopie Ihres Flash-Laufwerks. Es sichert keine temporären Dateien (wie Protokolle) oder Anwendungs-Binaries. Plugin-Konfigurationen sind enthalten, aber Anwendungsdateien müssen beim Start neu heruntergeladen werden. Einzelne Dateien bis zu 10 MB werden gesichert; wenn das Gesamtbackup 100 MB überschreitet, wird es gelöscht und neu erstellt.
-
- :::important
-
- So stellen Sie Ihre Konfiguration wieder her:
-
- :::
-
- Das Flash-Backup wurde entwickelt, um essentielle Konfigurationsdateien zu speichern und keine vollständige Kopie Ihres Flash-Laufwerks. Es sichert keine temporären Dateien (wie Protokolle) oder Anwendungs-Binaries. Plugin-Konfigurationen sind enthalten, aber Anwendungsdateien müssen beim Start neu heruntergeladen werden. Einzelne Dateien bis zu 10 MB werden gesichert; wenn das Gesamtbackup 100 MB überschreitet, wird es gelöscht und neu erstellt.
+
+ :::important
+
+ So stellen Sie Ihre Konfiguration wieder her:
+
+ :::Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 LanguageTool
[style] ~62-~62: Möchten Sie die modernere Schreibweise „essenzielle“ verwenden?
Context: ... Das Flash-Backup wurde entwickelt, um essentielle Konfigurationsdateien zu speichern und ...
(Z_ANSTATT_T)
[style] ~70-~70: Möchten Sie die modernere Schreibweise „essenzielle“ verwenden?
Context: ... Das Flash-Backup wurde entwickelt, um essentielle Konfigurationsdateien zu speichern und ...
(Z_ANSTATT_T)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
lines 62–70 contain a duplicated paragraph repeating the flash-backup scope;
remove the duplicated block (the second occurrence after the :::important
callout) so the scope text appears only once, preserving the important callout
structure and surrounding whitespace/markup.
|
|
||
| So stellen Sie Ihre Konfiguration wieder her: | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Orphaned important block contains only a heading.
The :::important block (lines 65–68) contains just a heading with no actual important content or instructions. Either add substantive content to this block or restructure it as a regular section header.
Consider replacing this with a regular section header:
- :::important
-
- So stellen Sie Ihre Konfiguration wieder her:
-
- :::
+ ## So stellen Sie Ihre Konfiguration wieder her📝 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.
| So stellen Sie Ihre Konfiguration wieder her: | |
| ::: | |
| ## So stellen Sie Ihre Konfiguration wieder her |
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
around lines 65–68, the :::important block contains only a heading and no
content; either add the missing important content (a short explanatory paragraph
or steps to restore configuration) inside the :::important container, or convert
the block into a normal section header by removing the :::important markers and
leaving the heading as a regular markdown/MDX heading so it no longer appears as
an empty important callout.
| 1. Klicken Sie in **Einstellungen → Management-Zugriff → Unraid API** auf **Deaktivieren** für Flash-Backup. | ||
| 2. Aktivieren Sie im Bestätigungsdialog **Auch Cloud-Backup löschen**, wenn Sie Ihr Backup sofort entfernen möchten. Andernfalls werden Backups nach einer gewissen Inaktivität automatisch gelöscht. |
There was a problem hiding this comment.
🧩 Analysis chain
Misplaced deactivation instructions in encryption section.
Lines 96–97 contain instructions for deactivating flash backup. This content belongs in a separate "Deactivate Flash Backup" or "Flash-Backup deaktivieren" section, not within the "Backups-Verschlüsselung" section where it currently appears.
Verify the intended section structure and move these instructions to the appropriate location in the document.
🏁 Script executed:
#!/bin/bash
# Read the document with line numbers to verify section structure and locate lines 96-97
cat -n "i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx" | head -120 | tail -40Length of output: 2571
🏁 Script executed:
#!/bin/bash
# Get the full document structure with line numbers to understand section headings
cat -n "i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx" | grep -E "^[[:space:]]*[0-9]+[[:space:]]+#{1,6}\s"Length of output: 346
🏁 Script executed:
#!/bin/bash
# Show a larger context around lines 96-97 (lines 70-110)
cat -n "i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx" | sed -n '70,110p'Length of output: 3133
🏁 Script executed:
#!/bin/bash
# Count total lines in file
wc -l "i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx"Length of output: 92
🏁 Script executed:
#!/bin/bash
# Search for "Backups-Verschlüsselung" and "deaktivieren" or "Deactivate" sections
grep -n -i "Backups-Verschlüsselung\|deaktivieren\|deactivate" "i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx"Length of output: 547
🏁 Script executed:
#!/bin/bash
# Show entire document to get complete picture
cat "i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx"Length of output: 7632
Move deactivation instructions (lines 96–97) to a dedicated section outside "Backups-Verschlüsselung."
Lines 96–97 contain operational steps for deactivating flash backup. They are currently placed within the "Backups-Verschlüsselung" (encryption) section (line 92) but describe an unrelated procedure. Encryption configuration and deactivation are separate concerns. Create a dedicated "## Flash-Backup deaktivieren" section and relocate these instructions there to match the document's established pattern: Enable → Restore → Deactivate → Security/Privacy Information.
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
around lines 96–97, the two-step deactivation instructions are incorrectly
placed inside the "Backups-Verschlüsselung" section; extract those lines and
create a new top-level subsection titled "## Flash-Backup deaktivieren"
(following the document pattern Enable → Restore → Deactivate →
Security/Privacy), move the two bullet steps into that new section, and ensure
surrounding headings/anchors and spacing are adjusted so the encryption section
no longer contains deactivation steps.
| :::tip | ||
| Überprüfen Sie vor dem Abschluss die Abschnitte über Zuordnungsprofile und Topologie, um eine fundierte Entscheidung zu treffen. | ||
|
|
||
| To add a %%ZFS|zfs%% disk to the %%array|array%%: | ||
|
|
||
| ::: | ||
|
|
||
| <div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}> | ||
|  | ||
|  | ||
| </div> |
There was a problem hiding this comment.
Complete the tip block content.
Lines 106-110 show an incomplete tip block: the header "To add a %%ZFS|zfs%% disk to the %%array|array%%" appears but there's no explanatory content before the next image. Either provide the intended explanation or reconsider the tip structure.
Verify the tip block intent and add descriptive content if needed:
:::tip
To add a %%ZFS|zfs%% disk to the %%array|array%%:
+ [Add explanation or procedural steps here]
+
:::📝 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.
| :::tip | |
| Überprüfen Sie vor dem Abschluss die Abschnitte über Zuordnungsprofile und Topologie, um eine fundierte Entscheidung zu treffen. | |
| To add a %%ZFS|zfs%% disk to the %%array|array%%: | |
| ::: | |
| <div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}> | |
|  | |
|  | |
| </div> | |
| :::tip | |
| To add a %%ZFS|zfs%% disk to the %%array|array%%: | |
| [Add explanation or procedural steps here] | |
| ::: | |
| <div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}> | |
|  | |
| </div> |
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
around lines 106 to 114, the tip block header "To add a %%ZFS|zfs%% disk to the
%%array|array%%" is left empty before the image; add a short explanatory
sentence or two inside the tip describing the required steps (e.g., select the
disk, set it as ZFS in Unraid, assign to the array, and any prerequisites like
formatting or backup) so the tip is complete and self-contained, or remove the
tip wrapper if no extra text is needed. Ensure the text is in German to match
the file locale and keep it concise.
| :::tip[Optimizing Festplattenanzahlen | ||
|
|
||
| Dies bietet zwei wesentliche Vorteile: | ||
|
|
||
| **Beispiele für optimierte Konfigurationen:** | ||
|
|
||
| - **RAIDZ1**: 3, 5 oder 9 Festplatten (Datenträger = 2, 4 oder 8) | ||
| - **RAIDZ2**: 4, 6 oder 10 Festplatten (Datenträger = 2, 4 oder 8) | ||
| - **RAIDZ3**: 5, 9 oder 17 Festplatten (Datenträger = 2, 6 oder 14) | ||
|
|
||
| Beachten Sie, dass diese Optimierungen optional sind - die oben genannten Empfehlungen sollten für die meisten Anwendungsfälle gut funktionieren. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Fix unpaired bracket in tip block.
The tip block opening on line 177 has a syntax error: :::tip[Optimizing Festplattenanzahlen is missing the closing bracket. This will break MDX rendering.
- :::tip[Optimizing Festplattenanzahlen
+ :::tip[Optimizing Festplattenanzahlen]📝 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.
| :::tip[Optimizing Festplattenanzahlen | |
| Dies bietet zwei wesentliche Vorteile: | |
| **Beispiele für optimierte Konfigurationen:** | |
| - **RAIDZ1**: 3, 5 oder 9 Festplatten (Datenträger = 2, 4 oder 8) | |
| - **RAIDZ2**: 4, 6 oder 10 Festplatten (Datenträger = 2, 4 oder 8) | |
| - **RAIDZ3**: 5, 9 oder 17 Festplatten (Datenträger = 2, 6 oder 14) | |
| Beachten Sie, dass diese Optimierungen optional sind - die oben genannten Empfehlungen sollten für die meisten Anwendungsfälle gut funktionieren. | |
| ::: | |
| :::tip[Optimizing Festplattenanzahlen] | |
| Dies bietet zwei wesentliche Vorteile: | |
| **Beispiele für optimierte Konfigurationen:** | |
| - **RAIDZ1**: 3, 5 oder 9 Festplatten (Datenträger = 2, 4 oder 8) | |
| - **RAIDZ2**: 4, 6 oder 10 Festplatten (Datenträger = 2, 4 oder 8) | |
| - **RAIDZ3**: 5, 9 oder 17 Festplatten (Datenträger = 2, 6 oder 14) | |
| Beachten Sie, dass diese Optimierungen optional sind - die oben genannten Empfehlungen sollten für die meisten Anwendungsfälle gut funktionieren. | |
| ::: |
🧰 Tools
🪛 LanguageTool
[typographical] ~177-~177: Zeichen ohne sein Gegenstück: ‚]‘ scheint zu fehlen
Context: ...n (max. 20) | :::tip[Optimizing Festplattenanzahlen Dies bie...
(UNPAIRED_BRACKETS)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
around lines 177 to 189, the tip block opener is missing the closing bracket;
fix by adding the closing bracket to the opener so it reads :::tip[Optimizing
Festplattenanzahlen] (keep the rest of the tip content unchanged) to restore
valid MDX tip block syntax.
|
|
||
| ::: | ||
|
|
||
| :::important[How elegir] |
There was a problem hiding this comment.
Fix mixed language in section header.
Same as line 129: section header mixes English (How) with Spanish (elegir). Should be entirely in Spanish for consistency.
-:::important[How elegir]
+:::important[Cómo elegir]📝 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.
| :::important[How elegir] | |
| :::important[Cómo elegir] |
🧰 Tools
🪛 LanguageTool
[grammar] ~191-~191: Cambia la palabra o signo.
Context: ...os casos de uso. ::: :::important[How elegir] - Use Espejo si quiere el mejor r...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
around line 191, the section header mixes English and Spanish ("How elegir");
replace it with a fully Spanish header such as "Cómo elegir" and update the
admonition markup accordingly (e.g., :::important[Cómo elegir]) to maintain
language consistency and correct accenting.
|
|
||
| :::caution | ||
|
|
||
| La mayoría de los usuarios de Unraid deberían evitar los vdevs de soporte / subpools a menos que tengan una necesidad específica y bien entendida. Están diseñados para cargas de trabajo especializadas y pueden introducir complejidad o riesgo si se usan incorrectamente. |
There was a problem hiding this comment.
Remove unnecessary spaces around forward slash.
Spanish typography: remove spaces around the "/" character in "soporte / subpools".
-La mayoría de los usuarios de Unraid deberían evitar los vdevs de soporte / subpools
+La mayoría de los usuarios de Unraid deberían evitar los vdevs de soporte/subpools📝 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.
| La mayoría de los usuarios de Unraid deberían evitar los vdevs de soporte / subpools a menos que tengan una necesidad específica y bien entendida. Están diseñados para cargas de trabajo especializadas y pueden introducir complejidad o riesgo si se usan incorrectamente. | |
| La mayoría de los usuarios de Unraid deberían evitar los vdevs de soporte/subpools a menos que tengan una necesidad específica y bien entendida. Están diseñados para cargas de trabajo especializadas y pueden introducir complejidad o riesgo si se usan incorrectamente. |
🧰 Tools
🪛 LanguageTool
[grammar] ~313-~313: Elimina el espacio
Context: ...aid deberían evitar los vdevs de soporte / subpools a menos que tengan una necesi...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~313-~313: Elimina el espacio
Context: ...d deberían evitar los vdevs de soporte / subpools a menos que tengan una necesida...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
around line 313, the phrase "soporte / subpools" contains unwanted spaces around
the forward slash; remove the spaces so it reads "soporte/subpools" to match
Spanish typography conventions.
|
|
||
| - **[Vista del Panel de Control](./tour-the-web-gui.mdx#1-dashboard)** - El panel proporciona una vista detallada y en tiempo real de su sistema, mostrando indicadores de salud del disco, temperaturas, uso de recursos y estados de aplicación. | ||
| - **[Operación del Array](./tour-the-web-gui.mdx#2-main)** - Administra tu %%array|array%% sin esfuerzo. \*\*\[Puedes asignar dispositivos para usar en el %%array|array%% o en el %%cache|cache%%, activar y desactivar individualmente los discos, iniciar y detener el %%array|array%%, e incluso realizar %%parity checks|parity-check%% al vuelo, todo desde una sola página. | ||
| - **[Operación del Array](./tour-the-web-gui.mdx#2-main)** - Administra tu %%array|array%% sin esfuerzo. \*\*[Puedes asignar dispositivos para usar en el %%array|array%% o en el %%cache|cache%%, activar y desactivar individualmente los discos, iniciar y detener el %%array|array%%, e incluso realizar %%parity checks|parity-check%% al vuelo, todo desde una sola página. |
There was a problem hiding this comment.
🧩 Analysis chain
Fix markdown formatting regression in the "Operación del Array" bullet point.
Line 13 uses escaped asterisks (\*\*) instead of standard markdown bold syntax (**), which will render as literal ** characters rather than applying bold formatting. This is inconsistent with lines 12 and 14–21, which use correct bold syntax.
Replace the escaped asterisks with standard markdown:
- **[Operación del Array](./tour-the-web-gui.mdx#2-main)** - Administra tu %%array|array%% sin esfuerzo. \*\*[Puedes asignar dispositivos para usar en el %%array|array%% o en el %%cache|cache%%, activar y desactivar individualmente los discos, iniciar y detener el %%array|array%%, e incluso realizar %%parity checks|parity-check%% al vuelo, todo desde una sola página.
+ **[Operación del Array](./tour-the-web-gui.mdx#2-main)** - Administra tu %%array|array%% sin esfuerzo. **[Puedes asignar dispositivos para usar en el %%array|array%% o en el %%cache|cache%%, activar y desactivar individualmente los discos, iniciar y detener el %%array|array%%, e incluso realizar %%parity checks|parity-check%% al vuelo, todo desde una sola página.**Additionally, a static analysis tool flagged a potential grammar issue on this line. Please review the Spanish text for correctness.
🏁 Script executed:
#!/bin/bash
# Inspect the Spanish localization file to verify markdown formatting on line 13
FILE_PATH="i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/key-features.mdx"
# Check if file exists and display context around line 13
if [ -f "$FILE_PATH" ]; then
echo "=== File found. Displaying lines 10-22 ==="
sed -n '10,22p' "$FILE_PATH" | cat -n
echo ""
echo "=== Raw line 13 for detailed inspection ==="
sed -n '13p' "$FILE_PATH" | od -c | head -20
else
echo "File not found at: $FILE_PATH"
find . -name "key-features.mdx" -type f 2>/dev/null | head -5
fiLength of output: 3053
Fix markdown formatting regression in the "Operación del Array" bullet point.
The verification confirms the escaped asterisks issue on line 13. The file contains \*\*[Puedes asignar... which will render as literal ** text instead of bold formatting. This is inconsistent with the standard markdown bold syntax (**...**) used in all other bullet points on lines 12 and 14–21.
Replace the escaped asterisks with standard markdown:
- **[Operación del Array](./tour-the-web-gui.mdx#2-main)** - Administra tu %%array|array%% sin esfuerzo. \*\*[Puedes asignar dispositivos para usar en el %%array|array%% o en el %%cache|cache%%, activar y desactivar individualmente los discos, iniciar y detener el %%array|array%%, e incluso realizar %%parity checks|parity-check%% al vuelo, todo desde una sola página.
+ **[Operación del Array](./tour-the-web-gui.mdx#2-main)** - Administra tu %%array|array%% sin esfuerzo. **[Puedes asignar dispositivos para usar en el %%array|array%% o en el %%cache|cache%%, activar y desactivar individualmente los discos, iniciar y detener el %%array|array%%, e incluso realizar %%parity checks|parity-check%% al vuelo, todo desde una sola página.**Additionally, verify the Spanish grammar on this line per static analysis flagging.
📝 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.
| - **[Operación del Array](./tour-the-web-gui.mdx#2-main)** - Administra tu %%array|array%% sin esfuerzo. \*\*[Puedes asignar dispositivos para usar en el %%array|array%% o en el %%cache|cache%%, activar y desactivar individualmente los discos, iniciar y detener el %%array|array%%, e incluso realizar %%parity checks|parity-check%% al vuelo, todo desde una sola página. | |
| - **[Operación del Array](./tour-the-web-gui.mdx#2-main)** - Administra tu %%array|array%% sin esfuerzo. **[Puedes asignar dispositivos para usar en el %%array|array%% o en el %%cache|cache%%, activar y desactivar individualmente los discos, iniciar y detener el %%array|array%%, e incluso realizar %%parity checks|parity-check%% al vuelo, todo desde una sola página.** |
🧰 Tools
🪛 LanguageTool
[grammar] ~13-~13: Agrega una palabra o signo.
Context: ... recursos y estados de aplicación. - **[Operación del Array](./tour-the-web-gui.mdx#2-mai...
(QB_NEW_ES_OTHER_ERROR_IDS_MISSING_OTHER)
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/key-features.mdx
around line 13, the bold markdown in the "Operación del Array" bullet contains
escaped asterisks (`\*\*`) causing literal `**` to render; remove the
backslashes so the text uses standard markdown bold (`**...**`) and ensure the
opening and closing `**` wrap the phrase "Puedes asignar dispositivos..."
correctly; while editing, correct Spanish grammar/typos if present (e.g.,
punctuation and agreement) so the sentence reads naturally and matches style
used in surrounding bullets.
| ## Parches | ||
|
|
||
| Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite ***Herramientas → Parche de Unraid*** para obtener los siguientes parches / hot fixes: | ||
| Con el [plugin de Parches para Unraid](https://forums.unraid.net/topic/185560-unraid-patch-plugin/) instalado, visite _**Herramientas → Parche de Unraid**_ para obtener los siguientes parches / hot fixes: |
There was a problem hiding this comment.
Remove unnecessary spacing after inline formatting emphasis.
The LanguageTool warnings indicate extra spaces around the emphasis markers: _**Herramientas → Parche de Unraid**_ (note spaces before/after). This appears consistent with similar issues flagged in other Spanish release notes in this PR (e.g., 6.12.4.md line 145).
Apply minimal spacing cleanup to align with markdown best practices.
🧰 Tools
🪛 LanguageTool
[grammar] ~59-~59: Elimina el espacio
Context: ...d**_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actual...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~59-~59: Elimina el espacio
Context: ...*_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actualiz...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
🤖 Prompt for AI Agents
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
around line 59: the inline emphasis `_**Herramientas → Parche de Unraid**_` has
extra space(s) adjacent to the emphasis markers; remove any spaces immediately
inside or immediately after the emphasis markers so the phrase reads exactly ...
visite _**Herramientas → Parche de Unraid**_ para ... with no extra space before
the opening underscore, between markers and text, or after the closing
underscore.
| Antes de revertir a una versión anterior, es importante asegurarse de que el Puenteo esté habilitado: | ||
|
|
||
| - ***Configuración > Configuración de Red > eth0 > Habilitar Puenteo*** = Sí | ||
| - _**Configuración > Configuración de Red > eth0 > Habilitar Puenteo**_ = Sí |
There was a problem hiding this comment.
Formatting approved with spacing issue noted.
Navigation and settings path formatting is consistent throughout. However, the same spacing issue flagged in 6.12.3.md appears here on line 145: extra spaces after the inline formatting emphasis around "parches / hot fixes". Consider normalizing spacing around all similar inline emphasis elements across the Spanish release notes for consistency.
Also applies to: 19-20, 30-30, 36-38, 42-42, 65-65, 73-73, 145-145
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
around lines 13 and also at lines 19-20, 30, 36-38, 42, 65, 73 and 145, several
inline emphasis elements have extra spaces inside or around the emphasis (e.g.
"_**...**_ = Sí" and "parches / hot fixes" spacing); remove the extraneous
spaces so emphasis markers directly wrap the text (e.g. "_**Configuración >
Configuración de Red > eth0 > Habilitar Puenteo**_ = Sí" and normalize spacing
around "parches/hot fixes" or similar phrases) to match the formatting used
elsewhere in the release notes.
Summary by CodeRabbit