New Crowdin updates #374
New Crowdin updates #374
Conversation
📝 WalkthroughWalkthroughLarge multilingual documentation update: adds many German and Spanish MDX pages, extensive content expansions and formatting normalizations, restructures several guides (storage, troubleshooting, system administration), and adds Docusaurus i18n entries. No code or API signatures were changed. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant Admin as Admin
participant GUI as WebGUI
participant Host as Unraid Host
participant VM as Guest VM
participant GA as Guest Agent
Note over Admin,GUI: Documented recommended VM shutdown/hibernation flow
Admin->>GUI: Click "Shut down"
GUI->>Host: initiate orderly shutdown sequence
Host->>VM: request graceful shutdown/hibernate
VM->>GA: guest-agent perform hibernate
GA-->>VM: confirm hibernation
VM-->>Host: guest halted
Host->>Host: stop services, flush disk I/O
Host-->>GUI: shutdown complete
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45–60 minutes
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
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: 85
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (25)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (2)
395-431: Duplicate "## Fehlerbehebung" heading and misplaced content.The section starting at line 395 appears to be out of scope—it discusses unassigned devices plugins rather than file system troubleshooting, and the same heading reappears at line 431. The content at lines 397–430 (about unassigned drives and plugins) should either be relocated to a separate section or removed, as the actual file system troubleshooting guidance begins at line 433. This creates structural confusion and breaks the logical flow.
Suggest reorganizing:
- Remove or relocate the "Unassigned drives" section (lines 397–430)
- Consolidate to a single "## Fehlerbehebung" heading
- Ensure troubleshooting content is grouped logically
242-242: Fix typo in section heading."Neusformatiert eines Laufwerks" appears to be a grammatical error. Consider revising to "Neuformatierung eines Laufwerks" or "Ein Laufwerk neuformatieren" for clarity and correctness.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdx (1)
20-26: Remove duplicate introductory text and clarify section flow.Lines 22 and 26 contain identical text: "Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen:". The introductory sentence appears twice, with line 24 (about viewing SMART data in the Main tab) inserted between them. This breaks the logical flow between the introduction and the attribute table.
The section should flow: introduction → explanation (optional) → table. Clarify whether line 24 belongs here or should be moved/removed, and remove the duplicate introduction.
## Wie Unraid SMART nutzt -Einige %%SMART|smart%% Attribute, die Unraid standardmäßig überwacht, umfassen: +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** | ...i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx (1)
145-167: Extensive untranslated English content in German localization—critical issue.The verification confirms multiple untranslated English sections scattered throughout the file that break continuity for German-speaking readers:
- Line 145: "Never assign a data disk as a %%parity drive|parity-drives%%. Incorrect assignments can overwrite data with parity information, resulting in permanent data loss."
- Line 151–152: "%%Parity drives|parity-drives%% do not have a mountable file system..." and "Data drives previously used by Unraid..."
- Line 163: "Do not click Format on any drive..."
- Line 166: "Go to Tools → New Config..."
- Line 168: "If you have a single %%parity|parity%% drive, the order of data drives is not critical..."
All must be translated to German. This is an automated Crowdin update; ensure the source English content has complete German translations before the next sync.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/managing-and-customizing-containers.mdx (1)
166-180: Misplaced User Scripts instruction within volume-mapping examples.Lines 172-174 ("Greifen Sie über Einstellungen → Benutzerskripte...") disrupt the flow of volume-mapping path examples. This content belongs in the "Benutzerskripte-Plugin" subsection (line 194+), not interspersed between the media server and multiple-shares examples.
Move lines 172-174 to the "Benutzerskripte-Plugin" subsection where User Scripts instructions are properly grouped.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx (1)
96-114: Critical: Duplicate sections with conflicting content depth.Lines 96–114 duplicate the WebGUI (lines 73–84) and Array (lines 87–93) startup steps. The duplicates are shorter and omit details from the first occurrence (e.g., the detailed list in the first WebGUI block at lines 77–83 is not present in the duplicate at lines 100–101).
Clarify whether both sets are needed or if one should be removed to avoid reader confusion.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/xfs-check-cli.mdx (1)
16-16: Critical: Untranslated English text in German documentation.Line 16 contains English text: "Both %%WebGUI|web-gui%% and command-line options are supported for %%XFS|xfs%% repair (commands shown below)."
This should be translated to German for consistency with the rest of the file.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/docker-troubleshooting.mdx (2)
20-20: Critical: Untranslated English paragraph in German documentation.Line 20 begins an English paragraph: "A corrupted Docker image file (
docker.img) is a common issue, often caused by the %%cache pool|cache-pool%% running out of space or an unclean shutdown..."This entire section requires German translation for consistency with the file language.
42-42: Critical: Untranslated English paragraph in German documentation.Line 42 begins an English paragraph: "Below are the main ways to access your Unraid %%WebGUI|web-gui%%, depending on your %%SSL|ssl%% configuration:"
This section should be translated to German or removed if this content is meant for another language version.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx (2)
46-46: Critical: Untranslated English section introduction.Line 46: "Below are the main ways to access your Unraid %%WebGUI|web-gui%%, depending on your %%SSL|ssl%% configuration:" requires German translation.
186-188: Critical: Untranslated English section on custom certificates.Lines 186-188 contain English paragraphs defining custom certificates. This requires German translation for the file to be complete.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx (1)
256-256: Critical: Untranslated English paragraph.Line 256 contains English text: "You should disable %%SSL|ssl%% for local access if you prefer a simple HTTP connection..."
This requires German translation.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx (1)
68-84: Duplicate content: "Best Practice" and "Anmeldeangaben-Beschränkung" repeated.Lines 68–71 and lines 82–84 contain identical guidance:
- "Best Practice: Richten Sie Benutzerkonten und Passwörter für Ihre Unraid-Freigaben ein..."
- "Anmeldeangaben-Beschränkung: Windows erlaubt gleichzeitig nur einen Satz..."
This content recurs within the Windows SMB access caution block (lines 78–90). While repetition can aid emphasis, consider consolidating to avoid redundancy. If emphasis is intentional for users skimming the Windows SMB section, add a brief note referencing the earlier guidance.
i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx (2)
50-54: Resolve duplicate section headings.There are two sections titled "Benutzeroberflächenverbesserungen" at different heading levels:
- Line 50:
### Benutzeroberflächenverbesserungen(subsection under Security & Authentication)- Line 54:
## Benutzeroberflächenverbesserungen(main section)This creates confusing hierarchy. The subsection at line 50 should either have a different title or the main section should be renamed. Same issue exists with "Plugin-System" at lines 104 and 109.
104-109: Resolve duplicate "Plugin-System" headings.Lines 104 and 109 both define "Plugin-System" sections at different heading levels, creating duplicate section titles. Rename one to clarify the distinction between the subsection and main section.
i18n/de/docusaurus-plugin-content-docs/current/API/index.mdx (1)
61-61: Fix broken link href on line 61.The href
./oIDC-Anbieter-Einrichtungdoes not match the actual file. The correct file isoidc-provider-setup.mdx, so the href should be./oidc-provider-setup.Change line 61 from:
<Card title="OIDC-Einrichtung" icon="Schild" href="./oIDC-Anbieter-Einrichtung">To:
<Card title="OIDC-Einrichtung" icon="Schild" href="./oidc-provider-setup">i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx (1)
58-121: Consolidate duplicate troubleshooting sections.The troubleshooting section contains three duplicate entries:
- Lines 69–76 and 100–108: "VMs zeigen 'Kann Schnittstellen-MTU nicht abrufen' oder Netzwerkfehler"
- Lines 80–87 and 112–115: "VNC-Zugriff auf VMs funktioniert nicht oder ist langsam"
- Lines 90–97 and 118–121: "VM wird nicht booten (EFI-Shell erscheint)"
Remove the second occurrence of each to maintain clarity and reduce maintenance overhead.
i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (1)
92-103: Consolidate duplicate section headings and content.Lines 92 and 101 both define encryption-related sections ("Backups-Verschlüsselung" at h2 and h3 levels), and lines 94–95 duplicate lines 103–104 nearly verbatim. Consolidate into a single, clear hierarchy.
- ## 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. - - 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. - - ## Datenschutz und Sicherheit - - ### Backups-Verschlüsselungi18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)
138-164: Remove duplicate "## Lizenzverwaltung" heading at line 168; relocate customization tabs to "## Anpassung" section.The file contains a critical structural error:
- Line 148–166: First "## Lizenzverwaltung" heading with customization tabs (banner, rearrange, themes)—but this content belongs under "Anpassung" (Customization), not license management.
- Line 168–180: Duplicate "## Lizenzverwaltung" heading with actual license management content (keys, upgrade, backup).
- Line 138–147: "## Anpassung" section currently only covers Deep Linking; customization tabs should be here.
Merge the customization tabs from lines 148–164 into the "Anpassung" section (line 138), then remove the duplicate heading and its intro at lines 148–150. Keep the second "Lizenzverwaltung" section (currently at lines 168–180) as the sole license management section.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (1)
92-128: Consolidate duplicate section headers and subsections throughout file.Verification confirms multiple duplicated sections with mismatched heading levels and repeated command subsections:
Main section duplicates:
- "Systemüberwachung" at lines 92 (###) and 106 (##)
- "Speicher-Utilities" at lines 148 (###) and 178 (##)
- "Netzwerkdiagnosen" at lines 240 (###) and 258 (##)
- "Systemwartung" at lines 367 and 387 (both ##)
Repeated command subsections:
blockdev -getszat lines 196 and 224pingat lines 262 and 315This indicates incomplete document reorganization. Remove all redundant sections and consolidate each topic to a single, properly-structured location with consistent heading hierarchy.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx (1)
40-62: Resolve duplicate heading and organize parity error content.Lines 40 and 51 contain duplicate headings "What to do if you encounter %%parity|parity%% errors". The preceding section (lines 40-47) presents error handling as bullet points, while lines 51-57 restructure the same guidance as a numbered list. Additionally, line 59 appears to have an incomplete info box marker (
:::info[Rebuild Zeit).Consolidate these sections into a single, well-organized structure. Either keep the numbered list (lines 51-57) as the authoritative version and remove lines 40-47, or combine the best elements of both. Also complete the info box on line 59 or remove it if incomplete.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx (1)
103-171: Remove duplicate performance optimization sections.The performance optimization section contains significant content duplication:
- Lines 107–119 and lines 145–156 both describe "Automatische Festplattendefragmentierung deaktivieren" (identical content)
- Lines 133–143 and lines 158–170 both describe "Hochleistungsmodus aktivieren" (similar content, with lines 133–143 in English and lines 158–170 in German)
Keep only the German versions (lines 121–131 and 158–170) as the primary documentation, and remove the duplicate English-language and redundant German sections (lines 107–119, 133–143, and 145–156). This will improve clarity and prevent user confusion.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx (1)
236-247: Fix step numbering sequence in the migration section.Lines 236 and 247 both label a section as "Schritt 4: Bearbeiten Sie das XML für Ihre virtuelle Maschine," but Step 3 appears to be missing after the "Schritt 2" section at line 228. This breaks the logical workflow sequence and confuses readers.
Verify the correct step ordering in this migration workflow and update accordingly. The first instance at line 236 should either be relabeled to "Schritt 3" or removed if it duplicates the content at line 247.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx (2)
99-130: Remove duplicate collapsible section.Lines 99–108 and 110–130 both define an identically-named section "3. Erstellen und starten Sie die VM" with
<details>blocks. The first version (lines 99–108) contains only 4 incomplete steps, while the second (lines 110–130) is the comprehensive version with all 8 steps.This duplication will render both sections in the output, confusing readers. Delete lines 99–108 and retain the complete version at lines 110–130.
Apply this diff to remove the incomplete duplicate:
</details> -<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>
115-115: Fix preposition error: remove extraneous "zu" before "unter".Line 115 reads: "Greifen Sie auf das %%WebGUI|web-gui%% der %%VM|vm%% zu unter
http://[VM-IP]." The phrase "zu unter" (to under) is grammatically incorrect.Change to: "Greifen Sie auf das %%WebGUI|web-gui%% der %%VM|vm%% unter
http://[VM-IP]zu" or more simply: "Greifen Sie unterhttp://[VM-IP]auf das %%WebGUI|web-gui%% der %%VM|vm%% zu."Apply this diff:
- 1. Greifen Sie auf das %%WebGUI|web-gui%% der %%VM|vm%% zu unter `http://[VM-IP]`. + 1. Greifen Sie unter `http://[VM-IP]` auf das %%WebGUI|web-gui%% der %%VM|vm%% zu.
🧹 Nitpick comments (17)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/pool-single-device-mode.mdx (1)
8-8: Minor grammar suggestion: Consider hyphenating compound adjective.Static analysis flagged that "single device mode" should be hyphenated as "single-device mode" when used as a compound adjective. However, this phrase appears to be part of shared template text (used across multiple localizations), so any change should be applied consistently across the entire documentation suite if adopted.
This is a minor style point and may be deferred if terminology consistency is already established in your documentation guidelines.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (1)
252-327: Clarify cache reformatting section structure.The cache reformatting section (starting at line 252) has confusing organization with nested instructions, warnings, and multiple subsections. The flow is unclear—lines 252–264 contain steps, then at line 265 it transitions to "Um Daten und Einstellungen wiederherzustellen," followed by "### Neues Format eines Cache-Laufwerks" at line 267 with different instructions. This creates ambiguity about which steps apply in which scenarios.
Consider:
- Reorganizing so the primary workflow is linear and clear
- Clearly separating optional substeps from main steps
- Providing a high-level overview before diving into details
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx (1)
180-180: Fix quotation mark formatting in WireGuard attribution.Line 180 uses straight double quotes (
"%%WireGuard|wireguard%%") which the static analysis suggests should use German quotation marks („%%WireGuard|wireguard%%"). Apply consistent typographic conventions for German text.-\* *"%%WireGuard|wireguard%%" und das "%%WireGuard|wireguard%%" Logo sind eingetragene Marken von Jason A. Donenfeld.* +\* *„%%WireGuard|wireguard%%" und das „%%WireGuard|wireguard%%" Logo sind eingetragene Marken von Jason A. Donenfeld.*i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md (4)
50-50: Standardize German quotation mark style.The file uses straight double quotes (
") in several places (lines 50, 139, 170, 187), but German typography convention requires guillemets or German quotes („"or«»). Crowdin may have introduced these during translation. Consider standardizing to German quotation marks for consistency with German documentation standards.Examples:
- Line 50:
_**Tools → Neue Konfiguration**_)should use German quotes around configuration terms if needed- Line 139:
"Terminal"should be„Terminal"- Line 170:
"dangling links"should be„dangling links"- Line 187:
"iso8859-1"and"utf8"should be„iso8859-1"and„utf8"Also applies to: 139-139, 170-170, 187-187
87-87: Resolve hyphenation inconsistency in compound words.Line 87 uses "Netzwerk-Änderungen" (with hyphen), while line 89 uses "Netzwerkänderungen" (without hyphen). In German, compound nouns are typically written as a single word without hyphenation. Standardize to "Netzwerkänderungen" consistently across the file.
Also applies to: 89-89
136-136: Remove extra spaces around forward slashes.Line 136 contains
Docker / Plugin / VM-Popupwith spaces around the slashes. Standard formatting removes these spaces:Docker/Plugin/VM-Popupfor better readability and consistency.
78-85: Consider standardizing fix/improvement terminology.Lines 78-85 use "Verbesserung" (Improvement), "Fix", and "Korrektur" (Correction) interchangeably for similar changelog items. While this may be intentional to distinguish between feature improvements and bug fixes, consider standardizing the prefix terminology for consistency throughout the release notes.
i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md (2)
64-64: Remove unnecessary underscore emphasis around pool state errors.Line 64 has underscore-wrapped text (
_État du pool incorrect, extension invalide_) that appears redundant given the surrounding context. Simplify by removing the underscores or replace with standard markdown emphasis if semantic emphasis is intended.LanguageTool also flagged unnecessary punctuation at this location. Verify the intended formatting aligns with the document's emphasis conventions.
269-269: Verify underscore formatting around UI path.Line 269 wraps a UI path in underscores:
_**Paramètres → Gestionnaire de VM → Afficher l'utilisation de VM**_. This creates redundant emphasis (both underscores and bold asterisks). Simplify to**Paramètres → Gestionnaire de VM → Afficher l'utilisation de VM**for consistency with other UI paths in the document.LanguageTool flagged unnecessary punctuation here as well.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/managing-and-customizing-containers.mdx (1)
142-142: Minor: Consider typographic improvement for punctuation.Per static analysis, line 142 uses a hyphen with spaces ("haben - nicht") which could be replaced with an en dash for better German typography. While this is minor, it improves consistency with professional typographical standards.
Consider updating to:
...eingerichtet haben – nicht den Host-Pfad.(using an en dash instead of spaced hyphen).i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (1)
379-379: Verify WireGuard trademark notice formatting.The German quotation marks in line 379 use straight quotes (
") instead of German-style quotes („and"). While this may render correctly, consider updating to proper German quotation formatting for consistency with localization best practices.-\* *"%%WireGuard|wireguard%%" und das "%%WireGuard|wireguard%%" Logo sind eingetragene Marken von Jason A. Donenfeld.* +\* *„%%WireGuard|wireguard%%" und das „%%WireGuard|wireguard%%" Logo sind eingetragene Marken von Jason A. Donenfeld.*i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md (1)
16-16: Optional: Consider German alternative for "Workaround".Line 16 uses the English term "Workaround" (highlighted by LanguageTool). While not critical, a German equivalent like "Umgehungslösung" would improve localization consistency. This is a minor, optional refinement.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx (2)
48-56: Clean up table formatting to remove unnecessary spaces.The configuration table contains extra spaces causing alignment issues flagged by LanguageTool. While markdown tables are forgiving, unnecessary trailing/leading spaces reduce readability and may cause rendering inconsistencies.
Trim excess spaces in the header separator row and ensure consistent spacing across all table cells. Most notably, lines 51, 53, 55, and 56 have trailing spaces that should be removed for consistency.
26-42: Clarify the flow between section heading and instructions.After the heading "## Erstellen einer Time Machine-Freigabe" (line 26), the caution block at lines 28-40 interrupts the flow before line 42 restarts with "Um eine Time Machine-Freigabe zu erstellen:" This reads as if the section begins twice.
Consider restructuring so that the caution is positioned either before the heading (as a prerequisite) or after the introductory instruction, making the flow more intuitive.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx (1)
30-34: Apply German quotation mark conventions.The new error guidance is helpful and well-placed. However, LanguageTool correctly flags that German text should use guillemets („...") instead of straight quotes ("...") for quotation marks.
Apply this diff to use proper German quotation marks:
- Wenn Sie den Fehler "Schlüsseldatei ist nicht gültig" sehen, könnte Ihr Schlüssel auf der schwarzen Liste stehen oder nicht der letzte gültige Schlüssel sein. [Kontaktieren Sie den Unraid-Support](https://unraid.net/support) für Unterstützung. + Wenn Sie den Fehler „Schlüsseldatei ist nicht gültig" sehen, könnte Ihr Schlüssel auf der schwarzen Liste stehen oder nicht der letzte gültige Schlüssel sein. [Kontaktieren Sie den Unraid-Support](https://unraid.net/support) für Unterstützung.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (1)
465-465: Gitleaks warnings are false positives; consider adding inline suppression for documentation code examples.Lines 465 and 531 are correctly flagged by Gitleaks as false positives—both contain code examples using the placeholder text
password=yourpassword, not actual credentials. To suppress these warnings, add agitleaks:allowinline comment above the line in the source file. Alternatively, if inline comments don't persist through your CI environment, use a.gitleaksignoreallowlist at the repository level to exclude this pattern from documentation code blocks.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx (1)
143-238: VM-Snapshots section is comprehensive but may benefit from structural review.The new VM-Snapshots section (lines 143–238) is substantial, detailed, and well-organized with tabbed content. The structure using Tabs and TabItems is appropriate. However, at ~95 lines within a single section with nested details, it may be worth considering:
- Whether the extremely detailed snapshot management explanations (lines 201–220) could be moved to a dedicated advanced guide or collapsed
<details>block to reduce cognitive load for beginners.- Testing the tabbed interface on mobile and desktop to ensure usability.
The content quality is high and the use cases (lines 260–267) are helpful. No blocking issues detected; this is a recommendation for future refinement if needed.
Consider moving the most advanced snapshot management details (Block Commit, Block Pull operations) into a collapsible
<details>section or separate subsection if you want to keep the main tabs more concise. For now, the current structure is acceptable.
| :::tip[Best Praktiken] | ||
|
|
||
| - Versuchen Sie, die Liste mit einem klaren Anfangssatz einzuführen, der in einem Doppelpunkt endet. | ||
| - Verwenden Sie maximal 4–6 Elemente in einer ungeordneten Liste, um das Scannen und Merken zu erleichtern. Längere Listen sind möglicherweise besser als Tabelle darzustellen. | ||
| - Vermeiden Sie Tabellen mit nur 1 oder 2 Zellen; stattdessen verwenden Sie Aufzählungslisten oder Sätze. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
🧩 Analysis chain
Misplaced table-avoidance guidance in the Lists section.
Line 91–92 advises against 1–2 cell tables, but this appears in the Lists section's best practices. This same guidance is repeated identically in the Tables section (line 102). While the advice itself is sound, having it in both sections—especially in a section about lists—is contextually confusing.
Consider removing the table-specific guidance from the Lists section and retaining it only in the Tables section where it belongs.
Verify whether this duplication is intentional (to reinforce the principle across both sections) or whether it should be removed from the Lists section.
🏁 Script executed:
#!/bin/bash
# Examine the German style guide file to verify the review comment's claims
file_path="i18n/de/docusaurus-plugin-content-docs/current/contribute/style-guide.mdx"
# Check if file exists and show lines 85-110 for context
if [ -f "$file_path" ]; then
echo "=== Lines 85-110 of the file ==="
sed -n '85,110p' "$file_path" | cat -n
else
echo "File not found at: $file_path"
fiLength of output: 92
🏁 Script executed:
#!/bin/bash
# Search for the German style guide file in the repository
echo "=== Searching for German style guide files ==="
fd -t f "style-guide.mdx" | head -20
echo ""
echo "=== Searching in i18n directories ==="
fd -t d "de" i18n 2>/dev/null | head -10
echo ""
echo "=== Full search for the file ==="
find . -name "style-guide.mdx" -path "*/de/*" 2>/dev/nullLength of output: 532
🏁 Script executed:
#!/bin/bash
# Extract the relevant sections to verify the duplication claim
file_path="./i18n/de/docusaurus-plugin-content-docs/current/contribute/style-guide.mdx"
echo "=== Lines 85-110 with context ==="
sed -n '85,110p' "$file_path" | nl -v 85
echo ""
echo "=== Full content around Lists section (lines 80-100) ==="
sed -n '80,100p' "$file_path"
echo ""
echo "=== Full content around Tables section (lines 95-110) ==="
sed -n '95,110p' "$file_path"Length of output: 1715
Confirmed: Table-avoidance guidance is duplicated and misplaced in the Lists section.
The verification confirms the review comment is accurate. The line "Vermeiden Sie Tabellen mit nur 1 oder 2 Zellen; stattdessen verwenden Sie Aufzählungslisten oder Sätze." appears identically in both:
- Lists section best practices (contextually inappropriate)
- Tables section best practices (correctly placed)
Removing this table-specific guidance from the Lists section is the right fix, as it belongs only in the Tables section where it provides meaningful context.
🧰 Tools
🪛 LanguageTool
[grammar] ~88-~88: Ergänze ein Satzzeichen
Context: ...rray|array%% zu starten..." :::tip[Best Praktiken] - Versuchen Sie, die Liste m...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_BESTDASHPRAKTIKEN)
[grammar] ~88-~88: Hier könnte ein Fehler sein.
Context: ...% zu starten..." :::tip[Best Praktiken] - Versuchen Sie, die Liste mit einem klare...
(QB_NEW_DE)
[grammar] ~90-~90: Hier könnte ein Fehler sein.
Context: ...uführen, der in einem Doppelpunkt endet. - Vermeiden Sie Tabellen mit nur 1 oder 2 ...
(QB_NEW_DE)
[grammar] ~91-~91: Hier könnte ein Fehler sein.
Context: ...wenden Sie Aufzählungslisten oder Sätze. ::: ### Tabellen Tabellen sind eine gr...
(QB_NEW_DE)
[grammar] ~93-~93: Hier könnte ein Fehler sein.
Context: ...n Sie Aufzählungslisten oder Sätze. ::: ### Tabellen Tabellen sind eine großartige ...
(QB_NEW_DE)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/contribute/style-guide.mdx around
lines 88-93: the Lists section contains a duplicated, table-specific guidance
sentence ("Vermeiden Sie Tabellen mit nur 1 oder 2 Zellen; stattdessen verwenden
Sie Aufzählungslisten oder Sätze.") that belongs only in the Tables
section—remove that sentence from this Best Praktiken tip in the Lists section,
leaving the remaining list item(s) intact and preserving formatting/spacing of
the :::tip block so only the unrelated table guidance is eliminated.
| :::note[Server Kontext erforderlich | ||
|
|
||
| Wenn Sie das Einlösungsformular nicht sehen, müssen Sie möglicherweise zuerst Ihren Serverkontext laden. Klicken Sie auf **"Server verwalten"**, um Ihren Server mit der Kontoanwendung zu verbinden. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Critical: Fix missing closing bracket in admonition.
Line 58 is missing the closing bracket for the admonition label.
Current:
:::note[Server Kontext erforderlich
Should be:
:::note[Server Kontext erforderlich]
Without the closing ], the admonition will fail to parse correctly in Docusaurus.
Apply this diff:
-:::note[Server Kontext erforderlich
+:::note[Server Kontext erforderlich]🧰 Tools
🪛 LanguageTool
[typographical] ~58-~58: Zeichen ohne sein Gegenstück: ‚]‘ scheint zu fehlen
Context: ...enz auf dem Server installiert. :::note[Server Kontext erforderlich Wenn Sie da...
(UNPAIRED_BRACKETS)
[grammar] ~58-~58: Hier könnte ein Fehler sein.
Context: ...rt. :::note[Server Kontext erforderlich Wenn Sie das Einlösungsformular nicht se...
(QB_NEW_DE)
[grammar] ~60-~60: Ersetze das Satzzeichen
Context: ... Serverkontext laden. Klicken Sie auf "Server verwalten", um Ihren Server mit der K...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~60-~60: Ersetze das Satzzeichen
Context: ...ontext laden. Klicken Sie auf "Server verwalten", um Ihren Server mit der Kontoanwendu...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~60-~60: Hier könnte ein Fehler sein.
Context: ...ver mit der Kontoanwendung zu verbinden. ::: ## Wichtige Hinweise - Aktivierung...
(QB_NEW_DE)
[grammar] ~62-~62: Hier könnte ein Fehler sein.
Context: ...it der Kontoanwendung zu verbinden. ::: ## Wichtige Hinweise - Aktivierungscodes s...
(QB_NEW_DE)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
around lines 58 to 62: the admonition opening is missing the closing bracket in
":::note[Server Kontext erforderlich" so update the line to include the closing
square bracket (:::note[Server Kontext erforderlich]) so the admonition label is
properly delimited and will parse correctly in Docusaurus.
| --- | ||
|
|
||
| \* *„%%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 and verify trademark terminology.
Line 126 has two issues:
-
Quotation mark formatting: LanguageTool flags that German text should use German quotation marks („...") rather than straight quotes ("..."). This is standard for German typography.
-
Terminology precision: The change from "eingetragene Warenzeichen" (registered trademarks) to "eingetragene Marken" (registered marks) is less precise for a legal trademark notice. Verify whether this terminology change was intentional and appropriate for the legal context.
Apply this diff to use proper German quotation marks:
-\* *"%%WireGuard|wireguard%%" und das "%%WireGuard|wireguard%%" Logo sind eingetragene Marken von Jason A. Donenfeld.*
+\* *„%%WireGuard|wireguard%%"-Wort- und Bildmarken sind eingetragene Marken von Jason A. Donenfeld.*Or align with standard trademark attribution format:
-\* *"%%WireGuard|wireguard%%" und das "%%WireGuard|wireguard%%" Logo sind eingetragene Marken von Jason A. Donenfeld.*
+\* *„%%WireGuard|wireguard%%" ist eine eingetragene Marke von Jason A. Donenfeld.*📝 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.
| \* *"%%WireGuard|wireguard%%" und das "%%WireGuard|wireguard%%" Logo sind eingetragene Marken von Jason A. Donenfeld.* | |
| \* *„%%WireGuard|wireguard%%"-Wort- und Bildmarken sind eingetragene Marken von Jason A. Donenfeld.* |
| \* *"%%WireGuard|wireguard%%" und das "%%WireGuard|wireguard%%" Logo sind eingetragene Marken von Jason A. Donenfeld.* | |
| \* *„%%WireGuard|wireguard%%" ist eine eingetragene Marke von Jason A. Donenfeld.* |
🧰 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_„)
[grammar] ~126-~126: Hier könnte ein Fehler sein.
Context: ...getragene Marken von Jason A. Donenfeld.*
(QB_NEW_DE)
🤖 Prompt for AI Agents
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 quotes around the WireGuard token
with German typographic quotation marks („...“) and restore or confirm the
precise trademark wording by changing "eingetragene Marken" back to the more
legally precise "eingetragene Warenzeichen" (unless the legal reviewer
intentionally wanted "Marken"); ensure the line reads using German quotes and
the chosen legal term consistently.
| ## NFS (Network File System) | ||
|
|
||
| **Network Services** let you configure network communication protocols on your Unraid server, which are essential for user and disk shares. You can also enable an %%FTP|ftp%% server, a logging server, and set up a %%VPN|vpn-tunnel%% for secure remote access. |
There was a problem hiding this comment.
Translate remaining English content in the NFS section.
The section heading was changed to German ("NFS (Network File System)"), but line 124 still contains English text ("Network Services let you configure..."). This content should be translated to German for consistency with the rest of the file.
-## NFS (Network File System)
+## NFS (Network File System)
-**Network Services** let you configure network communication protocols on your Unraid server, which are essential for user and disk shares. You can also enable an %%FTP|ftp%% server, a logging server, and set up a %%VPN|vpn-tunnel%% for secure remote access.
+**Netzwerkdienste** ermöglichen es Ihnen, Netzwerkkommunikationsprotokolle auf Ihrem Unraid-Server zu konfigurieren, die für Benutzer- und Datenträgerfreigaben wesentlich sind. Sie können auch einen %%FTP|ftp%% Server, einen Protokollierungsserver aktivieren und ein %%VPN|vpn-tunnel%% für sicheren Fernzugriff einrichten.📝 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.
| ## NFS (Network File System) | |
| **Network Services** let you configure network communication protocols on your Unraid server, which are essential for user and disk shares. You can also enable an %%FTP|ftp%% server, a logging server, and set up a %%VPN|vpn-tunnel%% for secure remote access. | |
| ## NFS (Network File System) | |
| **Netzwerkdienste** ermöglichen es Ihnen, Netzwerkkommunikationsprotokolle auf Ihrem Unraid-Server zu konfigurieren, die für Benutzer- und Datenträgerfreigaben wesentlich sind. Sie können auch einen %%FTP|ftp%% Server, einen Protokollierungsserver aktivieren und ein %%VPN|vpn-tunnel%% für sicheren Fernzugriff einrichten. |
🧰 Tools
🪛 LanguageTool
[grammar] ~122-~122: Hier könnte ein Fehler sein.
Context: ...ng) ## NFS (Network File System) Network Services let you configure net...
(QB_NEW_DE)
[grammar] ~124-~124: Korrigiere die Fehler
Context: ... Network Services let you configure network communication protocols on your Unraid ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~124-~124: Korrigiere die Fehler
Context: ...rk Services** let you configure network communication protocols on your Unraid server, which ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~124-~124: Korrigiere die Fehler
Context: ...let you configure network communication protocols on your Unraid server, which are essential for ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~124-~124: Korrigiere die Fehler
Context: ...k communication protocols on your Unraid server, which are essential for user and disk ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~124-~124: Korrigiere die Fehler
Context: ...cation protocols on your Unraid server, which are essential for user and disk shares....
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~124-~124: Korrigiere die Fehler
Context: ... protocols on your Unraid server, which are essential for user and disk shares. You...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~124-~124: Korrigiere die Fehler
Context: ...tocols on your Unraid server, which are essential for user and disk shares. You can also ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~124-~124: Korrigiere die Fehler
Context: ...your Unraid server, which are essential for user and disk shares. You can also enab...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~124-~124: Korrigiere die Fehler
Context: ... Unraid server, which are essential for user and disk shares. You can also enable an...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~124-~124: Korrigiere die Fehler
Context: ...id server, which are essential for user and disk shares. You can also enable an %%F...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~124-~124: Korrigiere die Fehler
Context: ...erver, which are essential for user and disk shares. You can also enable an %%FTP|ftp%% ser...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~124-~124: Hier könnte ein Fehler sein.
Context: ...N|vpn-tunnel%% for secure remote access. ### NFS (Network File System) NFSv4 support...
(QB_NEW_DE)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
around lines 122–124, the paragraph under the NFS heading is still in English;
replace the English sentence with a German translation while preserving markup
(bold and link tokens like **Network Services**, %%FTP|ftp%% and
%%VPN|vpn-tunnel%%). Suggested replacement: **Network Services** ermöglichen es
Ihnen, die Netzwerkkommunikationsprotokolle auf Ihrem Unraid-Server zu
konfigurieren, die für Benutzer- und Festplattenfreigaben wesentlich sind; Sie
können außerdem einen %%FTP|ftp%%-Server, einen Protokollierungsserver
aktivieren und ein %%VPN|vpn-tunnel%% für sicheren Remote-Zugriff einrichten.
|
|
||
| :::important | ||
|
|
||
| Der Unraid-Server ist über Ihr LAN zugänglich, sobald er vollständig gestartet ist. Sie können die IP-Adresse in der DHCP-Clientliste Ihres Routers finden oder ein Netzwerk-Scan-Tool verwenden. |
There was a problem hiding this comment.
Inconsistent compound word usage: "Unraid-Server" vs. "unraidserver".
Line 25 uses "Unraid-Server" (with hyphen) while the example hostname earlier uses "unraidserver" (no hyphen, lowercase). Standardize on one form for consistency. Per the static analysis tool, compound coherency should be maintained throughout.
Recommend using "Unraid-Server" consistently (with hyphen) as it matches the brand style used elsewhere in German technical documentation.
- Der Unraid-Server ist über Ihr LAN zugänglich, sobald er vollständig gestartet ist.
+ Der Unraid Server ist über Ihr LAN zugänglich, sobald er vollständig gestartet ist.Alternatively, if "unraidserver" is preferred for hostname examples, ensure the descriptive text uses the same casing/hyphenation for brand references.
Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~25-~25: Uneinheitliche Verwendung von Bindestrichen. Der Text enthält sowohl ‚Unraid-Server‘ als auch ‚unraidserver‘.
Context: ...r .local-Adressen. :::important Der Unraid-Server ist über Ihr LAN zugänglich, sobald er ...
(DE_COMPOUND_COHERENCY)
[grammar] ~25-~25: Hier könnte ein Fehler sein.
Context: ...n oder ein Netzwerk-Scan-Tool verwenden. ::: ## Ein Root-Passwort festlegen Wen...
(QB_NEW_DE)
🤖 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 line 25, the text uses "Unraid-Server" while an earlier hostname example
uses "unraidserver", causing inconsistent compound-word usage; standardize on
"Unraid-Server" (with hyphen) for all prose references by replacing occurrences
of "unraidserver" in descriptive text with "Unraid-Server", and if any instances
are literal hostname examples, change them to the hyphenated lowercase form
"unraid-server" to preserve hostname conventions while keeping the hyphen
consistent.
| ## 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 space after colon before list item.
Spanish release notes have the same formatting issue: extra space after fixes: before the list item. Reduce to single space.
🧰 Tools
🪛 LanguageTool
[grammar] ~58-~58: Aquí puede haber un error.
Context: ...d**_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actual...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~58-~58: Aquí puede haber un error.
Context: ...*_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actualiz...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~58-~58: Aquí puede haber un error.
Context: ...ener los siguientes parches / hot fixes: - Un subconjunto de actualizaciones de seg...
(QB_NEW_ES)
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.4.md
around line 58, there's an extra space after the colon before the list item
("fixes: para..."); edit the line to remove the extra space so there is only a
single space after the colon (i.e., "fixes: para..." → "fixes: para..." with one
space), preserving the surrounding punctuation and markdown formatting.
| ## 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 space after colon before list item.
Spanish 6.12.0 release notes have the same spacing issue at the patch tool reference on line 576: extra space between the colon and list hyphen.
🧰 Tools
🪛 LanguageTool
[grammar] ~576-~576: Aquí puede haber un error.
Context: ...d**_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actual...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~576-~576: Aquí puede haber un error.
Context: ...*_ para obtener los siguientes parches / hot fixes: - Un subconjunto de actualiz...
(QB_NEW_ES_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~576-~576: Aquí puede haber un error.
Context: ...ener los siguientes parches / hot fixes: - Un subconjunto de actualizaciones de seg...
(QB_NEW_ES)
🤖 Prompt for AI Agents
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.0.md
around line 576: there is an extra space after the colon before the list hyphen
in the patch tool sentence; remove the stray space so the colon is directly
followed by the list item marker (i.e., change "Herramientas → Parche de
Unraid**_ para obtener los siguientes parches / hot fixes:" plus a space before
the hyphen to have no space between the colon and the list hyphen), ensuring
spacing matches surrounding list formatting.
| ## Correctifs | ||
|
|
||
| Avec le plugin Unraid Patch installé, visitez ***Outils → Unraid Patch*** pour obtenir les correctifs / corrections à chaud suivants : | ||
| Avec le plugin Unraid Patch installé, visitez _**Outils → Unraid Patch**_ pour obtenir les correctifs / corrections à chaud suivants : |
There was a problem hiding this comment.
Remove extra space after colon before list item.
The French release notes have the same spacing inconsistency: extra space between the colon in suivants : and the list hyphen. Reduce to single space.
🧰 Tools
🪛 LanguageTool
[grammar] ~60-~60: Il y a peut-être une erreur ici
Context: ...ir les correctifs / corrections à chaud suivants : - Un sous-ensemble de mises à jour de sécu...
(QB_NEW_FR)
🤖 Prompt for AI Agents
In
i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.4.md
around line 60, there is an extra space between the colon in "suivants :" and
the following list hyphen; remove the extra space so the colon and the list
start use a single space ("suivants: -") or adjust the line break so the colon
is followed by a single space before the list item, ensuring consistent spacing.
| :::warning[Removed in Unraid 7.2.1] | ||
|
|
||
| This command line option was removed in Unraid 7.2.1. On newer releases, use the WebGUI method instead. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Translate admonition block to French.
The admonition block at lines 140–144 is entirely in English within a French-language document. This breaks localization consistency and readability for French speakers. The text should be translated to French to match the surrounding content.
Suggested translation:
-:::warning[Removed in Unraid 7.2.1]
+:::warning[Supprimé dans Unraid 7.2.1]
-This command line option was removed in Unraid 7.2.1. On newer releases, use the WebGUI method instead. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details.
+Cette option de ligne de commande a été supprimée dans Unraid 7.2.1. Sur les versions plus récentes, utilisez plutôt la méthode WebGUI. Voir [Convertir en un nouveau type de système de fichiers](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) pour plus de détails.
:::📝 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.
| :::warning[Removed in Unraid 7.2.1] | |
| This command line option was removed in Unraid 7.2.1. On newer releases, use the WebGUI method instead. See [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) for details. | |
| ::: | |
| :::warning[Supprimé dans Unraid 7.2.1] | |
| Cette option de ligne de commande a été supprimée dans Unraid 7.2.1. Sur les versions plus récentes, utilisez plutôt la méthode WebGUI. Voir [Convertir en un nouveau type de système de fichiers](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type) pour plus de détails. | |
| ::: |
🧰 Tools
🪛 LanguageTool
[typographical] ~140-~140: Une espace est requise.
Context: ...'mover' pour vider un disque d'array :::warning[Removed in Unraid 7.2.1] This c...
(DEUX_POINTS_ESPACE)
[grammar] ~140-~140: Il y a peut-être une erreur ici
Context: ...ray :::warning[Removed in Unraid 7.2.1] This command line option was removed in ...
(QB_NEW_FR)
[grammar] ~142-~142: Il y a peut-être une erreur ici
Context: ...-to-a-new-file-system-type) for details. ::: Le Mover peut maintenant être utili...
(QB_NEW_FR)
[grammar] ~144-~144: Il y a peut-être une erreur ici
Context: ...-new-file-system-type) for details. ::: Le Mover peut maintenant être utilisé po...
(QB_NEW_FR)
🤖 Prompt for AI Agents
In
i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
around lines 140–144, the admonition block is still in English; replace it with
a French translation so it matches the document locale. Change the block content
to a French version conveying the same message (e.g. indicate the command-line
option was removed in Unraid 7.2.1, instruct users to use the WebGUI on newer
releases, and point to the existing French documentation page for converting
file systems), updating the link text to French as needed.
| - Avec le tableau en cours d'exécution, sur _**Principal → Périphériques de la piscine**_, sélectionnez le nom de la piscine pour voir les détails | ||
| - Dans la zone **Statut du Pool**, vérifiez l'existence d'un bouton **Mettre à jour le Pool**. Si c'est le cas, vous devrez cliquer dessus avant de continuer. Notez qu'une mise à jour du pool limitera votre capacité à revenir aux versions précédentes d'Unraid (7.1 devrait être OK, mais pas 7.0). | ||
| - Arrêtez l'array | ||
| - Sur ***Main → Pool Devices***, ajoutez un emplacement au pool | ||
| - Sur _**Main → Pool Devices**_, ajoutez un emplacement au pool | ||
| - Sélectionnez le disque approprié (doit être au moins aussi grand que le plus petit disque du pool) | ||
| - Démarrez l'array | ||
|
|
There was a problem hiding this comment.
Inconsistent language in UI navigation path.
Line 37 contains English text ("Main → Pool Devices") while the preceding line 34 uses French ("Principal → Périphériques de la piscine"). This appears to be a partial translation or localization error in the French documentation.
Verify the correct French translation and apply consistently:
- Sur _**Main → Pool Devices**_, ajoutez un emplacement au pool
+ Sur _**Principal → Périphériques de la piscine**_, ajoutez un emplacement au poolOr confirm if this English text is intentional (e.g., if it refers to a specific UI label that must remain untranslated).
📝 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.
| - Avec le tableau en cours d'exécution, sur _**Principal → Périphériques de la piscine**_, sélectionnez le nom de la piscine pour voir les détails | |
| - Dans la zone **Statut du Pool**, vérifiez l'existence d'un bouton **Mettre à jour le Pool**. Si c'est le cas, vous devrez cliquer dessus avant de continuer. Notez qu'une mise à jour du pool limitera votre capacité à revenir aux versions précédentes d'Unraid (7.1 devrait être OK, mais pas 7.0). | |
| - Arrêtez l'array | |
| - Sur ***Main → Pool Devices***, ajoutez un emplacement au pool | |
| - Sur _**Main → Pool Devices**_, ajoutez un emplacement au pool | |
| - Sélectionnez le disque approprié (doit être au moins aussi grand que le plus petit disque du pool) | |
| - Démarrez l'array | |
| - Avec le tableau en cours d'exécution, sur _**Principal → Périphériques de la piscine**_, sélectionnez le nom de la piscine pour voir les détails | |
| - Dans la zone **Statut du Pool**, vérifiez l'existence d'un bouton **Mettre à jour le Pool**. Si c'est le cas, vous devrez cliquer dessus avant de continuer. Notez qu'une mise à jour du pool limitera votre capacité à revenir aux versions précédentes d'Unraid (7.1 devrait être OK, mais pas 7.0). | |
| - Arrêtez l'array | |
| - Sur _**Principal → Périphériques de la piscine**_, ajoutez un emplacement au pool | |
| - Sélectionnez le disque approprié (doit être au moins aussi grand que le plus petit disque du pool) | |
| - Démarrez l'array |
🧰 Tools
🪛 LanguageTool
[grammar] ~34-~34: Élément manquant
Context: ...nnez le nom de la piscine pour voir les détails - Dans la zone Statut du Pool, véri...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[style] ~35-~35: Un autre mot peut sembler plus précis et percutant.
Context: ...l**, vérifiez l'existence d'un bouton Mettre à jour le Pool. Si c'est le cas, vous devrez...
(METTRE_A_JOUR)
[grammar] ~35-~35: Il y a peut-être une erreur ici
Context: ...aid (7.1 devrait être OK, mais pas 7.0). - Arrêtez l'array - Sur _**Main → Pool Dev...
(QB_NEW_FR)
[grammar] ~36-~36: Élément manquant
Context: ...vrait être OK, mais pas 7.0). - Arrêtez l'array - Sur Main → Pool Devices, ajoute...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~37-~37: Élément manquant
Context: ...l Devices**_, ajoutez un emplacement au pool - Sélectionnez le disque approprié (doi...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[style] ~38-~38: Dans un contexte formel des synonymes peuvent enrichir votre style.
Context: ...ool - Sélectionnez le disque approprié (doit être au moins aussi grand que le plus petit ...
(REP_DEVOIR)
[grammar] ~38-~38: Élément manquant
Context: ...aussi grand que le plus petit disque du pool) - Démarrez l'array #### Améliorations ...
(QB_NEW_FR_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~39-~39: Il y a peut-être une erreur ici
Context: ...petit disque du pool) - Démarrez l'array #### Améliorations - Correctif : Un avertiss...
(QB_NEW_FR)
🤖 Prompt for AI Agents
In
i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md
around lines 34 to 40, the UI navigation path on line 37 is in English ("Main →
Pool Devices") while the rest is French; replace that English phrase with the
consistent French translation used above (e.g., "Principal → Périphériques de la
piscine") so the navigation path is fully localized, or if the English label is
intentional because it matches an untranslated UI string, leave it but add a
short parenthetical note indicating it is the literal UI label that must remain
in English.
There was a problem hiding this comment.
Actionable comments posted: 8
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
220-241: Remove redundant repeated content in "Compresión y RAM" section.Lines 224 and 237–240 contain identical text about importing ZFS pools. The same guidance appears both in the section text and within the
:::tipblock, creating redundancy. Remove one instance to improve readability.Consider removing the tip block entirely if it duplicates the preceding paragraph, or restructure to provide distinct complementary information.
♻️ Duplicate comments (20)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.0.md (2)
9-9: Fix incorrect anchor reference in German documentation link.The anchor
#license-types--featuresdoes not exist in the Germanlicensing-faq.mdxfile. The target heading "## Lizenztypen & Funktionen" auto-generates the anchor#lizenztypen--funktionen.- Fragen zu Ihrer [Lizenz](../../unraid-os/troubleshooting/licensing-faq.mdx#license-types--features)? + Fragen zu Ihrer [Lizenz](../../unraid-os/troubleshooting/licensing-faq.mdx#lizenztypen--funktionen)?
62-62: Fix incorrect anchor reference for file system conversion link.The anchor
#converting-to-a-new-file-system-typedoes not exist in the Germanfile-systems.mdxfile. The target heading "## Ändern eines Dateisystemtyps" (line 163 of the German file) auto-generates the anchor#ändern-eines-dateisystemtyps.- Weitere Details finden Sie in den Docs unter [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#converting-to-a-new-file-system-type). + Weitere Details finden Sie in den Docs unter [Converting to a new file system type](../using-unraid-to/manage-storage/file-systems.mdx#ändern-eines-dateisystemtyps).i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (2)
177-189: Unclosed bracket in admonition syntax (persisting from prior review).Line 177 still contains a malformed admonition opening:
:::tip[Optimizing Festplattenanzahlenwithout a closing bracket. This causes rendering errors and was flagged in prior reviews but remains unresolved. LanguageTool confirms: "Zeichen ohne sein Gegenstück: ‚]' scheint zu fehlen" (unpaired bracket).Apply this diff to fix the syntax:
-:::tip[Optimizing Festplattenanzahlen +:::tip[Optimizing Festplattenanzahlen]
106-110: Incomplete tip admonition block with only a header line.The tip block (lines 106–110) opens with
:::tipand contains only a single header line ("To add a %%ZFS|zfs%% disk to the %%array|array%%:") before closing with no actual implementation steps, instructions, or substantive content. This was flagged in prior reviews as incomplete but remains unaddressed. Either complete the tip with actual actionable instructions or remove the placeholder block entirely.For example, if this should document the hybrid setup process, provide the full step-by-step instructions within the tip block:
:::tip - -To add a %%ZFS|zfs%% disk to the %%array|array%%: - +To add a %%ZFS|zfs%% disk to the %%array|array%%: + +1. Go to the **Main** tab in the %%WebGUI|web-gui%%. +2. Stop the %%array|array%%. +3. [Additional steps...] + :::Alternatively, if this tip is a duplicate of the detailed section that follows (lines 139–157), consider removing it to avoid redundancy.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/adding-disks-to-array.mdx (1)
1-169: ** Extensive English content in German documentation persists from prior review.**This file continues to contain substantial untranslated English mixed throughout German content, as flagged in the previous review. The issues flagged before remain unresolved (lines 10–12, 24, 32, 58, 94, 102–103, 114–119, 121, 123–125, 130, 134–140, 158, 166–167, 174). Additionally, two critical MDX syntax errors prevent proper rendering:
- Line 107:
:::important\[Requirements]has an incorrect backslash escape; change to:::important[Requirements]or use proper MDX syntax (e.g.,:::important[Anforderungen]with a German label).- Line 165:
:::tip[Planning Ihren Paritätsupgradeis missing the closing bracket; change to:::tip[Planning Ihren Paritätsupgrade].Recommendation: Before merging, ensure all English content is translated to German to maintain documentation consistency, and fix the MDX syntax errors to prevent rendering failures.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx (5)
20-20: ** Untranslated English paragraph requires German translation.**Line 20 contains an entire paragraph in English that breaks the German documentation flow: "You can initiate a check using the Check button under Array Operations...". This should be translated to German, preserving the
%%parity check|parity-check%%and%%read check|read-check%%tokens.Suggested translation:
- You can initiate a check using the **Check** button under ***Array Operations***. Depending on your array's configuration, this button allows you to conduct either a %%parity check|parity-check%% or a %%read check|read-check%%. + Sie können eine Überprüfung über die Schaltfläche **Überprüfen** unter ***Array-Operationen*** einleiten. Je nach Konfiguration Ihres Arrays können Sie mit dieser Schaltfläche entweder eine %%parity check|parity-check%% oder eine %%read check|read-check%% durchführen.
46-46: ** Untranslated English paragraph requires German translation.**Line 46 contains English text that should be translated to German: "Whenever the system performs a %%parity check|parity-check%% or a %%read check|read-check%%, it keeps a record of what happened...". Preserve the placeholder tokens during translation.
Suggested translation:
- Whenever the system performs a %%parity check|parity-check%% or a %%read check|read-check%%, it keeps a record of what happened. You can view these details easily by clicking the **History** button found under ***Array Operations*** in the interface. + Immer wenn das System eine %%parity check|parity-check%% oder eine %%read check|read-check%% durchführt, führt es Aufzeichnungen über die Vorgänge. Sie können diese Details leicht anzeigen, indem Sie auf die Schaltfläche **Verlauf** unter ***Array-Operationen*** in der Oberfläche klicken.
52-52: ** Untranslated English paragraph requires German translation.**Line 52 contains untranslated English: "Unraid allows you to control the power states of your hard drives...". Translate to German while preserving the
%%spin them up or down|spin-state%%token.Suggested translation:
- Unraid allows you to control the power states of your hard drives. You can easily %%spin them up or down|spin-state%%, and manage SSDs to be active or in standby. This helps save energy, extend the life of your drives, and reduce noise when the disks are not being used. + Unraid ermöglicht es Ihnen, die Energiezustände Ihrer Festplatten zu steuern. Sie können diese leicht %%hochfahren oder herunterfahren|spin-state%%, und SSDs in den aktiven oder Standby-Modus schalten. Dies hilft, Energie zu sparen, die Lebensdauer Ihrer Laufwerke zu verlängern und Lärm zu reduzieren, wenn die Festplatten nicht verwendet werden.
72-76: ** Empty admonition block with label but no content.**Lines 72–76 define a
:::tipblock with label "Um den Schreibmodus zu ändern:" but provide no body content, leaving an empty block. Either add the intended tip content or remove the block entirely to prevent rendering an empty admonition.
118-124: ** Misplaced cache pools description in caution block about array reset.**Lines 122–123 contain a lengthy description of cache pools ("%%Cache-Pools|cache-pool%% in Unraid bieten erhebliche Vorteile...") that appears contextually out of place within a caution block about array configuration reset. This content disrupts the flow and confuses the reader.
Recommend relocating the cache pools description to a dedicated cache-management section or replacing it with guidance relevant to array reset (e.g., warnings about parity invalidation). If cache pools should be referenced here, provide brief context rather than a multi-sentence explanation.
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx (3)
12-12: ** Untranslated English paragraph requires German translation.**Line 12 contains an entire English paragraph that breaks the German documentation flow: "If you find that you no longer need the level of %%parity|parity%% protection in your setup, you can remove a %%parity disk|parity-drives%% whenever you want." Translate to German, preserving placeholder tokens.
Suggested translation:
- If you find that you no longer need the level of %%parity|parity%% protection in your setup, you can remove a %%parity disk|parity-drives%% whenever you want. + Wenn Sie feststellen, dass Sie den Grad des %%parity|parity%%-Schutzes in Ihrer Konfiguration nicht mehr benötigen, können Sie jederzeit eine %%parity disk|parity-drives%% entfernen.
75-75: ** Untranslated English sentence requires German translation.**Line 75 contains an English sentence at the end of the file: "Optionally run a correcting %%parity check|parity-check%% afterward to ensure parity integrity." Translate to German, preserving the placeholder token.
Suggested translation:
- 12. Optionally run a correcting %%parity check|parity-check%% afterward to ensure parity integrity. + 12. Führen Sie optional anschließend einen korrigierenden %%parity check|parity-check%% durch, um die Paritätsintegrität sicherzustellen.
31-31: Grammar error: Incorrect adjective form and singular noun for plural context.Line 31: "bei weiterer Plattenausfall" uses the wrong adjective form and singular noun. Change to the plural genitive form:
- Das Entfernen einer Datenplatte erfordert nachträglich einen Paritätssynchronisierungslauf. Bis dieser abgeschlossen ist, besteht bei weiterer Plattenausfall Gefahr eines Datenverlusts. + Das Entfernen einer Datenplatte erfordert nachträglich einen Paritätssynchronisierungslauf. Bis dieser abgeschlossen ist, besteht bei weiteren Plattenausfällen Gefahr eines Datenverlusts.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx (3)
32-32: Fix mixed-language header—this was flagged in the previous review.Line 32 still contains English "Before" in an otherwise German header. Change
:::note[Before Sie beginnen]to:::note[Bevor Sie beginnen]to maintain consistency.-:::note[Before Sie beginnen] +:::note[Bevor Sie beginnen]
246-246: Translate English text to German—this was flagged in the previous review.Line 246 contains English "Storage location: Snapshots are stored with your %%VM|vm%% files, so make sure you have enough space on your %%cache pools|cache-pool%% or %%array|array%%." This should be translated to German for consistency.
-- **Storage location**: Snapshots are stored with your %%VM|vm%% files, so make sure you have enough space on your %%cache pools|cache-pool%% or %%array|array%%. +- **Speicherort**: Snapshots werden zusammen mit Ihren %%VM|vm%%-Dateien gespeichert, stellen Sie daher sicher, dass Sie ausreichend Speicherplatz auf Ihrem %%cache pool|cache-pool%% oder %%array|array%% haben.
251-251: Translate English text to German—this was flagged in the previous review.Line 251 contains English "Actual snapshot data is stored alongside your %%VM|vm%% files on %%cache pools|cache-pool%% or %%array|array%%." This should be translated to German.
-- Actual snapshot data is stored alongside your %%VM|vm%% files on %%cache pools|cache-pool%% or %%array|array%%. +- Tatsächliche Snapshot-Daten werden neben Ihren %%VM|vm%%-Dateien auf den %%cache pools|cache-pool%% oder %%array|array%% gespeichert.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (4)
11-18: Duplicate introductory text persists.Lines 13-14 contain the same paragraph as line 17. Remove one instance to avoid redundancy while preserving the important block emphasis.
Apply this diff to remove the duplication:
:::important[Special gracias] - -%%ZFS|zfs%% aporta integridad de datos avanzada, configuraciones de almacenamiento flexibles y alto rendimiento a tu sistema Unraid. Esta guía explica los conceptos básicos de %%ZFS|zfs%% y te guía en la gestión de pools %%ZFS|zfs%% directamente desde el %%WebGUI|web-gui%% de Unraid. Ya sea que estés configurando un nuevo almacenamiento %%ZFS|zfs%% o integrando un pool existente, encontrarás los pasos y contexto que necesitas para comenzar con confianza. - ::: %%ZFS|zfs%% aporta integridad de datos avanzada, configuraciones de almacenamiento flexibles y alto rendimiento a tu sistema Unraid. Esta guía explica los conceptos básicos de %%ZFS|zfs%% y te guía en la gestión de pools %%ZFS|zfs%% directamente desde el %%WebGUI|web-gui%% de Unraid. Ya sea que estés configurando un nuevo almacenamiento %%ZFS|zfs%% o integrando un pool existente, encontrarás los pasos y contexto que necesitas para comenzar con confianza.Alternatively, if the important block should highlight the introduction, keep it inside and remove the duplication after the block closes.
177-189: Fix unmatched bracket in callout syntax.Line 177 has an unclosed bracket:
:::tip[Optimizing conteos de unidadesis missing the closing].Apply this diff:
-:::tip[Optimizing conteos de unidades +:::tip[Optimizing conteos de unidades]
191-197: Translate English callout title to Spanish.Line 191 contains an English callout title
:::important[How to choose]within a Spanish localization file, breaking language consistency.Apply this diff to translate:
-:::important[How to choose] +:::important[Cómo elegir]
331-335: Translate English text in callout block to Spanish.Lines 333–334 contain untranslated English text within a
:::tipblock in a Spanish localization file: "Always assign every physical drive from your original %%ZFS|zfs%% pool, including all support vdevs, when importing into Unraid..."Apply this diff to translate:
-Always assign every physical drive from your original %%ZFS|zfs%% pool, including all support vdevs, when importing into Unraid. This ensures smooth detection and integration. For new pools created in Unraid, support vdevs are optional and generally not needed for most users. +Asigna siempre cada disco físico de tu pool %%ZFS|zfs%% original, incluidos todos los vdevs de soporte, al importar en Unraid. Esto asegura una detección e integración sin problemas. Para nuevos pools creados en Unraid, los vdevs de soporte son opcionales y generalmente no se necesitan para la mayoría de usuarios.
🧹 Nitpick comments (1)
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx (1)
339-345: English term in Troubleshooting header—verify consistency.Line 340 has
:::info[Troubleshooting tipps]which uses English "Troubleshooting" with German "tipps" (which should be "Tipps" capitalized). Verify this is consistent with the document's terminology patterns, or consider using fully GermanFehlerbehebungs-Tipps.The term could be:
:::info[Fehlerbehebung-Tipps](fully German), or:::info[Troubleshooting-Tipps](consistent if English terms are preferred), or- Keep as-is if this matches Crowdin conventions.
Based on learnings, confirm current Crowdin setup expectations.
| 1. Installieren Sie das [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) Plugin aus den [Community Applications](../../unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx). | ||
| 2. Kein Unraid Connect Login erforderlich für lokalen API-Zugriff. | ||
| 3. Plugin-Einstellungen konfigurieren. | ||
| 4. Aktivieren Sie die %%GraphQL|graphql%% Sandbox. | ||
| 5. Beginne die API zu erkunden! |
There was a problem hiding this comment.
Resolve German formality inconsistency in step 5.
Lines 1–4 now use formal German imperative ("Installieren Sie", "Aktivieren Sie"), but line 5 uses informal second-person singular ("Beginne"). To maintain consistent tone throughout, consider updating line 5 to match:
-5. Beginne die API zu erkunden!
+5. Beginnen Sie die API zu erkunden!This aligns with the formality tone upgrade made in the earlier steps and maintains a consistent register for the audience.
🧰 Tools
🪛 LanguageTool
[grammar] ~1-~1: Ergänze ein Satzzeichen
Context: 1. Installiere das Unraid Connect Plugin aus den Community Apps 2....
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_UNRAIDDASHCONNECTDASHPLUGIN)
[grammar] ~1-~1: Ergänze ein Satzzeichen
Context: 1. Installiere das Unraid Connect Plugin aus den Community Apps 2. Kein Un...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_UNRAIDDASHCONNECTDASHPLUGIN)
[grammar] ~1-~1: Korrigiere die Fehler
Context: ... Unraid Connect Plugin aus den Community Apps 2. Kein Unraid Connect Login erford...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~2-~2: Ergänze ein Satzzeichen
Context: ...in aus den Community Apps 2. Kein Unraid Connect Login erforderlich für lokalen A...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_UNRAIDDASHCONNECTDASHLOGIN)
[grammar] ~2-~2: Ergänze ein Satzzeichen
Context: ...en Community Apps 2. Kein Unraid Connect Login erforderlich für lokalen API-Zugri...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_UNRAIDDASHCONNECTDASHLOGIN)
[grammar] ~2-~2: Ergänze ein Satzzeichen
Context: ...nnect Login erforderlich für lokalen API-Zugriff 3. Plugin-Einstellungen konfigurieren 4...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~3-~3: Ergänze ein Satzzeichen
Context: ...len API-Zugriff 3. Plugin-Einstellungen konfigurieren 4. Aktiviere die GraphQL-Sandbox 5. Beg...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[style] ~4-~4: Möchten Sie die modernere Schreibweise „GrafQL-Sandbox“ verwenden?
Context: ...ellungen konfigurieren 4. Aktiviere die GraphQL-Sandbox 5. Beginne die API zu erkunden!
(F_ANSTATT_PH)
[grammar] ~5-~5: Hier könnte ein Fehler sein.
Context: ...-Sandbox 5. Beginne die API zu erkunden!
(QB_NEW_DE)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/API/partials/get-started-pre72.mdx
around lines 1 to 5, step 5 uses informal German ("Beginne die API zu
erkunden!") while steps 1–4 use formal imperatives; change step 5 to a formal
imperative to match the rest, e.g., replace it with "Beginnen Sie, die API zu
erkunden!" or "Beginnen Sie mit dem Erkunden der API!" so the tone is
consistent.
| ## Kompression und RAM | ||
|
|
||
| %%ZFS|zfs%% bietet erweiterte Funktionen, die die Speichereffizienz und Leistung von Unraid erheblich verbessern können. Zwei gängige Interessensthemen sind Komprimierung und Speicheranforderungen. | ||
| When you import a %%ZFS|zfs%% pool into Unraid, you need to assign every drive from your original pool, including those used for support vdevs, to the pool slots. Unraid will automatically recognize each drive’s role (data, log, cache, special, or dedup) once the %%array|array%% starts. You don’t need to specify which drive serves what purpose manually. |
There was a problem hiding this comment.
Duplicate content: identical paragraph repeated about pool import process.
Lines 224 and 239 contain the same paragraph verbatim: "When you import a %%ZFS|zfs%% pool into Unraid, you need to assign every drive from your original pool, including those used for support vdevs, to the pool slots. Unraid will automatically recognize each drive's role (data, log, cache, special, or dedup) once the %%array|array%% starts. You don't need to specify which drive serves what purpose manually."
This appears in two different sections (Kompression und RAM / pool import tips) and may represent a copy-paste artifact or unintended duplication. Verify the intended placement and remove the redundancy if not intentional.
Consider consolidating this guidance into a single, well-placed section (e.g., in the dedicated "Importieren von auf anderen Systemen erstellten ZFS-Pools" section at line 263) rather than repeating it across multiple sections.
Also applies to: 239-239
🧰 Tools
🪛 LanguageTool
[grammar] ~224-~224: Hier könnte ein Fehler sein.
Context: ...rittene Benutzer könnten ihnen begegnen: ZFS-Kompression arbeitet transparent – s...
(QB_NEW_DE)
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
around lines 224 and 239: the exact same paragraph about importing a ZFS pool is
duplicated; remove the redundant copy and keep a single canonical instance
(preferably in the dedicated "Importieren von auf anderen Systemen erstellten
ZFS-Pools" section near line 263), update surrounding text to reference that
section if needed, and ensure any cross-references or anchors still work and the
translation/formatting remain consistent.
| Unraid 7.x führt eine Reihe leistungsstarker Erweiterungen für den **%%VM|vm%%-Manager** ein, die den Prozess des Ausführens und Verwalten von %%virtuellen Maschinen|vm%% vereinfachen. Diese Funktionen richten sich sowohl an Anfänger als auch an fortgeschrittene Benutzer und vereinfachen die Bereitstellung, Anpassung und Optimierung Ihrer %%VMs|vm%%. | ||
| Unraid 7.x führt eine Reihe leistungsstarker Verbesserungen für den **%%VM|vm%% Manager** ein, die den Prozess des Betriebs und Managements von %%VMs|vm%% vereinfachen. Diese Funktionen richten sich sowohl an Anfänger als auch an fortgeschrittene Benutzer und erleichtern das Einrichten, Anpassen und Optimieren Ihrer %%VMs|vm%%. | ||
|
|
||
| :::tip\[Highlights] |
There was a problem hiding this comment.
Remove unnecessary backslash escape in admonition.
Line 90 has an escaped bracket :::tip\[Highlights] that is inconsistent with other admonitions in the file. Remove the backslash.
-:::tip\[Highlights]
+:::tip[Highlights]📝 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\[Highlights] | |
| :::tip[Highlights] |
🧰 Tools
🪛 LanguageTool
[grammar] ~90-~90: Hier könnte ein Fehler sein.
Context: ...n Ihrer %%VMs|vm%%. :::tip[Highlights] - Sparen Sie Zeit mit %%VM|vm%%-Klone, Sna...
(QB_NEW_DE)
🤖 Prompt for AI Agents
In
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
around line 90, the admonition opener uses an unnecessary escape:
":::tip\[Highlights]"; remove the backslash so it matches other admonitions (use
":::tip[Highlights]") ensuring there are no stray escape characters and the
admonition renders correctly.
| ::: | ||
|
|
||
| ### Manuelle ROM-Injektion | ||
| ### Steckenbleiben in der UEFI-Shell |
There was a problem hiding this comment.
🧩 Analysis chain
Duplicate section header "Steckenbleiben in der UEFI-Shell".
The subsection "### Steckenbleiben in der UEFI-Shell" appears at both line 424 and line 503. This appears to be a document structure issue from reorganization. Review whether both sections should exist or if one should be removed/renamed.
Is this intentional duplication or a merge artifact from the Crowdin update?
Also applies to: 503-503
🏁 Script executed:
#!/bin/bash
# Verify the duplicate section header claim
# Check lines around 424 and 503
echo "=== Content around line 424 ==="
sed -n '420,430p' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
echo ""
echo "=== Content around line 503 ==="
sed -n '500,510p' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
echo ""
echo "=== Searching for all occurrences of 'Steckenbleiben in der UEFI-Shell' ==="
rg -n "Steckenbleiben in der UEFI-Shell" i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdxLength of output: 1228
Rename first section header at line 425 for clarity.
The header "### Steckenbleiben in der UEFI-Shell" appears at both lines 425 and 504, but the sections address different issues:
- Line 425: GPU ROM injection (provisioning ROM files for GPU passthrough)
- Line 504: UEFI shell boot problems (when VM boots to shell instead of OS)
The first section needs a distinct header such as "### GPU-ROM-Injection" or "### ROM-Datei einspeisen" to reflect its actual content and avoid reader confusion.
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
around line 424: the header "### Steckenbleiben in der UEFI-Shell" is duplicated
and the first occurrence (line ~425) actually covers GPU ROM injection; rename
that header to a distinct, accurate title such as "### GPU-ROM-Injektion" or
"### ROM-Datei einspeisen" (keep German localization style) to reflect GPU ROM
provisioning and avoid confusion with the later UEFI-shell boot problem section.
|
|
||
| ::: | ||
|
|
||
| :::info[Rebuild Zeit |
There was a problem hiding this comment.
MDX syntax error: Unclosed admonition bracket.
Line 196 opens an info admonition with :::info[Rebuild Zeit but the closing bracket is missing. Complete the label and close the bracket:
- :::info[Rebuild Zeit
+ :::info[Rebuild-Zeit]📝 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.
| :::info[Rebuild Zeit | |
| :::info[Rebuild-Zeit] |
🤖 Prompt for AI Agents
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
around line 196: the MDX admonition opening uses ":::info[Rebuild Zeit" but the
label is not closed; fix by completing and closing the bracket (e.g., change to
:::info[Rebuild Zeit] or the correct localized label) and ensure the admonition
block ends with a matching ::: delimiter so the admonition is properly formed.
| 1. Instala el plugin [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) desde [Aplicaciones Comunitarias](../../unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx). | ||
| 2. No se requiere login en Unraid Connect para acceso local a la API. | ||
| 3. Configure la configuración del plugin. | ||
| 4. Habilita el Sandbox %%GraphQL|graphql%%. | ||
| 5. ¡Comience a explorar la API! |
There was a problem hiding this comment.
Inconsistent imperative mood: Mix of formal and informal Spanish directives.
The steps use both informal imperative forms ("Instala", "Habilita") and formal imperative forms ("Configure", "Comience"). Official documentation should consistently use one style. Spanish documentation conventions typically favor formal imperative (usted form) for professionalism and clarity.
Recommendation: Standardize all imperative verbs to formal usted form:
-1. Instala el plugin [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) desde [Aplicaciones Comunitarias](../../unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx).
+1. Instale el plugin [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) desde [Aplicaciones Comunitarias](../../unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx).
2. No se requiere login en Unraid Connect para acceso local a la API.
3. Configure la configuración del plugin.
-4. Habilita el Sandbox %%GraphQL|graphql%%.
+4. Habilite el Sandbox %%GraphQL|graphql%%.
5. ¡Comience a explorar la API!🧰 Tools
🪛 LanguageTool
[grammar] ~4-~4: Aquí puede haber un error.
Context: ...onfiguración del plugin. 4. Habilita el Sandbox %%GraphQL|graphql%%. 5. ¡Comience a exp...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~4-~4: Aquí puede haber un error.
Context: ...Habilita el Sandbox %%GraphQL|graphql%%. 5. ¡Comience a explorar la API!
(QB_NEW_ES)
| 4. Habilitar el GraphQL Sandbox | ||
| 1. Instala el plugin [Unraid Connect](../../unraid-connect/overview-and-setup.mdx) desde [Aplicaciones Comunitarias](../../unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx). | ||
| 2. No se requiere login en Unraid Connect para acceso local a la API. | ||
| 3. Configure la configuración del plugin. |
There was a problem hiding this comment.
Revise redundant phrasing on Line 3.
"Configure la configuración" (literally "Configure the configuration") is awkward and circular. Recommend clearer phrasing:
-3. Configure la configuración del plugin.
+3. Configure los ajustes del plugin.Or alternatively:
-3. Configure la configuración del plugin.
+3. Configure el plugin.📝 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.
| 3. Configure la configuración del plugin. | |
| 3. Configure los ajustes del plugin. |
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/API/partials/get-started-pre72.mdx
around line 3, the phrase "Configure la configuración del plugin." is redundant
and awkward; replace it with a concise, non-redundant alternative such as
"Configurar el plugin" or the imperative "Configura el plugin" (choose one to
match the surrounding tone), ensuring surrounding punctuation and capitalization
remain consistent.
| :::tip | ||
| Antes de finalizar, revise las secciones sobre perfiles de asignación y topología para tomar una decisión informada. | ||
|
|
||
| Para añadir un disco %%ZFS|zfs%% al %%array|array%%: | ||
|
|
||
| ::: |
There was a problem hiding this comment.
🧩 Analysis chain
Incomplete tip section lacks substantive guidance.
The :::tip block at lines 106–110 contains only a heading ("Para añadir un disco...") with no actual tip content or guidance. Add relevant guidance inside the tip or remove the block if it's not needed.
Consider either:
- Expanding with actual tip content (e.g., steps, caveats, or best practices for adding a ZFS disk to the array)
- Removing the empty tip if the guidance is provided elsewhere
🏁 Script executed:
#!/bin/bash
# Examine the file and show context around lines 106-110
if [ -f "i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx" ]; then
echo "=== Context around lines 100-125 ==="
sed -n '100,125p' "i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx" | cat -n
else
echo "File not found, searching for similar filenames..."
find . -name "*zfs-storage*" -type f 2>/dev/null | head -20
fiLength of output: 1042
Incomplete tip section lacks substantive guidance.
The :::tip block at lines 106–110 contains only a heading ("Para añadir un disco...") with no actual tip content. Either expand with tip content (steps, caveats, or best practices for adding a ZFS disk) or remove the block.
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
around lines 106 to 110, the :::tip block contains only a heading and no
actionable content; either expand it with a concise tip (e.g., step-by-step
instructions or important caveats for adding a ZFS disk to an array, such as
preparing the disk, ensuring correct device naming, using zpool commands, and
backing up data) or remove the entire :::tip block; update the file by replacing
the empty tip with a short, practical paragraph or bullet list that provides the
recommended steps or delete the block if no guidance is needed.
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (1)
i18n/de/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx (1)
58-58: Critical: Fix missing closing bracket in admonition label.As flagged in the previous review, line 58 is missing the closing bracket for the admonition label. The current format
:::note[Server Kontext erforderlichis invalid; Docusaurus requires:::note[label]syntax.Apply this diff to fix the syntax error:
-:::note[Server Kontext erforderlich +:::note[Server Kontext erforderlich]Without the closing bracket, the admonition will fail to parse correctly in Docusaurus, potentially causing rendering issues.
🧹 Nitpick comments (1)
i18n/de/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx (1)
6-10: Consider translating info box label to German.The admonition label at line 6 ("Prerequisite") is in English while the rest of the German documentation uses German text. For full localization consistency, this should be translated to German (e.g., "Voraussetzung").
Apply this diff to align with the rest of the German documentation:
-:::info\[Prerequisite] +:::info\[Voraussetzung]
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
i18n/de/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx(1 hunks)i18n/es/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: elibosley
Repo: unraid/docs PR: 321
File: crowdin.yml:10-11
Timestamp: 2025-09-16T15:34:45.481Z
Learning: In the unraid/docs repository, the Crowdin configuration uses a broad `/docs/**/*` source pattern and relies on overriding the v1 parser to use the v2 parser at the Crowdin project settings level, rather than specifying `type: mdx_v2` in crowdin.yml.
Learnt from: elibosley
Repo: unraid/docs PR: 339
File: src/components/ManualKeyfileTabs.tsx:9-14
Timestamp: 2025-09-28T04:48:08.800Z
Learning: The user is using Crowdin 3.x and indicates that wrapping TabItem labels with translate() may not be necessary with their current setup, suggesting Crowdin 3.x handles string extraction differently than earlier versions. I should verify current behavior rather than assume traditional Docusaurus practices apply to their specific configuration.
Learnt from: elibosley
Repo: unraid/docs PR: 339
File: docs/unraid-os/getting-started/what-is-unraid.mdx:64-80
Timestamp: 2025-09-28T04:47:45.534Z
Learning: In Docusaurus MDX files, `mdx-code-block` is not a literal code block but an escape hatch for Crowdin translation integration. It's a no-op wrapper that allows complex JSX to be preserved during Crowdin upload/download cycles while still rendering normally. Docusaurus includes special handling that unwraps these blocks so the JSX content renders as intended.
📚 Learning: 2025-09-28T04:47:45.534Z
Learnt from: elibosley
Repo: unraid/docs PR: 339
File: docs/unraid-os/getting-started/what-is-unraid.mdx:64-80
Timestamp: 2025-09-28T04:47:45.534Z
Learning: In Docusaurus MDX files, `mdx-code-block` is not a literal code block but an escape hatch for Crowdin translation integration. It's a no-op wrapper that allows complex JSX to be preserved during Crowdin upload/download cycles while still rendering normally. Docusaurus includes special handling that unwraps these blocks so the JSX content renders as intended.
Applied to files:
i18n/es/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
🪛 LanguageTool
i18n/es/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
[grammar] ~6-~6: Aquí puede haber un error.
Context: ...ia de Unraid --- :::info[Prerequisite] Un mínimo de Unraid OS v6.10 o posterior...
(QB_NEW_ES)
[grammar] ~8-~8: Aquí puede haber un error.
Context: ...o acceso a su panel de cuenta de Unraid. ::: ## Cómo Canjear su Código de Activ...
(QB_NEW_ES)
[grammar] ~12-~12: Aquí puede haber un error.
Context: ...anel de cuenta de Unraid. ::: ## Cómo Canjear su Código de Activación Primero, sigue...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~12-~12: Aquí puede haber un error.
Context: ...nta de Unraid. ::: ## Cómo Canjear su Código de Activación Primero, sigue nuestra [...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~12-~12: Aquí puede haber un error.
Context: ...aid. ::: ## Cómo Canjear su Código de Activación Primero, sigue nuestra [guía de introduc...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~14-~14: Aquí puede haber un error.
Context: ...mdx) para configurar un servidor Unraid. Cuando tu servidor esté en funcionamien...
(QB_NEW_ES)
[grammar] ~18-~18: Aquí puede haber un error.
Context: ...entes: ### Para Unraid 6.10 o posterior 1. Inicie sesión en el WebGUI de su servido...
(QB_NEW_ES)
[grammar] ~24-~24: Aquí puede haber un error.
Context: ...pra y complete el proceso de activación. ### Para Códigos de Activación de Actualizac...
(QB_NEW_ES)
[grammar] ~26-~26: Aquí puede haber un error.
Context: ...ete el proceso de activación. ### Para Códigos de Activación de Actualización 1. Inic...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~26-~26: Aquí puede haber un error.
Context: ...eso de activación. ### Para Códigos de Activación de Actualización 1. Inicie sesión en e...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~26-~26: Aquí puede haber un error.
Context: ...ión. ### Para Códigos de Activación de Actualización 1. Inicie sesión en el WebGUI de su servido...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~28-~28: Aquí puede haber un error.
Context: ...sión en el WebGUI de su servidor Unraid. 2. Elija "Actualizar Clave" del menú desple...
(QB_NEW_ES)
[grammar] ~30-~30: Aquí puede haber un error.
Context: ... servidor Unraid. 2. Elija "Actualizar Clave" del menú desplegable en la parte superi...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~30-~30: Aquí puede haber un error.
Context: ...en la parte superior derecha del WebGUI. 3. Desplácese hacia abajo para encontrar l...
(QB_NEW_ES)
[grammar] ~34-~34: Aquí puede haber un error.
Context: ... de activación para activar su licencia. ### Para Unraid 6.9 y anteriores 1. Navegue...
(QB_NEW_ES)
[grammar] ~36-~36: Aquí puede haber un error.
Context: ...encia. ### Para Unraid 6.9 y anteriores 1. Navegue a Herramientas → Registro en...
(QB_NEW_ES)
[grammar] ~38-~38: Aquí puede haber un error.
Context: ...Herramientas → Registro* en el WebGUI. 2. Haga clic en "Comprar Clave". 3. Ingres...
(QB_NEW_ES)
[grammar] ~40-~40: Aquí puede haber un error.
Context: ...en el WebGUI. 2. Haga clic en "Comprar Clave". 3. Ingrese el código de activación qu...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~40-~40: Aquí puede haber un error.
Context: ...ebGUI. 2. Haga clic en "Comprar Clave". 3. Ingrese el código de activación que fig...
(QB_NEW_ES)
[grammar] ~42-~42: Aquí puede haber un error.
Context: ...ido y complete el proceso de activación. ## Alternativa: Canjear a través del Tabler...
(QB_NEW_ES)
[grammar] ~44-~44: Aquí puede haber un error.
Context: ...: Canjear a través del Tablero de Cuenta También puede canjear su código de activ...
(QB_NEW_ES)
[grammar] ~48-~48: Aquí puede haber un error.
Context: ...d.net desde la esquina superior derecha. 2. Haga clic en la esquina superior derecha...
(QB_NEW_ES)
[grammar] ~50-~50: Aquí puede haber un error.
Context: ... con el contexto de su servidor cargado. 3. En la aplicación de cuentas, verá la pá...
(QB_NEW_ES)
[grammar] ~54-~54: Aquí puede haber un error.
Context: ...eo electrónico o confirmación de compra. 4. Haga clic en "Canjear Código" para c...
(QB_NEW_ES)
[grammar] ~56-~56: Aquí puede haber un error.
Context: ...su licencia se instalará en el servidor. :::note[Server Context Required] Si no ...
(QB_NEW_ES)
[grammar] ~58-~58: Aquí puede haber un error.
Context: ...vidor. :::note[Server Context Required] Si no ve el formulario de canje, es posi...
(QB_NEW_ES)
[grammar] ~60-~60: Aquí puede haber un error.
Context: ...u servidor. Haga clic en "Administrar Servidor" para conectar su servidor a la aplica...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~60-~60: Aquí puede haber un error.
Context: ... su servidor a la aplicación de cuentas. ::: ## Notas Importantes - Los código...
(QB_NEW_ES)
[grammar] ~64-~64: Aquí puede haber un error.
Context: ...a aplicación de cuentas. ::: ## Notas Importantes - Los códigos de activación son de un solo...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~74-~74: Aquí puede haber un error.
Context: ...o exactamente como aparece en su correo electrónico - Verifique que el código de activación...
(QB_NEW_ES_OTHER_ERROR_IDS_MISSING_PUNCTUATION)
[grammar] ~75-~75: Aquí puede haber un error.
Context: ...digo de activación no se haya utilizado ya - Asegúrese de haber iniciado sesión co...
(QB_NEW_ES_OTHER_ERROR_IDS_MISSING_PUNCTUATION)
[grammar] ~76-~76: Aquí puede haber un error.
Context: ...esión con la misma cuenta que compró la licencia - Verifique que el contexto de su servi...
(QB_NEW_ES_OTHER_ERROR_IDS_MISSING_PUNCTUATION)
[grammar] ~77-~77: Aquí puede haber un error.
Context: ...e el contexto de su servidor se detecte correctamente - Consulta nuestro [Licensing FAQ](../u...
(QB_NEW_ES_OTHER_ERROR_IDS_MISSING_PUNCTUATION)
[grammar] ~78-~78: Aquí puede haber un error.
Context: .../licensing-faq.mdx) para más información
(QB_NEW_ES)
i18n/de/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
[grammar] ~1-~1: Hier könnte ein Fehler sein.
Context: --- title: Aktivierungscode einlösen description: So lösen Sie Ihren Aktivierungscode ein, um Ihre Unraid-Lizenz zu installieren --- :::info[Prerequisite] Mindestens Unrai...
(QB_NEW_DE)
[grammar] ~6-~6: Ergänze ein Leerzeichen
Context: ...raid-Lizenz zu installieren --- :::info[Prerequisite] Mindestens Unraid OS v6....
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)
[grammar] ~6-~6: Hier könnte ein Fehler sein.
Context: ...installieren --- :::info[Prerequisite] Mindestens Unraid OS v6.10 oder höher od...
(QB_NEW_DE)
[grammar] ~8-~8: Hier könnte ein Fehler sein.
Context: ... Zugriff auf Ihr Unraid-Konto-Dashboard. ::: ## Wie Sie Ihren Aktivierungscode e...
(QB_NEW_DE)
[grammar] ~10-~10: Hier könnte ein Fehler sein.
Context: ...iff auf Ihr Unraid-Konto-Dashboard. ::: ## Wie Sie Ihren Aktivierungscode einlösen ...
(QB_NEW_DE)
[grammar] ~12-~12: Hier könnte ein Fehler sein.
Context: ... Wie Sie Ihren Aktivierungscode einlösen Zuerst, folgen Sie unserem [Getting Star...
(QB_NEW_DE)
[grammar] ~14-~14: Entferne ein Leerzeichen
Context: ...sen Zuerst, folgen Sie unserem [Getting Started guide](../unraid-os/getting-star...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~14-~14: Entferne ein Leerzeichen
Context: ...rst, folgen Sie unserem [Getting Started guide](../unraid-os/getting-started/what-is-u...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~14-~14: Hier könnte ein Fehler sein.
Context: ...x), um einen Unraid-Server einzurichten. Wenn Ihr Server läuft, lauten die Anweis...
(QB_NEW_DE)
[grammar] ~16-~16: Hier könnte ein Fehler sein.
Context: ... zur Aktivierung Ihrer Lizenz wie folgt: ### Für Unraid 6.10 oder später 1. Melden S...
(QB_NEW_DE)
[grammar] ~18-~18: Hier könnte ein Fehler sein.
Context: ... folgt: ### Für Unraid 6.10 oder später 1. Melden Sie sich an der WebGUI (http://to...
(QB_NEW_DE)
[grammar] ~20-~20: Hier könnte ein Fehler sein.
Context: ... standardmäßig) Ihres Unraid-Servers an. 2. Melden Sie sich von rechts oben in der W...
(QB_NEW_DE)
[grammar] ~22-~22: Ersetze das Satzzeichen
Context: ...oder erstellen Sie eins) und wählen Sie "Aktivierungscode einlösen". 3. Geben Sie den Aktivierun...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~22-~22: Ersetze das Satzzeichen
Context: ... eins) und wählen Sie "Aktivierungscode einlösen". 3. Geben Sie den Aktivierungscode aus...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~22-~22: Hier könnte ein Fehler sein.
Context: ... wählen Sie "Aktivierungscode einlösen". 3. Geben Sie den Aktivierungscode aus Ihrer...
(QB_NEW_DE)
[grammar] ~24-~24: Hier könnte ein Fehler sein.
Context: ...chließen Sie den Aktivierungsprozess ab. ### Für Upgrade-Aktivierungscodes 1. Melden...
(QB_NEW_DE)
[grammar] ~26-~26: Hier könnte ein Fehler sein.
Context: ...s ab. ### Für Upgrade-Aktivierungscodes 1. Melden Sie sich an der WebGUI Ihres Unra...
(QB_NEW_DE)
[grammar] ~28-~28: Hier könnte ein Fehler sein.
Context: ...h an der WebGUI Ihres Unraid-Servers an. 2. Wählen Sie "Schlüssel aktualisieren" aus...
(QB_NEW_DE)
[grammar] ~30-~30: Ersetze das Satzzeichen
Context: ...Ihres Unraid-Servers an. 2. Wählen Sie "Schlüssel aktualisieren" aus dem Dropdown-Menü ob...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~30-~30: Ersetze das Satzzeichen
Context: ...d-Servers an. 2. Wählen Sie "Schlüssel aktualisieren" aus dem Dropdown-Menü oben rechts in de...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~30-~30: Hier könnte ein Fehler sein.
Context: ...Dropdown-Menü oben rechts in der WebGUI. 3. Scrollen Sie nach unten, um das Eingabef...
(QB_NEW_DE)
[grammar] ~32-~32: Ersetze das Satzzeichen
Context: ...llen Sie nach unten, um das Eingabefeld "Aktivierungscode für Upgrade einlösen" zu finden. 4. Ge...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~32-~32: Ersetze das Satzzeichen
Context: ...ngabefeld "Aktivierungscode für Upgrade einlösen" zu finden. 4. Geben Sie den Aktivierun...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~32-~32: Hier könnte ein Fehler sein.
Context: ...ngscode für Upgrade einlösen" zu finden. 4. Geben Sie den Aktivierungscode ein, um I...
(QB_NEW_DE)
[grammar] ~34-~34: Hier könnte ein Fehler sein.
Context: ...scode ein, um Ihre Lizenz zu aktivieren. ### Für Unraid 6.9 und früher 1. Navigieren...
(QB_NEW_DE)
[grammar] ~36-~36: Hier könnte ein Fehler sein.
Context: ...tivieren. ### Für Unraid 6.9 und früher 1. Navigieren Sie zu **Tools → Registrierun...
(QB_NEW_DE)
[grammar] ~38-~38: Hier könnte ein Fehler sein.
Context: ...Tools → Registrierung* auf der WebGUI. 2. Klicken Sie auf "Schlüssel kaufen". 3. ...
(QB_NEW_DE)
[grammar] ~40-~40: Ersetze das Satzzeichen
Context: ...g** auf der WebGUI. 2. Klicken Sie auf "Schlüssel kaufen". 3. Geben Sie den Aktivierungs...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~40-~40: Ersetze das Satzzeichen
Context: ... WebGUI. 2. Klicken Sie auf "Schlüssel kaufen". 3. Geben Sie den Aktivierungscode auf...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~40-~40: Hier könnte ein Fehler sein.
Context: ... 2. Klicken Sie auf "Schlüssel kaufen". 3. Geben Sie den Aktivierungscode auf Ihrer...
(QB_NEW_DE)
[grammar] ~42-~42: Hier könnte ein Fehler sein.
Context: ...chließen Sie den Aktivierungsprozess ab. ## Alternative: Einlösen über das Kontodash...
(QB_NEW_DE)
[grammar] ~44-~44: Hier könnte ein Fehler sein.
Context: ...native: Einlösen über das Kontodashboard Sie können Ihren Aktivierungscode auch ü...
(QB_NEW_DE)
[grammar] ~46-~46: Hier könnte ein Fehler sein.
Context: ... Dashboard Ihres Unraid-Kontos einlösen: 1. Navigieren Sie zur WebGUI Ihres Unraid-S...
(QB_NEW_DE)
[grammar] ~48-~48: Hier könnte ein Fehler sein.
Context: ... Ihrem Unraid.net-Konto angemeldet sind. 2. Klicken Sie auf die rechte obere Ecke de...
(QB_NEW_DE)
[grammar] ~50-~50: Ersetze das Satzzeichen
Context: ... obere Ecke der WebGUI und wählen Sie "Aktivierungscode einlösen" oder **"Lizenz aktualisiere...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~50-~50: Ersetze das Satzzeichen
Context: ...bGUI und wählen Sie "Aktivierungscode einlösen" oder "Lizenz aktualisieren", um d...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~50-~50: Ersetze das Satzzeichen
Context: ... "Aktivierungscode einlösen" oder "Lizenz aktualisieren", um das Kontodashboard...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~50-~50: Ersetze das Satzzeichen
Context: ...vierungscode einlösen"** oder "Lizenz aktualisieren", um das Kontodashboard mit Ihrem Serv...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~50-~50: Hier könnte ein Fehler sein.
Context: ...board mit Ihrem Serverkontext zu öffnen. 3. In der Kontoanwendung sehen Sie die Seit...
(QB_NEW_DE)
[grammar] ~52-~52: Ersetze das Satzzeichen
Context: ... der Kontoanwendung sehen Sie die Seite "Aktivierungscode einlösen". Hier haben Sie zwei Möglichk...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~52-~52: Ersetze das Satzzeichen
Context: ...g sehen Sie die Seite "Aktivierungscode einlösen". Hier haben Sie zwei Möglichkeiten: ...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~53-~53: Entferne ein Wort
Context: ...lichkeiten: - Wählen Sie aus Ihren Codes: Wenn Sie berechtigte Aktivierungscodes ...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_NOUN)
[grammar] ~53-~53: Hier könnte ein Fehler sein.
Context: ...tät Ihres Servers automatisch gefiltert. - Code manuell eingeben: Klicken Sie auf...
(QB_NEW_DE)
[grammar] ~54-~54: Entferne ein Wort
Context: ...omatisch gefiltert. - Code manuell eingeben: Klicken Sie auf "Code stattdessen einge...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_NOUN)
[grammar] ~54-~54: Ersetze das Satzzeichen
Context: ...ode manuell eingeben**: Klicken Sie auf "Code stattdessen eingeben" (oder verwenden S...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~54-~54: Ersetze das Satzzeichen
Context: ...en**: Klicken Sie auf "Code stattdessen eingeben" (oder verwenden Sie die manuelle Eingab...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~54-~54: Hier könnte ein Fehler sein.
Context: ...ail oder Kaufbestätigung angezeigt wird. 4. Klicken Sie auf "Code einlösen", um ...
(QB_NEW_DE)
[grammar] ~56-~56: Ersetze das Satzzeichen
Context: ...g angezeigt wird. 4. Klicken Sie auf "Code einlösen", um den Aktivierungsprozess...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~56-~56: Ersetze das Satzzeichen
Context: ...zeigt wird. 4. Klicken Sie auf "Code einlösen", um den Aktivierungsprozess abzuschli...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~56-~56: Hier könnte ein Fehler sein.
Context: ... Ihre Lizenz auf dem Server installiert. :::note[Server Kontext erforderlich Wen...
(QB_NEW_DE)
[typographical] ~58-~58: Zeichen ohne sein Gegenstück: ‚]‘ scheint zu fehlen
Context: ...enz auf dem Server installiert. :::note[Server Kontext erforderlich Wenn Sie da...
(UNPAIRED_BRACKETS)
[grammar] ~58-~58: Hier könnte ein Fehler sein.
Context: ...rt. :::note[Server Kontext erforderlich Wenn Sie das Einlösungsformular nicht se...
(QB_NEW_DE)
[grammar] ~60-~60: Ersetze das Satzzeichen
Context: ... Serverkontext laden. Klicken Sie auf "Server verwalten", um Ihren Server mit der K...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)
[grammar] ~60-~60: Ersetze das Satzzeichen
Context: ...ontext laden. Klicken Sie auf "Server verwalten", um Ihren Server mit der Kontoanwendu...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_L_DOUBLE_QUOT)
[grammar] ~60-~60: Hier könnte ein Fehler sein.
Context: ...ver mit der Kontoanwendung zu verbinden. ::: ## Wichtige Hinweise - Aktivierung...
(QB_NEW_DE)
[grammar] ~62-~62: Hier könnte ein Fehler sein.
Context: ...it der Kontoanwendung zu verbinden. ::: ## Wichtige Hinweise - Aktivierungscodes s...
(QB_NEW_DE)
[grammar] ~64-~64: Hier könnte ein Fehler sein.
Context: ...zu verbinden. ::: ## Wichtige Hinweise - Aktivierungscodes sind nur einmal verwen...
(QB_NEW_DE)
[grammar] ~66-~66: Hier könnte ein Fehler sein.
Context: ...seldatei für Ihren Server zu generieren. - Stellen Sie sicher, dass Sie mit demselb...
(QB_NEW_DE)
[grammar] ~67-~67: Hier könnte ein Fehler sein.
Context: ...meldet sind, das die Lizenz gekauft hat. - Der Aktivierungscode muss mit dem Server...
(QB_NEW_DE)
[grammar] ~68-~68: Hier könnte ein Fehler sein.
Context: ...reinstimmen, den Sie aktivieren möchten. ## Brauchst du Hilfe? Wenn Sie Probleme be...
(QB_NEW_DE)
[grammar] ~70-~70: Hier könnte ein Fehler sein.
Context: ...tivieren möchten. ## Brauchst du Hilfe? Wenn Sie Probleme beim Einlösen Ihres Ak...
(QB_NEW_DE)
[grammar] ~72-~72: Hier könnte ein Fehler sein.
Context: ... Einlösen Ihres Aktivierungscodes haben: - Stellen Sie sicher, dass Sie den Code ge...
(QB_NEW_DE)
[grammar] ~74-~74: Ergänze ein Satzzeichen
Context: ...geben, wie er in Ihrer E-Mail angezeigt wird - Überprüfen Sie, ob der Aktivierungsco...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~75-~75: Ergänze ein Satzzeichen
Context: ... der Aktivierungscode bereits verwendet wurde - Stellen Sie sicher, dass Sie mit dems...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~76-~76: Ergänze ein Satzzeichen
Context: ...angemeldet sind, das die Lizenz gekauft hat - Überprüfen Sie, ob Ihr Serverkontext ...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~77-~77: Ergänze ein Satzzeichen
Context: ...e, ob Ihr Serverkontext korrekt erkannt wird - Siehe unsere [Licensing FAQ](../unrai...
(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_PERIOD)
[grammar] ~78-~78: Hier könnte ein Fehler sein.
Context: ...nsing-faq.mdx) für weitere Informationen
(QB_NEW_DE)
| :::info\[Prerequisite] | ||
|
|
||
| Un mínimo de Unraid OS v6.10 o posterior, o acceso a su panel de cuenta de Unraid. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Translate admonition label to Spanish.
The info box label at line 6 ("Prerequisite") is in English while the documentation is in Spanish. This should be translated for consistency across the localized page.
Apply this diff to translate the label:
-:::info\[Prerequisite]
+:::info\[Requisito previo]📝 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.
| :::info\[Prerequisite] | |
| Un mínimo de Unraid OS v6.10 o posterior, o acceso a su panel de cuenta de Unraid. | |
| ::: | |
| :::info\[Requisito previo] | |
| Un mínimo de Unraid OS v6.10 o posterior, o acceso a su panel de cuenta de Unraid. | |
| ::: |
🧰 Tools
🪛 LanguageTool
[grammar] ~6-~6: Aquí puede haber un error.
Context: ...ia de Unraid --- :::info[Prerequisite] Un mínimo de Unraid OS v6.10 o posterior...
(QB_NEW_ES)
[grammar] ~8-~8: Aquí puede haber un error.
Context: ...o acceso a su panel de cuenta de Unraid. ::: ## Cómo Canjear su Código de Activ...
(QB_NEW_ES)
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
around lines 6 to 10, the admonition label "Prerequisite" is in English; update
the admonition opening to use the Spanish label (e.g., "Requisito" or "Requisito
previo") so the info box matches the Spanish content, keeping the rest of the
admonition syntax and content unchanged.
| :::note[Server Context Required] | ||
|
|
||
| Si no ve el formulario de canje, es posible que deba cargar primero el contexto de su servidor. Haga clic en **"Administrar Servidor"** para conectar su servidor a la aplicación de cuentas. | ||
|
|
||
| ::: |
There was a problem hiding this comment.
Translate admonition label to Spanish for consistency.
The note label at line 58 is in English ("Server Context Required") while the rest of the document is in Spanish. This creates inconsistency in the localized documentation.
Apply this diff to translate the label:
-:::note[Server Context Required]
+:::note[Se requiere contexto del servidor]📝 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.
| :::note[Server Context Required] | |
| Si no ve el formulario de canje, es posible que deba cargar primero el contexto de su servidor. Haga clic en **"Administrar Servidor"** para conectar su servidor a la aplicación de cuentas. | |
| ::: | |
| :::note[Se requiere contexto del servidor] | |
| Si no ve el formulario de canje, es posible que deba cargar primero el contexto de su servidor. Haga clic en **"Administrar Servidor"** para conectar su servidor a la aplicación de cuentas. | |
| ::: |
🧰 Tools
🪛 LanguageTool
[grammar] ~58-~58: Aquí puede haber un error.
Context: ...vidor. :::note[Server Context Required] Si no ve el formulario de canje, es posi...
(QB_NEW_ES)
[grammar] ~60-~60: Aquí puede haber un error.
Context: ...u servidor. Haga clic en "Administrar Servidor" para conectar su servidor a la aplica...
(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
[grammar] ~60-~60: Aquí puede haber un error.
Context: ... su servidor a la aplicación de cuentas. ::: ## Notas Importantes - Los código...
(QB_NEW_ES)
🤖 Prompt for AI Agents
In
i18n/es/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
around lines 58 to 62, the admonition label "Server Context Required" is still
in English; replace it with a Spanish label (e.g., "Contexto del servidor
requerido" or "Se requiere contexto del servidor") so the note matches the rest
of the Spanish content, keeping the admonition syntax and inner Spanish text
unchanged.
Summary by CodeRabbit
Documentation
Localization