Conversation
📝 WalkthroughWalkthroughThis pull request updates the Unraid documentation across multiple languages (German, Spanish, French, Chinese) with a comprehensive shift from "flash device" terminology to "boot device," adds new documentation pages for billing address management and internal boot FAQs, introduces two new Docusaurus 7.3.0 beta and 7.2.4 release notes, and includes various formatting refinements including Docusaurus anchor ID additions to section headings, JSX/HTML style attribute standardization, and component imports for shared UI labeling. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 25
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
🧹 Nitpick comments (24)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx (2)
34-34: Polish phrasing for Spanish style consistency.Line 34 can be simplified stylistically (e.g., avoid repeating
-menteadverbs in sequence) for smoother reading.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx` at line 34, The sentence "Para mayor comodidad, puedes programar estas comprobaciones para que se ejecuten automáticamente en los intervalos que mejor te convengan navegando a ***Settings → Scheduler***. Es recomendable realizar comprobaciones automáticas y correctivas mensualmente o trimestralmente..." (the line starting with "Para mayor comodidad...") is stylistically repetitive with consecutive -mente adverbs; rephrase it to improve flow by removing redundancy and tightening structure — e.g., consolidate the scheduling instruction and the recommendation into one smoother sentence such as: "Para mayor comodidad, programa estas comprobaciones en Settings → Scheduler; se recomienda ejecutarlas automáticamente cada mes o cada trimestre para garantizar la salud continua de los datos y corregir errores de sincronización." Replace the original sentence with this or a similar compact formulation.
48-48: Make the history-file location fully actionable.Line 48 says logs are in the
configdirectory, but omits the exact filename/path. Adding the concrete path/file would improve troubleshooting clarity.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx` at line 48, Replace the vague sentence that says logs are in the `config` directory with a concrete, actionable path and filename — edit the line in array-health-and-maintenance.mdx that begins "Para quienes quieran profundizar más..." to include the full path to the history/log file (for example, /boot/config/disk.log) so readers can open the exact file directly; keep the rest of the wording but append the filename and, optionally, a one‑phrase hint on how to view it (e.g., "ábralo con un editor de texto").i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx (1)
68-68: Consider consistent formatting for closing tags.Blank lines have been added before several
</details>closing tags. While not harmful, this may create inconsistency if applied selectively. Consider either applying this formatting pattern consistently throughout the file or removing these blank lines to match the typical compact closing tag style.Also applies to: 98-98, 110-110, 133-133
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx` at line 68, The file has inconsistent blank lines immediately before several closing details tags (</details>), which breaks uniform formatting; update the occurrences of the closing tag (</details>) so they follow a consistent style—either remove the extra blank line(s) before each </details> to match the compact style used elsewhere or add the blank line consistently across all details blocks; locate all instances of the </details> tag (including the instances noted around the current changes) and normalize them across the document.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (1)
273-344:pingsubsection appears twice with conflicting labeling.Line 273 and Line 328 both define
### ping, and the second block summary at Line 333 says “Voir les options ss”. Consider merging/fixing these subsections so heading, summary, and command examples are consistent.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx` around lines 273 - 344, There are two duplicate headings "### `ping`" (with summaries "<strong>Voir l'utilisation de ping</strong>" and "<strong>Voir les options ss</strong>") and mixed examples (commands `ss -tuln`, `ss -tup` and `ping -c 4 google.com`); remove the duplicate ping subsection and merge into a single "### `ping`" block that contains the ping example (`ping -c 4 google.com`) under a matching summary like "Voir l'utilisation de ping", and move or restore the `ss` examples (`ss -tuln`, `ss -tup`) to an appropriate "ss" or networking tools subsection (or change the second summary to reference ping if you prefer keeping both examples together) so headings, summaries, and command examples are consistent.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx (1)
10-10: Optional French style refinements suggested by static analysis.LanguageTool suggests two minor style improvements for this line:
- "mis à jour" could potentially be replaced with a more precise/impactful alternative
- "se chargent en même temps que" could use a more direct structure
These are stylistic suggestions that could enhance readability but don't affect correctness or functionality.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx` at line 10, Refine the French phrasing in the sentence starting "Unraid s'installe sur une clé USB..." by replacing "pilotes matériels mis à jour" with a tighter alternative like "pilotes matériels récents" or "pilotes matériels à jour", and simplify "se chargent en même temps que le système d'exploitation" to a more direct form such as "se chargent avec le système d'exploitation" or "se chargent au démarrage" to improve readability while preserving meaning.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx (1)
56-65: Remove duplicated “Risiken der Übertaktung” headings.Lines 56 and 64 repeat the same heading, making the section noisy. Keep a single heading.
Proposed cleanup
-**Risiken der Übertaktung:** - :::caution[RAM Übertaktungsrisiken und Empfehlungen] @@ -**Risiken der Übertaktung:** -🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx` around lines 56 - 65, Remove the duplicated "Risiken der Übertaktung" heading in the MDX section so only one instance remains; locate the repeated heading string "Risiken der Übertaktung" in the content around the RAM/XMP/AMP caution block and delete the extra occurrence (ensure surrounding text and admonition block :::caution remain intact and spacing/newlines are correct).i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
11-11: Mixed language in callout header.The callout header mixes English ("Special") with German ("Hinweis"). For a German localization, this should be fully translated, e.g.,
:::important[Spezieller Hinweis]or:::important[Wichtiger Hinweis].🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx` at line 11, The callout header uses mixed English and German ("Special Hinweis"); update the callout label in the MDX callout token `:::important[Special Hinweis]` to a fully German phrase such as `:::important[Wichtiger Hinweis]` (or `:::important[Spezieller Hinweis]`) so the header is fully localized.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx (2)
488-492: Admonition syntax: add space after type identifier.Docusaurus admonitions work better with a space or newline after
:::note. While it may still render, the standard pattern is:::notefollowed by a newline, then content.✨ Consistent formatting
-:::note - -Vous ne pouvez pas réduire un %%vDisk|vdisk%% depuis l'interface Unraid ; seule l'expansion est prise en charge. +:::note +Vous ne pouvez pas réduire un %%vDisk|vdisk%% depuis l'interface Unraid ; seule l'expansion est prise en charge. + :::🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx` around lines 488 - 492, The admonition header `:::note` in the VM setup doc should be followed by a space or newline before the content to match Docusaurus syntax; update the admonition block that currently reads `:::note` immediately followed by the French sentence so there is a blank line (or at least a single newline) between `:::note` and the content line "Vous ne pouvez pas réduire un %%vDisk|vdisk%% ..." to ensure correct rendering and consistent formatting.
104-104: Minor: Missing accent on "Edition"."Edition" should be "Édition" in French (with the accent aigu on the É).
✏️ Fix
-- **Edition/visualisation XML en ligne :** Visualisez ou copiez instantanément le `XML` généré par le %%WebGUI|web-gui%% ; passez en mode `XML` pour des éditions avancées. +- **Édition/visualisation XML en ligne :** Visualisez ou copiez instantanément le `XML` généré par le %%WebGUI|web-gui%% ; passez en mode `XML` pour des éditions avancées.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx` at line 104, Update the French text fragment that currently reads "**Edition/visualisation XML en ligne :** Visualisez ou copiez instantanément le `XML` généré par le %%WebGUI|web-gui%% ; passez en mode `XML` pour des éditions avancées." to use the correct accented form "**Édition/visualisation XML en ligne :** …". Locate the string in the VM setup doc (the line containing "Edition/visualisation XML en ligne") and replace "Edition" with "Édition" to correct the accent.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
479-482: Line 481 repeats earlier content; make the tip actionable.The tip currently duplicates the paragraph from Line 469 rather than adding planning guidance.
Suggested replacement for the tip body
- %%ZFS|zfs%% es poderoso, pero es importante entender cómo funciona su expansión de almacenamiento - especialmente si estás planificando un crecimiento futuro. + Planifica el crecimiento por vdev desde el inicio: define de antemano cuántos discos añadirás por expansión para evitar rediseños costosos del pool.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx` around lines 479 - 482, The tip block titled ":::tip[Planning adelante]" currently duplicates the earlier paragraph using the token "%%ZFS|zfs%%"; replace its body with actionable planning guidance: explain specific steps to plan ZFS growth (estimate future capacity, choose pool layout and vdev types, leave spare disks for resilvering, consider RAID-Z expansion constraints, and schedule regular scrubs), mention when to add capacity vs rebuild pools, and keep the "%%ZFS|zfs%%" reference intact so localization tokens remain correct.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (1)
395-397: Consolidate duplicated troubleshooting sections
## Fehlerbehebungand### Überprüfen eines Dateisystemsare duplicated with overlapping content. This increases drift risk and makes navigation harder.Also applies to: 431-434, 483-485
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx` around lines 395 - 397, Consolidate the duplicated troubleshooting content by keeping a single "## Fehlerbehebung" section and one canonical "### Überprüfen eines Dateisystems" subsection: merge overlapping paragraphs about unassigned drives, their uses (transfer files, backups, fast storage for VMs), and any step-by-step checks into the canonical subsection, remove the duplicate blocks that repeat the same text, and ensure all internal references (%%array|array%%, %%cache pool|cache-pool%%, %%virtual machines|vm%%) are preserved; apply the same consolidation to the other duplicated occurrences of these headings so only one authoritative troubleshooting and filesystem-check section remains.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx (1)
246-247: Start the TPM procedure at the first real action.These two steps repeat the prerequisite checklist from the callout above, so the numbered flow does not actually begin until the BIOS change on Line 248. I’d drop the duplicates and start the procedure there instead.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx` around lines 246 - 247, Remove the duplicated prerequisite steps "1. Erstellen Sie eine vollständige Sicherung Ihrer %%VM|vm%%." and "2. Stellen Sie sicher, dass Unraid Version 6.10 oder später ausgeführt wird." from the numbered procedure and start the numbered procedure at the first actual action (the BIOS/UEFI TPM change that follows those lines), so the callout remains the prerequisites and the sequential steps begin with the BIOS change.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/reset-password-basic.mdx (1)
6-10: Align Step 3 terminology with the updated boot-device wording.Line 7 still says “unidad USB” while the surrounding steps now use “dispositivo USB de arranque”.
Consistency tweak
-3. **Elimina estos archivos** de la unidad USB: +3. **Elimina estos archivos** del dispositivo USB de arranque:🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/reset-password-basic.mdx` around lines 6 - 10, Step 3's wording uses "unidad USB" which is inconsistent with the surrounding steps; update the phrase in the paragraph under "3. **Elimina estos archivos**" to "dispositivo USB de arranque" so the step reads that you delete the files (`/config/shadow`, `/config/smbpasswd`) from the boot USB device; keep the list of files and the rest of the sentence unchanged.i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx (1)
18-18: Consider using "主页面" for UI consistency.Based on learnings, the Chinese Unraid interface translates "Main" as "主页面". Using "Main 选项卡" may create inconsistency with the actual UI. Consider using "主页面选项卡" instead.
Based on learnings: "在Unraid简体中文界面中，'Main'标签页/按钮被翻译为'主页面'，中文文档应使用'主页面'而非英文'Main'以保持与实际用户界面的一致性。"
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx` at line 18, The text uses the English UI label "**Main** 选项卡" which is inconsistent with the Simplified Chinese Unraid UI; update the string to use the localized label by replacing "**Main** 选项卡" with "**主页面**选项卡" in the sentence that references the Unraid Web GUI (the segment containing "Unraid %%WebGUI|web-gui%% 中的 **Main** 选项卡") so the documentation matches the actual UI terminology.i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (1)
91-93: Consider harmonizing UI label language in this FR doc.These steps mix French prose with English labels (
Settings,Onboarding Wizard,internal boot). Aligning terminology with the rest of the page would improve consistency.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx` around lines 91 - 93, The UI labels in the steps mix French and English; update the strings "Settings → Onboarding Wizard" and "internal boot" to French equivalents used elsewhere in the doc (for example "Paramètres → Assistant d'intégration" and "démarrage interne" or the project's chosen translations) so the instructions read entirely in French and match the rest of the page; locate the text in the automated-flash-backup.mdx file and replace those exact labels inside the list items while preserving formatting and emphasis.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx (1)
26-26: Consider translating "Blacklisted" to Spanish for consistency.The title mixes English ("Blacklisted") with Spanish ("Dispositivos de arranque USB"). Consider using the Spanish equivalent "Dispositivos de arranque USB en lista negra" for a consistent user experience.
Suggested fix
-:::caution[Blacklisted Dispositivos de arranque USB] +:::caution[Dispositivos de arranque USB en lista negra]🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx` at line 26, The admonition title currently mixes English and Spanish in the frontmatter token ":::caution[Blacklisted Dispositivos de arranque USB]"; change the label to fully Spanish (for example ":::caution[Dispositivos de arranque USB en lista negra]" or ":::caution[Dispositivos de arranque USB en lista‑negra]") so the caution block title is consistent; update the token in the MDX file where "Blacklisted Dispositivos de arranque USB" appears.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx (1)
12-12: English heading in Spanish document.Same as the French version, the heading "Back up your boot device" is in English. Consider translating to Spanish (e.g., "Haz una copia de seguridad de tu dispositivo de arranque") while preserving the anchor ID for backwards compatibility.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx` at line 12, The heading "Back up your boot device" in the Spanish doc should be translated to Spanish while keeping the existing anchor for backward compatibility: replace the line "## Back up your boot device {`#back-up-your-flash-device`}" with a Spanish translation such as "## Haz una copia de seguridad de tu dispositivo de arranque {`#back-up-your-flash-device`}" so the visible text is Spanish but the anchor ID "back-up-your-flash-device" remains unchanged; update the header in the file where that heading appears.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx (1)
12-12: English heading in French document.The heading "Back up your boot device" is in English while the rest of the document is in French. This appears intentional to maintain anchor ID consistency (
{#back-up-your-flash-device}), but consider translating it to French (e.g., "Sauvegarder votre périphérique de démarrage") for a consistent user experience.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx` at line 12, The heading text "Back up your boot device" in the French doc should be translated to French for consistency while keeping the existing anchor ID to avoid breaking links; replace the visible heading text with "Sauvegarder votre périphérique de démarrage" (or a similar French phrasing) but leave the anchor token {`#back-up-your-flash-device`} unchanged in the heading line.i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx (1)
9-9: Minor terminology inconsistency.The image alt text uses "périphérique d'amorçage" while the rest of the document uses "périphérique de démarrage". Both terms are valid French translations for "boot device," but consider using consistent terminology throughout.
Suggested fix
-  + 🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx` at line 9, The image alt text string "Contrôle de sauvegarde du périphérique d’amorçage dans le WebGUI" is inconsistent with the document's preferred term "périphérique de démarrage"; update that alt text to "Contrôle de sauvegarde du périphérique de démarrage dans le WebGUI" (the markdown image line containing the alt text and /img/flashbackup.png) and search the document for any other occurrences of "périphérique d’amorçage" to replace them for consistent terminology.i18n/fr/docusaurus-plugin-content-docs/current/unraid-account/update-billing-address-on-file.mdx (1)
11-11: Consider using proper arrow characters.The documentation uses
->for navigation arrows. Consider using the proper Unicode arrow character→for better readability and consistency with documentation standards.Suggested fix
-2. Si vous avez déjà quitté cette page, connectez-vous à votre compte Unraid, accédez à **Gérer les achats** -> **Commandes**, ouvrez la commande, puis cliquez sur **Mettre à jour l'adresse**. +2. Si vous avez déjà quitté cette page, connectez-vous à votre compte Unraid, accédez à **Gérer les achats** → **Commandes**, ouvrez la commande, puis cliquez sur **Mettre à jour l'adresse**.-- Si vous ne voyez pas la commande dans **Gérer les achats** -> **Commandes**, vérifiez que vous utilisez le bon compte. +- Si vous ne voyez pas la commande dans **Gérer les achats** → **Commandes**, vérifiez que vous utilisez le bon compte.Also applies to: 29-29
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-account/update-billing-address-on-file.mdx` at line 11, Replace the ASCII arrow token "->" with the proper Unicode right arrow "→" in the documentation text (e.g., the navigation string "Gérer les achats -> Commandes" and any other occurrences such as the one at the second reported spot), updating the sentence that mentions clicking "Mettre à jour l’adresse" to read "Gérer les achats → Commandes" so all navigation arrows use the proper character for readability and consistency.i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx (1)
44-46: Keep imperative voice consistent in the list.Use the same formal imperative form across bullets (e.g.,
Instale,Acceda) to match the rest of the Spanish page style.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx` around lines 44 - 46, The three bullet items use inconsistent voice and casing; update them to a consistent formal imperative and sentence casing: change "NO necesita iniciar sesión en Unraid Connect para usar la API localmente" to "No necesita iniciar sesión en Unraid Connect para usar la API localmente" (or rephrase to the imperative "No necesite..." if you prefer strict imperative), and change "Accede a la funcionalidad de la API a través del [GraphQL Sandbox](./how-to-use-the-api.mdx)" to "Acceda a la funcionalidad de la API a través del [GraphQL Sandbox](./how-to-use-the-api.mdx)"; ensure all bullets (e.g., the lines containing "Instale", the "No necesita/No necesite" bullet, and "Acceda") consistently use the same formal imperative tone.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdx (1)
1-15: Inconsistent language mixing between English and German.This partial mixes English (lines 1-2, 8-9, 15) with German (lines 4, 6, 11). While keeping WebGUI labels in English may be intentional, the explanatory text switches between languages, which could confuse readers. Consider either fully translating the instructional content or keeping a consistent approach throughout.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdx` around lines 1 - 15, The partial mixes English UI labels and explanatory German; make the language consistent by translating the English instructional and explanatory sentences into German while keeping WebGUI label tokens (e.g., "Mirror syslog to boot drive", "Apply", and the %%syslog|syslog%% viewer token) in English as needed. Specifically update the top instructions ("Select **Yes** under **Mirror syslog to boot drive**." and "Click **Apply**. Logs will be saved to `/boot/logs/syslog` on your boot device"), the "By default..." paragraph and the caution paragraph lines that are in English into German, and ensure references to `/boot/logs/syslog-previous` and the viewer remain clear and use the existing %%syslog|syslog%% token (leave token syntax unchanged).i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md (1)
95-95: Disambiguate the repeated beta.1 subheadings.Reusing
### Stockageand### Unraid APIin the retained beta.1 changelog triggers duplicate-heading warnings and makes generated anchors less predictable. Adding a suffix like(beta.1)would keep these sections distinct.Also applies to: 145-145
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md` at line 95, The repeated section headings "### Stockage" and "### Unraid API" cause duplicate-heading warnings and ambiguous anchors; update the duplicate occurrences (the retained beta.1 changelog headings) by appending a disambiguator like " (beta.1)" to each duplicate heading so they become e.g. "### Stockage (beta.1)" and "### Unraid API (beta.1)" ensuring both occurrences are consistently renamed to keep anchors unique and predictable.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md (1)
95-95: Disambiguate the repeated beta.1 subheadings.Reusing
### Speicherand### Unraid APIin the retained beta.1 changelog triggers duplicate-heading warnings and makes generated anchors less predictable. Adding a suffix like(beta.1)would keep these sections distinct.Also applies to: 145-145
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.3.0.md` at line 95, The repeated headings "### Speicher" and "### Unraid API" cause duplicate-heading warnings; edit the two occurrences (the heading at "### Speicher" and the heading at "### Unraid API") to append a disambiguating suffix such as " (beta.1)" — e.g., change "### Speicher" -> "### Speicher (beta.1)" and "### Unraid API" -> "### Unraid API (beta.1)" so anchors and headings are unique and warnings are resolved.
| ::: | ||
|
|
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE="i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx"
echo "Context around the changed area:"
nl -ba "$FILE" | sed -n '128,146p'
echo
echo "Detect potential orphan admonition closers:"
python - <<'PY'
from pathlib import Path
p = Path("i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx")
lines = p.read_text(encoding="utf-8").splitlines()
depth = 0
for i, line in enumerate(lines, 1):
s = line.strip()
if s.startswith(":::") and s != ":::":
depth += 1
elif s == ":::":
if depth == 0:
print(f"orphan closing delimiter at line {i}")
else:
depth -= 1
print(f"final admonition depth: {depth}")
PYRepository: unraid/docs
Length of output: 147
🏁 Script executed:
#!/bin/bash
set -euo pipefail
FILE="i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx"
echo "Context around the changed area (lines 128-146):"
sed -n '128,146p' "$FILE" | cat -n
echo
echo "Detect potential orphan admonition closers:"
python3 <<'PY'
from pathlib import Path
p = Path("i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx")
lines = p.read_text(encoding="utf-8").splitlines()
depth = 0
orphans = []
for i, line in enumerate(lines, 1):
s = line.strip()
if s.startswith(":::") and s != ":::":
depth += 1
print(f"Line {i}: opening delimiter - depth now {depth}")
elif s == ":::":
if depth == 0:
orphans.append(i)
print(f"Line {i}: ORPHAN closing delimiter")
else:
depth -= 1
print(f"Line {i}: closing delimiter - depth now {depth}")
print(f"\nFinal admonition depth: {depth}")
if orphans:
print(f"Orphan delimiters found at lines: {orphans}")
PYRepository: unraid/docs
Length of output: 1494
Remove the orphan ::: delimiter before the highlights section.
Line 138 contains a standalone ::: after the prior admonition is already closed at line 136, which breaks MDX/Docusaurus admonition syntax and will cause parsing or rendering issues.
Proposed fix
-:::
-
### Unraid v7.2-beta.1 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.
| ::: | |
| ### Unraid v7.2-beta.1 Highlights |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx`
around lines 138 - 139, Remove the orphan MDX admonition delimiter "::: " that
appears standalone before the highlights section (it follows the previously
closed admonition), so delete that extra `:::` line to restore valid
Docusaurus/MDX admonition syntax and prevent parsing/rendering errors.
| <div | ||
| style={{ | ||
| margin: "auto", | ||
| maxWidth: "600px", | ||
| display: "flex", | ||
| flexDirection: "column", | ||
| alignItems: "center", | ||
| }} | ||
| > | ||
|  | ||
| </div> |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify if both image path conventions are valid and images exist
echo "Checking for images in ./assets/ directory:"
fd -t f 'zfs.*\.png' docs/ i18n/ --exec dirname {} \; | sort -u | head -5
echo ""
echo "Checking for images in /img/ or static/img directory:"
fd -t f 'zfs14.png\|zfs15.png\|zfs16.png' . 2>/dev/null || echo "Not found in current search"
echo ""
echo "Listing static/img contents if exists:"
ls -la static/img/zfs*.png 2>/dev/null || echo "No static/img directory or no zfs images found"Repository: unraid/docs
Length of output: 723
🏁 Script executed:
# First, let's check the file size and then read the relevant sections
wc -l i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxRepository: unraid/docs
Length of output: 172
🏁 Script executed:
# Read lines around 354-364 and also check lines 409 and 428 mentioned in the review
sed -n '350,370p' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxRepository: unraid/docs
Length of output: 1073
🏁 Script executed:
# Check lines 405-415 and 424-434 as well
sed -n '405,415p' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
echo "---"
sed -n '424,434p' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxRepository: unraid/docs
Length of output: 1753
🏁 Script executed:
# Search for all image references in the file to see the pattern
rg -n '\!\[.*\]\(' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx | head -20Repository: unraid/docs
Length of output: 131
🏁 Script executed:
# Search for all image references in the file with proper syntax
rg -n '!\[' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxRepository: unraid/docs
Length of output: 478
🏁 Script executed:
# Also check the English version to see what path convention it uses
wc -l docs/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdxRepository: unraid/docs
Length of output: 130
🏁 Script executed:
# Check image paths in the English version
rg -n '!\[' docs/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx | head -20Repository: unraid/docs
Length of output: 524
🏁 Script executed:
# Verify the image files actually exist in the assets directory
ls -la i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/assets/zfs14.png i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/assets/zfs15.png i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/assets/zfs16.png 2>&1Repository: unraid/docs
Length of output: 552
🏁 Script executed:
# Check if there's a static/img directory anywhere in the repo
fd -t d 'img' . --type directory | grep -E '(static|public)' | head -10Repository: unraid/docs
Length of output: 68
🏁 Script executed:
# Check if zfs14, zfs15, zfs16 images exist in static/img directory
ls -la static/img/ | grep -E 'zfs(14|15|16)'Repository: unraid/docs
Length of output: 37
🏁 Script executed:
# Let's also check what's in the static/img directory
ls -la static/img/ | head -20Repository: unraid/docs
Length of output: 1365
Fix broken image paths in German translation.
The German file uses incorrect /img/ paths for lines 363, 409, and 428 (zfs14, zfs15, zfs16) that don't resolve to valid files. These images actually exist in ./assets/ like all other images in the file and the English version. Change all three references from /img/zfsN.png to ./assets/zfsN.png.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 354 - 364, Replace the three broken image references
'/img/zfs14.png', '/img/zfs15.png' and '/img/zfs16.png' in the German MDX (they
appear where the HTML <div> renders the image) with the local asset paths
'./assets/zfs14.png', './assets/zfs15.png' and './assets/zfs16.png' respectively
so they match the English version and other images in the file; update each src
string exactly and keep the surrounding JSX/HTML structure unchanged.
| Es wird empfohlen, Ihre %%VM|vm%% **Netzwerkquelle** auf **virbr0** (Private NAT) einzurichten. Dieser Modus funktioniert mit einer beliebigen Anzahl von %%VMs|vm%% und stellt den Netzwerkzugang über %%NAT|nat%% bereit. Beachten Sie, dass mDNS nicht über NAT funktioniert, sodass die %%VM|vm%% auf andere lokale Netzwerkgeräte über die IP-Adresse und nicht über den Hostnamen zugreifen muss. Sie können IP-Adressen und Hostnamen zur Hosts-Datei im Betriebssystem der %%VM|vm%% hinzufügen, um den Zugriff über den Hostnamen zu ermöglichen. Die %%VMs|vm%% sind nicht direkt von anderen Geräten in Ihrem LAN erreichbar, aber Sie können dennoch über %%VNC|vnc-session%% über den Host auf sie zugreifen. | ||
| Die Einstellung **Power Mode** ermöglicht es Ihnen, Ihren Unraid-Server für Energieeffizienz, ausgewogene Betriebsweise oder maximale Leistung zu optimieren. Sie können aus den verfügbaren Modi - **Beste Energieeffizienz**, **Ausgewogener Betrieb** oder **Beste Leistung** - wählen, um Ihren Arbeitslasten und Energiepräferenzen gerecht zu werden. Die Anpassung des Power Modes kann dazu beitragen, den Energieverbrauch zu senken, die Systemtemperaturen zu reduzieren oder zusätzliche Ressourcen für anspruchsvolle Aufgaben bereitzustellen. | ||
|
|
||
| Für weitere Informationen zur %%VM|vm%%-Vernetzung, siehe [Übersicht und Systemvorbereitung](../../using-unraid-to/create-virtual machines/overview-and-system-prep.mdx). |
There was a problem hiding this comment.
Broken link due to space in path.
The link path create-virtual machines contains a space which will cause a 404 error. It should be create-virtual-machines.
-Für weitere Informationen zur %%VM|vm%%-Vernetzung, siehe [Übersicht und Systemvorbereitung](../../using-unraid-to/create-virtual machines/overview-and-system-prep.mdx).
+Für weitere Informationen zur %%VM|vm%%-Vernetzung, siehe [Übersicht und Systemvorbereitung](../../using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx).📝 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.
| Für weitere Informationen zur %%VM|vm%%-Vernetzung, siehe [Übersicht und Systemvorbereitung](../../using-unraid-to/create-virtual machines/overview-and-system-prep.mdx). | |
| Für weitere Informationen zur %%VM|vm%%-Vernetzung, siehe [Übersicht und Systemvorbereitung](../../using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx). |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx`
at line 174, Update the broken markdown link target by replacing the space in
the URL segment "create-virtual machines" with a hyphen; locate the link with
the anchor text "[Übersicht und Systemvorbereitung]" and change the path segment
to "create-virtual-machines" so the link points to the correct document.
|
|
||
| - system - wird verwendet, um Docker-Image-Schichten in einem Loopback-Image zu speichern, das in system/docker gespeichert ist. | ||
| - appdata - wird von Docker-Anwendungen verwendet, um Anwendungsdaten zu speichern. | ||
| - vielleicht hatten wir keinen Platz mehr |
There was a problem hiding this comment.
Remove placeholder/incomplete text.
Line 157 contains what appears to be a placeholder comment in German ("maybe we ran out of space") that should not be in the final release notes. This line should be removed.
🗑️ Proposed fix
- appdata - wird von Docker-Anwendungen verwendet, um Anwendungsdaten zu speichern.
-- vielleicht hatten wir keinen Platz mehr
-
-### Vorhandene Freigaben verwalten
Der Unraid OS VM-Manager ist standardmäßig so konfiguriert, dass er diese vorhandenen Freigaben verwendet:📝 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.
| - vielleicht hatten wir keinen Platz mehr | |
| - appdata - wird von Docker-Anwendungen verwendet, um Anwendungsdaten zu speichern. | |
| ### Vorhandene Freigaben verwalten | |
| Der Unraid OS VM-Manager ist standardmäßig so konfiguriert, dass er diese vorhandenen Freigaben verwendet: |
🧰 Tools
🪛 LanguageTool
[grammar] ~157-~157: Hier könnte ein Fehler sein.
Context: ... vielleicht hatten wir keinen Platz mehr ### Vorhandene Freigaben verwalten Der Unra...
(QB_NEW_DE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md`
at line 157, Remove the placeholder German sentence "vielleicht hatten wir
keinen Platz mehr" from the release notes so the final copy contains no
incomplete or placeholder text; locate the string in the release-notes content
for version 7.0.0 and delete that line, then run a quick local build or linter
to ensure no trailing whitespace or formatting issues remain in the same
document.
| ### Vorhandene Freigaben verwalten | ||
|
|
||
| Der Unraid OS VM-Manager ist standardmäßig so konfiguriert, dass er diese vorhandenen Freigaben verwendet: | ||
|
|
||
| - system - wird verwendet, um Libvirt-Loopback-Image zu speichern, das in system/libvirt gespeichert ist. | ||
| - domains - wird zum Speichern von VM-Vdisk-Images verwendet | ||
| - isos - wird zum Speichern von ISO-Boot-Images verwendet | ||
|
|
||
| Wenn Docker oder VMs aktiviert sind, werden die erforderlichen vorhandenen Freigaben je nach diesen Regeln bei Bedarf erstellt: | ||
| Der Unraid OS VM-Manager ist standardmäßig so konfiguriert, dass er diese vorhandenen Freigaben verwendet: | ||
|
|
||
| - Wenn ein Pool namens 'cache' vorhanden ist, werden vordefinierte Freigaben mit 'cache' als Primärspeicher ohne Sekundärspeicher erstellt. | ||
| - Wenn kein Pool namens 'cache' vorhanden ist, werden die vordefinierten Freigaben mit dem alphabetisch ersten vorhandenen Pool als Primärspeicher ohne Sekundärspeicher erstellt. | ||
| - Wenn keine Pools vorhanden sind, werden die vordefinierten Freigaben auf dem Unraid-Array als Primärspeicher ohne Sekundärspeicher erstellt. | ||
|
|
||
| ### ZFS-Implementierung | ||
| Wenn Docker oder VMs aktiviert sind, werden die erforderlichen vorhandenen Freigaben je nach diesen Regeln bei Bedarf erstellt: | ||
|
|
||
| - Für ZFS-Hauptpool (Root): | ||
| - Für ZFS-Spezial-, Log- und Deduplizierungs-Sub-Pools: | ||
| - Wenn keine Pools vorhanden sind, werden die vordefinierten Freigaben auf dem Unraid-Array als Primärspeicher ohne Sekundärspeicher erstellt. | ||
|
|
There was a problem hiding this comment.
Fix duplicated and jumbled section content.
Lines 159-177 contain severe structural problems:
- The "Vorhandene Freigaben verwalten" heading appears twice (lines 159, 166)
- VM Manager configuration content is duplicated (lines 161-165)
- ZFS allocation profile content is incorrectly mixed into the VM Manager section (lines 174-177)
- Docker/VM activation rules appear duplicated
This creates a confusing and broken document structure. The content needs to be deduplicated and properly organized into distinct sections.
🧰 Tools
🪛 LanguageTool
[grammar] ~161-~161: Entferne ein Leerzeichen
Context: ...rhandene Freigaben verwalten Der Unraid OS VM-Manager ist standardmäßig so konfigur...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~163-~163: Passe die Groß- und Kleinschreibung an
Context: ...ese vorhandenen Freigaben verwendet: - system - wird verwendet, um Libvirt-Loopback-Ima...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_LOWERCASE)
[grammar] ~164-~164: Korrigiere die Fehler
Context: ...as in system/libvirt gespeichert ist. - domains - wird zum Speichern von VM-Vdisk-Images verwe...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)
[grammar] ~166-~166: Entferne ein Leerzeichen
Context: ...on VM-Vdisk-Images verwendet Der Unraid OS VM-Manager ist standardmäßig so konfigur...
(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)
[grammar] ~168-~168: Ersetze das Satzzeichen
Context: ...aben verwendet: - Wenn ein Pool namens 'cache' vorhanden ist, werden vordefinierte Fre...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_APOSTROPHE_‚)
[grammar] ~168-~168: Ersetze das Satzzeichen
Context: ...ist, werden vordefinierte Freigaben mit 'cache' als Primärspeicher ohne Sekundärspeiche...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_APOSTROPHE_‚)
[grammar] ~169-~169: Ersetze das Satzzeichen
Context: ...icher erstellt. - Wenn kein Pool namens 'cache' vorhanden ist, werden die vordefinierte...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_APOSTROPHE_‚)
[style] ~170-~170: Drei aufeinanderfolgende Sätze beginnen mit dem gleichen Wort. Evtl. können Sie den Satz umformulieren, zum Beispiel, indem Sie ein Synonym nutzen.
Context: ...icher ohne Sekundärspeicher erstellt. - Wenn keine Pools vorhanden sind, werden die ...
(GERMAN_WORD_REPEAT_BEGINNING_RULE)
[style] ~171-~171: Drei aufeinanderfolgende Sätze beginnen mit dem gleichen Wort. Evtl. können Sie den Satz umformulieren, zum Beispiel, indem Sie ein Synonym nutzen.
Context: ...eicher ohne Sekundärspeicher erstellt. Wenn Docker oder VMs aktiviert sind, werden ...
(GERMAN_WORD_REPEAT_BEGINNING_RULE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md`
around lines 159 - 177, Remove the duplicated "Vorhandene Freigaben verwalten"
block and the repeated VM Manager paragraphs so only one clear "Vorhandene
Freigaben verwalten" section remains describing the default shares used (system,
domains) and the cache/first-pool/no-pool rules for VM manager; extract the ZFS
allocation profile lines referencing "ZFS-Hauptpool (Root)" and "ZFS-Spezial-,
Log- und Deduplizierungs-Sub-Pools" into a separate, correctly titled section
(e.g., "ZFS-Zuweisungsprofil") and ensure the Docker/VM activation rules appear
once under the appropriate section, deduplicating any repeated bullets.
| <div | ||
| style={{ | ||
| margen: "auto", | ||
| maxAnchura: "600px", | ||
| display: "flex", | ||
| flexDirection: "columna", | ||
| alignItems: "centro", | ||
| }} | ||
| > |
There was a problem hiding this comment.
Invalid CSS property names will break rendering.
Same issue as in the backup-using-webgui.mdx partial - CSS property names are incorrectly translated to Spanish.
Proposed fix
<div
style={{
- margen: "auto",
- maxAnchura: "600px",
+ margin: "auto",
+ maxWidth: "600px",
display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
+ flexDirection: "column",
+ alignItems: "center",
}}
>📝 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.
| <div | |
| style={{ | |
| margen: "auto", | |
| maxAnchura: "600px", | |
| display: "flex", | |
| flexDirection: "columna", | |
| alignItems: "centro", | |
| }} | |
| > | |
| <div | |
| style={{ | |
| margin: "auto", | |
| maxWidth: "600px", | |
| display: "flex", | |
| flexDirection: "column", | |
| alignItems: "center", | |
| }} | |
| > |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx`
around lines 42 - 50, The inline style object on the JSX <div> in the
diagnostics page uses Spanish property names that are invalid in CSS-in-JS
(e.g., "margen", "maxAnchura", "columna", "centro"); replace them with the
correct CSS-in-JS keys ("margin", "maxWidth", "flexDirection": "column", and
"alignItems": "center") in the style prop of the <div> so the component renders
correctly.
| <div | ||
| style={{ | ||
| margen: "auto", | ||
| maxAnchura: "600px", | ||
| display: "flex", | ||
| flexDirection: "columna", | ||
| alignItems: "centro", | ||
| }} |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What are the valid CSS property names and values for React JSX style objects? Are CSS properties like margin, maxWidth, flexDirection, and alignItems values like "column" and "center" translatable?
💡 Result:
In React JSX, the style attribute accepts a JavaScript object where keys are CSS property names converted to camelCase (e.g., 'background-color' becomes 'backgroundColor', 'max-width' becomes 'maxWidth', 'flex-direction' becomes 'flexDirection', 'align-items' becomes 'alignItems'). Values are standard CSS values as strings (e.g., 'column', 'center') or numbers (for properties where React auto-appends 'px', like margin: 10 becomes '10px'; unitless for properties like flex, order). Valid property names: All standard CSS properties supported by browsers, in camelCase form, consistent with the DOM element.style object. Examples: - margin (shorthand: margin: '10px') - maxWidth: '500px' - flexDirection: 'column' - alignItems: 'center' These specific properties and values are directly translatable and valid in React style objects, as they match browser DOM style properties. Note: Inline styles do not support pseudo-classes, media queries, or autoprefixing; prefer className for complex styling. Examples from docs: <div style={{color: 'blue', backgroundImage: 'url(' + imgUrl + ')'}}>... <div style={{marginBottom: 10}}>... Shorthand properties like margin expand correctly (margin: '10px 20px').
Citations:
- 1: https://legacy.reactjs.org/docs/dom-elements.html
- 2: https://www.w3schools.com/react/react_css.asp
- 3: https://reactjs.org/docs/dom-elements.html
- 4: https://learn.react-js.dev/basics/css-and-styling
- 5: https://blogs.purecode.ai/blogs/react-inline-style
- 6: https://developer.mozilla.org/en-US/docs/Web/API/CSSStyleProperties
- 7: https://developer.mozilla.org/en/DOM/element.style
🏁 Script executed:
cat -n "i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx" | sed -n '274,281p'Repository: unraid/docs
Length of output: 234
Invalid CSS property names and values in JSX style object.
The style prop at lines 276–280 contains Spanish translations of CSS property names and values, which are invalid in JSX:
margenshould bemarginmaxAnchurashould bemaxWidthflexDirection: "columna"should beflexDirection: "column"alignItems: "centro"should bealignItems: "center"
CSS property names and values in JSX must use the standard camelCase JavaScript API (e.g., maxWidth, not maxAnchura) and English keywords (e.g., "center", not "centro"). These are not user-facing strings and should never be translated.
Proposed fix
<div
style={{
- margen: "auto",
- maxAnchura: "600px",
+ margin: "auto",
+ maxWidth: "600px",
display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
+ flexDirection: "column",
+ alignItems: "center",
}}📝 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.
| <div | |
| style={{ | |
| margen: "auto", | |
| maxAnchura: "600px", | |
| display: "flex", | |
| flexDirection: "columna", | |
| alignItems: "centro", | |
| }} | |
| <div | |
| style={{ | |
| margin: "auto", | |
| maxWidth: "600px", | |
| display: "flex", | |
| flexDirection: "column", | |
| alignItems: "center", | |
| }} |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx`
around lines 274 - 281, The inline JSX style object on the <div> uses
Spanish-translated CSS keys/values (margen, maxAnchura, "columna", "centro");
update the style prop on that <div> so the keys use standard camelCase JS names
and English values (replace margen → margin, maxAnchura → maxWidth,
flexDirection: "columna" → flexDirection: "column", alignItems: "centro" →
alignItems: "center") so the style object is valid in React.
| @@ -51,19 +51,27 @@ Pour les versions d'Unraid antérieures à la v7.2 ou pour accéder à de nouvel | |||
|
|
|||
| <div style={{affichage: 'grille', templateColonnesGrille: 'répéter(auto-fit, minmax(250px, 1fr))', écart: '1rem'}}> | |||
There was a problem hiding this comment.
CSS property names incorrectly translated - will break rendering.
The inline style uses French words for CSS properties (affichage, templateColonnesGrille, répéter, écart), but CSS property names must remain in English. This will cause the grid layout to fail.
Proposed fix
-<div style={{affichage: 'grille', templateColonnesGrille: 'répéter(auto-fit, minmax(250px, 1fr))', écart: '1rem'}}>
+<div style={{display: 'grid', gridTemplateColumns: 'repeat(auto-fit, minmax(250px, 1fr))', gap: '1rem'}}>📝 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.
| <div style={{affichage: 'grille', templateColonnesGrille: 'répéter(auto-fit, minmax(250px, 1fr))', écart: '1rem'}}> | |
| <div style={{display: 'grid', gridTemplateColumns: 'repeat(auto-fit, minmax(250px, 1fr))', gap: '1rem'}}> |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@i18n/fr/docusaurus-plugin-content-docs/current/API/index.mdx` at line 52, The
inline JSX style on the <div> element uses French CSS property names (affichage,
templateColonnesGrille, écart) and translated function names (répéter) which
will break rendering; update the style object on that <div> (the line starting
with <div style={{affichage: ...) to use the correct English CSS-in-JS keys and
values: display, gridTemplateColumns, gap and the CSS function repeat(auto-fit,
minmax(250px, 1fr)) so the grid layout renders correctly.
| ::: | ||
|
|
||
| ## Dépannage en mode sans échec {#troubleshooting-with-safe-mode} | ||
| ## Dépannage en mode sans échec |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify whether the removed fragment is still referenced anywhere in the repo.
rg -n --hidden -S 'troubleshooting-with-safe-mode|#troubleshooting-with-safe-mode'Repository: unraid/docs
Length of output: 2970
Critical: Removing this anchor breaks active cross-document links.
The explicit anchor {#troubleshooting-with-safe-mode} is actively referenced in at least 2 French documentation files:
i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx:205i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx:136
Dropping the explicit anchor will cause these links to fail. Restore the heading with the explicit anchor:
-## Dépannage en mode sans échec
+## Dépannage en mode sans échec {`#troubleshooting-with-safe-mode`}📝 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.
| ## Dépannage en mode sans échec | |
| ## Dépannage en mode sans échec {`#troubleshooting-with-safe-mode`} |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx`
at line 61, Restore the explicit anchor on the heading by changing the "##
Dépannage en mode sans échec" heading to include the anchor
{`#troubleshooting-with-safe-mode`} (i.e., ensure the heading text "Dépannage en
mode sans échec" contains the anchor id troubleshooting-with-safe-mode) so
existing cross-document links referencing that anchor continue to resolve;
update the heading in the plugins.mdx file where the heading appears (look for
the exact heading text and add the {`#troubleshooting-with-safe-mode`} anchor).
| :::note[Server 需要上下文 | ||
|
|
||
| 如果您看不到兑换表单，您可能需要先加载服务器上下文。单击**"管理服务器"**以将服务器连接到帐户应用程序。 | ||
| 如果您看不到兑换表单，您可能需要先加载服务器上下文。单击\*\*“管理服务器”\*\*以将服务器连接到帐户应用程序。 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify malformed admonition titles in MDX files (missing closing bracket).
# Expected: no matches.
rg -nP --iglob '*.mdx' ':::(note|info|tip|warning|danger)\[[^\]]*$'Repository: unraid/docs
Length of output: 5694
🏁 Script executed:
cat -n i18n/zh/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx | sed -n '50,70p'Repository: unraid/docs
Length of output: 679
Close the admonition title bracket to avoid MDX parse errors.
Line 58 has :::note[Server 需要上下文 without a closing ]. Docusaurus admonition syntax requires closing brackets for titled admonitions.
Fix
-:::note[Server 需要上下文
+:::note[Server 需要上下文]📝 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 需要上下文 | |
| 如果您看不到兑换表单，您可能需要先加载服务器上下文。单击**"管理服务器"**以将服务器连接到帐户应用程序。 | |
| 如果您看不到兑换表单，您可能需要先加载服务器上下文。单击\*\*“管理服务器”\*\*以将服务器连接到帐户应用程序。 | |
| :::note[Server 需要上下文] | |
| 如果您看不到兑换表单，您可能需要先加载服务器上下文。单击\*\*"管理服务器"\*\*以将服务器连接到帐户应用程序。 |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~60-~60: 您的意思是“"账"户”？
Context: ...您可能需要先加载服务器上下文。单击**“管理服务器”**以将服务器连接到帐户应用程序。 ::: ## 重要说明 - 激活码仅能使用一次，用于为您的服...
(ZHANG7_ZHANG8)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx`
around lines 58 - 60, The MDX admonition title is missing a closing bracket:
change the token `:::note[Server 需要上下文` to include the closing bracket (i.e.,
`:::note[Server 需要上下文]`) and verify the admonition body is followed by a closing
`:::` so the `redeem-activation-code.mdx` admonition parses correctly; locate
the line containing `:::note[Server 需要上下文` and add the `]` and ensure the
matching `:::` terminator is present.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
unraid-docs | 36cf38e | Apr 02 2026, 03:24 AM |
2 participants
Summary by CodeRabbit