Conversation
📝 WalkthroughWalkthroughThis pull request contains extensive internationalization (i18n) updates and documentation additions across multiple languages (German, Spanish, French, and Japanese), along with formatting refinements to inline style objects in existing MDX files. The changes include new Japanese language support with comprehensive translations of API documentation, account management, Unraid Connect features, system administration guides, troubleshooting resources, and release notes spanning multiple Unraid OS versions. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 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: 10
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (14)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (1)
212-223:⚠️ Potential issue | 🔴 CriticalCSS properties and values must remain in English—this will break the layout.
CSS property names (
margen,maxAnchura) and values ("columna","centro") have been incorrectly translated to Spanish. CSS is a language-specific syntax that only recognizes English keywords. This styling will not be applied, breaking the image centering and layout.🐛 Proposed fix to restore valid CSS
<div style={{ -margen: "auto", -maxAnchura: "600px", +margin: "auto", +maxWidth: "600px", display: "flex", -flexDirection: "columna", -alignItems: "centro", +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/manage-storage/cache-pools.mdx` around lines 212 - 223, The inline style object on the <div> uses translated CSS keys and values (e.g., "margen", "maxAnchura", "columna", "centro") which are invalid—replace them with standard English CSS property names and values (e.g., margin, maxWidth, display, flexDirection set to "column", alignItems set to "center") so the style on the div element and the image centering resume working; update the style object where it appears (the <div style={{ ... }}> block) and ensure values use correct casing and string values as in typical React inline styles.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx (3)
62-72:⚠️ Potential issue | 🟡 MinorDuplicate paragraph about QEMU guest agent.
The paragraph explaining the need to install the QEMU guest agent for hibernation (lines 62 and 72) appears twice in the document.
🤖 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 62 - 72, Remove the duplicated paragraph that repeats the explanation to install the %%QEMU|qemu%%-%%Guest-Agent|guest-agent%% in your Windows %%VM|vm%% (the two identical blocks about hibernation, shutdown and live stats); keep a single instance of that paragraph and delete the redundant copy so the document contains only one explanation of the QEMU guest agent.
109-162:⚠️ Potential issue | 🟠 MajorMultiple duplicate and mismatched sections.
This section has significant content issues:
- "Windows-Indizierung deaktivieren" appears twice (lines 109-122 and 124-135)
- "Automatische Festplattendefragmentierung deaktivieren" (lines 137-148) incorrectly describes Windows Search indexing instead of disk defragmentation
- "Hochleistungsmodus aktivieren" (lines 150-162) also incorrectly describes Windows Search indexing instead of high-performance mode
These appear to be Crowdin sync artifacts. The descriptions should match their respective section headings.
🤖 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 109 - 162, Remove the duplicate "Windows-Indizierung deaktivieren" block and ensure only one correct German section remains; replace the English/incorrect paragraph under "Automatische Festplattendefragmentierung deaktivieren" with German instructions that actually describe how to disable scheduled drive optimization (match the steps already present for opening Datei-Explorer → Eigenschaften → Tools → Optimieren → Einstellungen ändern), and replace the incorrect Windows Search text under "Hochleistungsmodus aktivieren" with the correct German steps to enable High Performance power plan (e.g., Öffnen der Energieoptionen → Erweiterte Pläne anzeigen → Hochleistung aktivieren / Energieeinstellungen ändern); confirm headings "Windows-Indizierung deaktivieren", "Automatische Festplattendefragmentierung deaktivieren", and "Hochleistungsmodus aktivieren" each have matching German content and remove any Crowdin-sync duplicate artifacts.
205-228:⚠️ Potential issue | 🟠 MajorMismatched section content.
The "HDMI-Audio mit MSI-Interrupts beheben" section (lines 205-228) contains instructions labeled as "Wie man den Remote-Desktop-Zugriff (RDP) aktiviert" instead of MSI interrupt configuration. The content appears mixed with RDP and MSI instructions interleaved incorrectly.
🤖 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 205 - 228, The "HDMI-Audio mit MSI-Interrupts beheben" section contains RDP enablement content titled "Wie man den Remote-Desktop-Zugriff (RDP) aktiviert" mixed with MSI steps; separate and correct the content by removing RDP-specific instructions and tip from this section and instead keep only MSI-related steps: keep the lspci command example (`lspci -v -s 01:00.0`) and the search for the `Capabilities: [68] MSI: Enable+` line, instruct to enable MSI via the Windows registry or the MSI Mode Utility (link retained), and tell the user to reboot the VM after changes; move the RDP instructions and the network bridge tip into the appropriate RDP/remote-access section or create a distinct "Remote Desktop (RDP) aktivieren" section so the "HDMI-Audio mit MSI-Interrupts beheben" header and its details only document MSI troubleshooting and remediation.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx (3)
350-352:⚠️ Potential issue | 🟡 MinorDuplicate instruction line.
Lines 351-352 contain the same instruction about setting USB flash drive as primary boot device and enabling UEFI boot mode. One instance should be removed.
🤖 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/faq.mdx` around lines 350 - 352, Remove the duplicate instruction sentence that repeats "Setzen Sie das USB-Flash-Laufwerk als primäres Boot-Gerät und aktivieren Sie den %%UEFI|uefi%%-Bootmodus (deaktivieren Sie CSM/Legacy/Kompatibilitätsmodus, sofern verfügbar)." so it appears only once in the FAQ section; edit the file entry where this sentence occurs twice (the two identical lines in the snippet) and delete one of them, leaving a single, correctly formatted occurrence.
35-37:⚠️ Potential issue | 🟡 MinorDuplicate paragraph detected.
Lines 35-37 contain a duplicate of lines 35-36. The text about checking firmware updates and HBA/IT mode appears twice consecutively.
🤖 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/faq.mdx` around lines 35 - 37, Remove the duplicated paragraph that repeats "Überprüfen Sie stets auf Firmware-Updates und stellen Sie sicher, dass der Controller auf HBA/IT-Modus und nicht auf %%RAID|raid%%-Modus eingestellt ist..." so only a single instance remains; locate the repeated sentence in the FAQ content and delete the second occurrence, preserving the link to "Empfohlene Controller-Thread" and leaving the placeholder token %%RAID|raid%% intact.
45-59:⚠️ Potential issue | 🟡 MinorUntranslated English content in German locale file.
Several paragraphs remain in English instead of German:
- Line 45: "Unraid allows for the expansion..."
- Lines 53-55: "While Unraid doesn't have a specific allocation feature..."
- Lines 57-59: "If you're uncertain about a drive's health..."
These should be translated to German for consistency with the rest of the document.
🤖 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/faq.mdx` around lines 45 - 59, Translate the untranslated English paragraphs into German while preserving all localization tokens (e.g., %%SMART|smart%%, %%WebGUI|web-gui%%, %%RAID|raid%%, %%AHCI|ahci%%, %%parity|parity%%), anchors (e.g., <a id="fehlerhafte-sektoren-zuteilung" />), HTML tags (<br />) and forum links; specifically replace the English sentence beginning "Unraid allows for the expansion..." and both repeated blocks starting "While Unraid doesn't have a specific allocation feature..." and "If you're uncertain about a drive's health..." with correct German translations, keeping the same sentence structure/formatting and duplications mirrored if intentional. Ensure the translated text reads naturally in German and retains the tokens and link syntax exactly as shown.i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (1)
73-78:⚠️ Potential issue | 🟡 MinorIncomplete admonition block structure.
The
:::importantblock at lines 73-77 appears incomplete - it contains only "So stellen Sie Ihre Konfiguration wieder her:" but then the admonition closes, and the actual steps appear separately below. This may cause rendering issues or confusing documentation structure.-:::important - -So stellen Sie Ihre Konfiguration wieder her: - -::: - -Nach dem Booten mit dem wiederhergestellten Flash-Laufwerk: - ## Flash-Backup wiederherstellenConsider either removing this incomplete block or restructuring the content appropriately.
🤖 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-connect/automated-flash-backup.mdx` around lines 73 - 78, The documentation contains an incomplete admonition started with the token ":::important" that only includes the heading "So stellen Sie Ihre Konfiguration wieder her:" and then closes, leaving the actual steps outside; fix it by either (A) expanding the admonition block around the following steps so the instructions are inside the ":::important" ... ":::” block, or (B) remove the ":::important" markers entirely and make the heading a normal paragraph/heading; update the block that uses the ":::important" token so the admonition syntax and its content are consistent (adjust the text immediately following the current ":::important" token and the subsequent steps).i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)
33-38:⚠️ Potential issue | 🟡 MinorUntranslated English content in German documentation.
Several sections contain English text that appears not to have been translated yet (e.g., lines 33-38, 191-199, 433-436, 449, 493-496, 506). If this is a work-in-progress translation from Crowdin, this may be expected behavior.
🤖 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 33 - 38, Several English strings remain untranslated in the German doc (notably the block containing placeholders like %%ZFS|zfs%%, %%snapshots|snapshot%%, %%array|array%%, and %%parity|parity%%). Replace the English sentences in that block with proper German translations while preserving all Crowdin/placeholder tokens exactly (e.g., %%ZFS|zfs%%, %%snapshots|snapshot%%, %%array|array%%, %%parity|parity%%) and keep Markdown/MDX structure (the :::info block and wording) intact; ensure similar untranslated occurrences elsewhere (lines flagged in the comment) are translated the same way for consistency.i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (2)
229-250:⚠️ Potential issue | 🟡 MinorDuplicate "Deinstallation" content.
The uninstallation bullet points appear twice - once under "Abmeldung" (Sign Out, lines 233-239) and again under "Deinstallation des Plugins" (lines 244-250). The content is identical and may need consolidation.
🤖 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-connect/overview-and-setup.mdx` around lines 229 - 250, The "Deinstallation des Plugins" bullet list is duplicated under the "Abmeldung" section; keep the sign-out instruction under the "Abmeldung" heading and remove or collapse the duplicated uninstallation bullets there, leaving the full uninstallation bullet list only under the "Deinstallation des Plugins" heading (or alternatively replace the duplicate in "Abmeldung" with a single line linking to "Deinstallation des Plugins"); update the headings "Abmeldung" and "Deinstallation des Plugins" areas accordingly to avoid repeated content.
157-179:⚠️ Potential issue | 🟡 MinorDuplicate "Lizenzverwaltung" (License Management) sections.
The "Lizenzverwaltung" section appears twice (lines 157-175 and 177-196). This appears to be duplicate content that may have been introduced during Crowdin synchronization.
🤖 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-connect/overview-and-setup.mdx` around lines 157 - 179, Remove the duplicated "## Lizenzverwaltung" block by keeping the first occurrence with the Tabs section (the header "## Lizenzverwaltung" followed by the paragraph and the <Tabs> containing <TabItem value="Banner"/ConnectChangeBanner>, <TabItem value="ordnen"/ConnectRearrangeDashboard>, and <TabItem value="Thema"/ConnectSwitchThemes>) and delete the second repeated "## Lizenzverwaltung" header and its repeated paragraph; ensure only one header+paragraph+Tabs sequence remains to avoid duplicate content.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx (1)
79-92:⚠️ Potential issue | 🔴 CriticalMalformed admonition syntax will break rendering.
The admonition block has broken syntax:
- Line 79:
:::tip[When "Wann Sie Tailscale Exit-Nodes verwenden sollten"has mismatched brackets and quotes- Line 92: A stray
]appears outside the admonitionThis will likely cause MDX parsing errors or incorrect rendering.
🐛 Proposed fix for admonition syntax
-:::tip[When "Wann Sie Tailscale Exit-Nodes verwenden sollten" +:::tip[Wann Sie Tailscale Exit-Nodes verwenden sollten] Erwägen Sie die Verwendung von %%Tailscale|tailscale%% Exit-Nodes für: - Sichern des ausgehenden Datenverkehrs von Ihrem Heimnetzwerk während des Reisens - Beibehalten konsistenter IP-Adressen für Dienste, die VPN-Verkehr blockieren - Nahtlose Integration mit bestehender %%Tailscale|tailscale%%-Infrastruktur ::: ### Konfigurieren von Tailscale Exit-Nodes Um einen %%Tailscale|tailscale%% Exit-Node für den ausgehenden Datenverkehr Ihres Servers einzurichten: -]🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx` around lines 79 - 92, The admonition block starting with ":::tip[When \"Wann Sie Tailscale Exit-Nodes verwenden sollten\"" has malformed brackets/quotes and a stray closing bracket `]`; fix by replacing the opening line with a valid admonition header (e.g., :::tip Wann Sie Tailscale Exit-Nodes verwenden sollten or :::tip[Wann Sie Tailscale Exit-Nodes verwenden sollten]) and remove the stray `]` after the paragraph so the block is properly opened and closed with :::; update the admonition title text around the %%Tailscale|tailscale%% token as needed to keep the translated title while ensuring balanced brackets and quotes.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx (1)
62-62:⚠️ Potential issue | 🟡 MinorUntranslated English content in Spanish documentation.
This paragraph about Mover logging appears to be in English while the rest of the document is in Spanish. This seems like content that was missed during translation.
🤖 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` at line 62, The paragraph starting "By default, diagnostics are automatically anonymized..." is still in English; translate it into Spanish while preserving the inline tokens and formatting (e.g., %%Mover|mover%%, %%syslog|syslog%% and the bold/italic headings ***Settings → Scheduler → Mover Settings***), so the sentence reads naturally in Spanish and keeps the special tokens and emphasis intact; update only the text content, not the tokens or Markdown structure.i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx (1)
291-291:⚠️ Potential issue | 🟡 MinorUntranslated English content in German documentation.
Line 291 contains English text that wasn't translated: "Delete
/boot/config/wireguard/autostartfrom your boot drive and reboot."🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx` at line 291, Replace the untranslated English sentence "Delete `/boot/config/wireguard/autostart` from your boot drive and reboot." in wireguard.mdx with a proper German translation—e.g. "Lösche `/boot/config/wireguard/autostart` von deinem Boot-Laufwerk und starte das System neu."—so the documentation is fully translated.
♻️ Duplicate comments (8)
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx (5)
91-99:⚠️ Potential issue | 🔴 CriticalCritical: CSS properties incorrectly translated to Spanish.
🔧 Fix
<div style={{ -margen: "auto", -maxAnchura: "600px", -display: "flex", -flexDirection: "columna", -alignItems: "centro", +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/system-administration/secure-your-server/wireguard.mdx` around lines 91 - 99, The inline style object on the div has Spanish-translated CSS keys/values (margen, maxAnchura, columna, centro) causing runtime/render errors; update the style object in that div to use correct JS/CSS names and values (e.g., margin, maxWidth, flexDirection: "column", alignItems: "center") while keeping display: "flex" and the max width numeric/px value as before so the layout renders correctly.
61-69:⚠️ Potential issue | 🔴 CriticalCritical: CSS properties and values incorrectly translated to Spanish.
First occurrence in this file - CSS must use English keywords.
🔧 Fix: Revert to English CSS syntax
<div style={{ -margen: "auto", -maxAnchura: "600px", -display: "flex", -flexDirection: "columna", -alignItems: "centro", +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/system-administration/secure-your-server/wireguard.mdx` around lines 61 - 69, CSS properties and values in the inline style object are mistakenly translated to Spanish; in the JSX <div> with the style object (keys like "margen", "maxAnchura", "flexDirection" and values "columna", "centro"), revert the keys and values to proper English CSS/React names and values: use "margin", "maxWidth", keep "display", set "flexDirection" to "column", and "alignItems" to "center" in that style object so the inline styles work correctly.
152-160:⚠️ Potential issue | 🔴 CriticalCritical: CSS properties incorrectly translated to Spanish.
🔧 Fix
<div style={{ -margen: "auto", -maxAnchura: "600px", -display: "flex", -flexDirection: "columna", -alignItems: "centro", +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/system-administration/secure-your-server/wireguard.mdx` around lines 152 - 160, The inline style object on the JSX <div> uses Spanish-translated property names and values (margen, maxAnchura, columna, centro) which are invalid; update the style keys to the correct React/CSS camelCase names and values: replace margen -> margin, maxAnchura -> maxWidth, flexDirection: "columna" -> "column", and alignItems: "centro" -> "center", keeping the existing values (e.g., "auto" and "600px") and preserving display: "flex".
108-116:⚠️ Potential issue | 🔴 CriticalCritical: CSS properties incorrectly translated to Spanish.
🔧 Fix
<div style={{ -margen: "auto", -maxAnchura: "600px", -display: "flex", -flexDirection: "columna", -alignItems: "centro", +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/system-administration/secure-your-server/wireguard.mdx` around lines 108 - 116, The inline style object on the JSX <div> uses Spanish-translated CSS keys and values (margen, maxAnchura, columna, centro) which are invalid in React; update the style object used in the div to use the correct JS/CSS property names and values: replace "margen" with "margin", "maxAnchura" with "maxWidth", set "flexDirection" to "column" (not "columna"), and set "alignItems" to "center" (not "centro"), keeping the existing values like "auto" and "600px" as appropriate.
125-133:⚠️ Potential issue | 🔴 CriticalCritical: CSS properties incorrectly translated to Spanish.
🔧 Fix
<div style={{ -margen: "auto", -maxAnchura: "600px", -display: "flex", -flexDirection: "columna", -alignItems: "centro", +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/system-administration/secure-your-server/wireguard.mdx` around lines 125 - 133, The inline style object on the JSX <div> has CSS property names and values translated to Spanish (e.g., margen, maxAnchura, columna, centro); update the style object used in the <div> so keys use valid React/CSS camelCase names (margin, maxWidth, display, flexDirection, alignItems) and values use correct English keywords where applicable (e.g., "column", "center"), preserving existing values like "auto" and "600px".i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx (1)
34-42:⚠️ Potential issue | 🔴 CriticalCritical: CSS properties and values incorrectly translated to Spanish.
CSS syntax in React inline styles must use English keywords.
🔧 Fix: Revert to English CSS syntax
<div style={{ -margen: "auto", -maxAnchura: "600px", -display: "flex", -flexDirection: "columna", -alignItems: "centro", +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/system-administration/secure-your-server/secure-your-outgoing-comms.mdx` around lines 34 - 42, The inline React style object on the div uses Spanish property names and values; change the keys and values to valid CSS-in-JS English identifiers: replace margen -> margin, maxAnchura -> maxWidth, keep display -> "flex", change flexDirection value "columna" -> "column", and change alignItems value "centro" -> "center" so the style object on the div renders correctly.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx (1)
29-37:⚠️ Potential issue | 🔴 CriticalCritical: CSS properties and values incorrectly translated to Spanish.
CSS property names and values in React inline styles must remain in English.
🔧 Fix: Revert to English CSS syntax
<div style={{ -margin: "auto", -maxWidth: "600px", -display: "flex", -flexDirection: "column", -alignItems: "center", +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/system-administration/secure-your-server/secure-your-boot-drive.mdx` around lines 29 - 37, The inline style object on the MDX <div> has CSS property names/values translated to Spanish; revert them to standard React inline style syntax (English camelCase property names and English string values) in the style prop for the <div> (look for the style={{ ... }} block with margin, maxWidth, display, flexDirection, alignItems) so all keys like maxWidth, flexDirection and values like "auto", "flex", "column", "center" are in English and correctly cased.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx (1)
4-10:⚠️ Potential issue | 🔴 CriticalCritical: CSS properties and values incorrectly translated to Spanish.
Same issue as in
wireguard-configure-mobile.mdx- CSS syntax must remain in English for React inline styles to function.🔧 Fix: Revert to English CSS syntax
<div style={{ -margen: "auto", -maxAnchura: "600px", -display: "flex", -flexDirection: "columna", -alignItems: "centro", +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/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx` around lines 4 - 10, The inline style object contains Spanish-translated CSS keys/values (margen, maxAnchura, flexDirection: "columna", alignItems: "centro") which breaks React styles; revert those to English names/values by changing margen → margin, maxAnchura → maxWidth, keep display: "flex", change flexDirection: "column" and alignItems: "center", and ensure values like "auto" and "600px" remain correct so the style object uses standard CSS identifiers.
🧹 Nitpick comments (23)
i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (1)
196-455: Use one language style consistently for section/admonition titles.Titles are currently mixed (e.g.,
VMマネージャー,Security 推奨,スケジューラー, plus many English headers). Please standardize heading/admonition language for a consistent Japanese-reading experience.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx` around lines 196 - 455, The document mixes Japanese and English in section and admonition titles (examples: headings "VMマネージャー", "スケューラー" vs. English "Network services", "User preferences", and admonition title "Security 推奨"); update all top-level and subhead headings and admonition titles to use a single language (Japanese) consistently—e.g., translate "Network services", "User preferences", "Notification Settings", "Scheduler", and admonition labels like ":::tip" / ":::warning" titles (currently "Security 推奨") into Japanese, and ensure Markdown/MDX heading strings and admonition text (the visible title parts) are consistently localized throughout the file so readers see only Japanese titles like "ネットワークサービス", "ユーザー設定", "通知設定", "スケジューラー", and matching admonition labels.i18n/ja/docusaurus-plugin-content-blog/options.json (1)
2-8: Consider using distinct title and description values.Both
titleanddescriptionfields use the identical message "ブログ". While this may be intentional, having distinct values could improve SEO. For example, the description could be more descriptive (e.g., "Unraidブログ" or a longer phrase).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-blog/options.json` around lines 2 - 8, The title and description keys in options.json currently both use the same Japanese message "ブログ"; update the description.message to a more descriptive, distinct string to improve SEO (for example "Unraidブログ" or a longer descriptive phrase). Locate the "title" and "description" entries in i18n/ja/docusaurus-plugin-content-blog/options.json and modify the "description"."message" value only (leave "title" as-is) so the two fields are not identical while keeping the description in Japanese and consistent with site branding.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.2.md (1)
1-1: Optional: Consider adjusting heading level.The static analysis tool suggests starting with a top-level heading (h1
#) instead of h2 (##). However, this may be intentional based on the documentation structure where the page title is managed by Docusaurus frontmatter.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.2.md` at line 1, The heading currently uses an h2 ("## バージョン 6.9.2 2021-04-07"); if this document should be the page title, change it to an h1 by replacing "## バージョン 6.9.2 2021-04-07" with "# バージョン 6.9.2 2021-04-07"; otherwise, if Docusaurus frontmatter already supplies the page title, leave the h2 as-is and ignore this change.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx (1)
6-7: Remove unused imports.The
TabsandTabItemcomponents are imported but never used in this document.♻️ Proposed fix
---- -sidebar_position: 4 -sidebar_label: Unraid as a VM ---- - -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -# Unraid as a VM +--- +sidebar_position: 4 +sidebar_label: Unraid as a VM +--- + +# Unraid as a VM🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx` around lines 6 - 7, Remove the unused imports by deleting the import statement that brings in the Tabs and TabItem symbols (remove "Tabs" and "TabItem" from the imports) so the module no longer imports `@theme/Tabs` and `@theme/TabItem`; update any import lines referencing Tabs or TabItem in the file (the import of Tabs and TabItem at the top of the document) to eliminate these unused symbols.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md (2)
44-46: Additional English text in Japanese document.Lines 44-46 also contain English text. Same consistency concern as lines 30-35.
Consider translating or documenting why this section remains in English.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md` around lines 44 - 46, The Japanese release-notes file contains an English sentence starting with "Note: if you previously used the [2-nic docker segmentation method]..." that breaks language consistency; either translate that sentence into Japanese or add a brief Japanese explanation stating why it remains in English (e.g., quoted English term/link kept for accuracy). Update the section around the quoted link text ("[2-nic docker segmentation method]") and the following sentence to be fully Japanese, or add a Japanese parenthetical note clarifying the retention of the English phrase so the document remains consistent.
30-35: English text in Japanese document.Lines 30-35 contain English text within an otherwise Japanese document. This appears to provide technical guidance about Docker network settings, but breaks the language consistency.
Consider translating this section to Japanese or adding a note indicating why it's in English (e.g., if it's a direct quote from official documentation that should remain in English).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md` around lines 30 - 35, The paragraph about switching "Docker custom network type" from macvlan to ipvlan (containing "Settings > Docker", "Docker custom network type", "macvlan", "ipvlan", and the link to [the next section](`#system-drivers-page`)) is in English inside a Japanese doc; translate that entire block into natural Japanese (or, if it must remain verbatim, prepend a short Japanese note explaining why it's left in English) so the section language matches the rest of the document while preserving the technical terms and the link target.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md (2)
1-1: Consider using h1 for the main version heading.The first line uses
##(h2) instead of#(h1). While this doesn't break functionality, using h1 for the main document heading is a common Markdown convention.📝 Proposed adjustment
-## バージョン 6.9.1 2021-03-08 +# バージョン 6.9.1 2021-03-08🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md` at line 1, The document's top-level heading currently uses "## バージョン 6.9.1 2021-03-08" (an h2); change it to a top-level h1 by replacing the leading "##" with "#" so the main version heading becomes "# バージョン 6.9.1 2021-03-08" to follow standard Markdown heading conventions.
29-29: Heading level jumps from h2 to h4.Line 29 uses
####(h4) directly under##(h2) sections, skipping h3. This violates the heading hierarchy convention where levels should increment by one.📝 Proposed adjustment
-#### ベースディストリビューション +### ベースディストリビューションApply the same change to other h4 headings in the changelog section (lines 35, 41).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.1.md` at line 29, Change the heading "#### ベースディストリビューション" to an h3 (### ベースディストリビューション) so it follows the h2 -> h3 hierarchy, and apply the same adjustment for the other h4 headings in the changelog section (the headings currently using "####" at the same block, e.g., the ones around lines with texts following this section) so all h4s under the h2 are converted to h3.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/_category_.json (1)
1-4: Consider addinglinkproperty for consistency.This category config is missing the
linkproperty that other category files in this PR include (e.g.,i18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/_category_.jsonandi18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/_category_.jsonboth define"link": { "type": "generated-index" }). If this omission is intentional, it's fine, but if not, adding it would ensure consistency across category pages.📝 Proposed addition for consistency
{ "label": "トラブルシューティング", - "position": 5 + "position": 5, + "link": { + "type": "generated-index" + } }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/_category_.json` around lines 1 - 4, The category JSON for the "トラブルシューティング" label is missing a "link" property for consistency with other category files; update the _category_.json for the unraid-os/troubleshooting category by adding a "link" entry (e.g., "link": { "type": "generated-index" }) alongside the existing "label" and "position" so the category behaves like the other files that define generated indexes.i18n/ja/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx (1)
141-164:trapの登録位置が遅く、失敗時にキー削除が走らない可能性がありますLine 163 で
trapを設定していますが、Line 145-160 のどこかで失敗するとset -eで終了し、クリーンアップが未登録のままになります。trapはAPIキー作成直後に登録してください。Diff案
#!/bin/bash set -e # 1. Create temporary API key echo "Creating temporary API key..." KEY_DATA=$(unraid-api apikey --create \ --name "temp deployment key" \ --roles ADMIN \ --description "Temporary key for deployment $(date)" \ --json) # 2. Extract the API key API_KEY=$(echo "$KEY_DATA" | jq -r '.key') echo "API key created successfully" + +# Ensure cleanup is always registered before further operations +trap 'echo "Cleaning up..."; unraid-api apikey --delete --name "temp deployment key"' EXIT # 3. Use the key for operations echo "Configuring services..." curl -H "Authorization: Bearer $API_KEY" \ -H "Content-Type: application/json" \ -d '{"provider": "azure", "clientId": "your-client-id"}' \ http://localhost:3001/graphql -# 4. Clean up (always runs, even on error) -trap 'echo "Cleaning up..."; unraid-api apikey --delete --name "temp deployment key"' EXIT - echo "Deployment completed successfully"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx` around lines 141 - 164, The trap for cleanup is registered too late and may not run if KEY_DATA creation fails; move the trap registration to immediately after creating the API key (after KEY_DATA is assigned and before extracting API_KEY) so the EXIT handler (trap 'echo "Cleaning up..."; unraid-api apikey --delete --name "temp deployment key"' EXIT) is guaranteed to be installed once the key exists; ensure references to KEY_DATA, API_KEY, and the unraid-api apikey --create call remain unchanged and that the trap still deletes the same named key.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md (1)
276-276: Use unique subsection headings to avoid duplicate anchors.
### その他の変更is repeated multiple times, which creates auto-suffixed anchors and makes stable linking harder. Consider context-specific titles (e.g., 「Docker のその他の変更」).Also applies to: 304-304, 379-379, 405-405
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md` at line 276, The repeated heading "### その他の変更" creates duplicate anchors; update each occurrence of that exact heading in this doc to a unique, context-specific subsection title (for example, rename to "### Docker のその他の変更", "### ネットワークのその他の変更", etc.), ensuring any changed headings remain concise and reflect the section content so anchors become stable and links remain predictable.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx (1)
1-68: This file appears to be untranslated.The sidebar label and all content remain in English, while other Japanese documentation files in this PR (e.g.,
unraid-net.mdx,licensing-faq.mdx) have Japanese translations for both labels and content. This creates an inconsistent user experience in the Japanese documentation.If this is intentional (e.g., awaiting Crowdin translation), consider adding a note or ensuring the file follows the same pattern as other translated files.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx` around lines 1 - 68, The file's frontmatter (sidebar_label) and all page content are still in English while other Japanese docs are translated; update the frontmatter sidebar_label and translate the MDX body (title "Internal Boot FAQ (7.3+)", headings like "I switched from flash boot..." and all paragraph text including details and video captions) into Japanese following the same translation style/pattern used in unraid-net.mdx and licensing-faq.mdx, or if intentional, add a clear translation-pending note at the top consistent with other files awaiting Crowdin; ensure the translated sidebar_label and TOC headings match the other Japanese files' conventions before committing.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/unraid-net.mdx (1)
12-12: Untranslated line in Japanese documentation.Line 12 remains in English while the surrounding content (lines 13-17) is translated to Japanese. For consistency:
-- **%%Single Sign-On (SSO)|sso%%:** Access Unraid's systems with one set of credentials. +- **%%シングルサインオン (SSO)|sso%%:** 1つの認証情報でUnraidのシステムにアクセスできます。🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/unraid-net.mdx` at line 12, Replace the untranslated English bold line "**%%Single Sign-On (SSO)|sso%%:**: Access Unraid's systems with one set of credentials." with a Japanese translation while preserving the shortcode/placeholder and formatting; e.g. keep the exact token "%%Single Sign-On (SSO)|sso%%" and surrounding "**" and ":" then provide the Japanese text such as "単一の資格情報でUnraidのシステムにアクセスできます。" so the final line reads like "**%%Single Sign-On (SSO)|sso%%:** 単一の資格情報でUnraidのシステムにアクセスできます。"i18n/ja/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx (1)
1-78: File contains no Japanese translation.This file is placed in the Japanese i18n directory (
i18n/ja/...) but contains entirely English content. The frontmattertitleanddescription, as well as all page content, are in English.If this is intentional as a fallback while awaiting Crowdin translation, this is acceptable. However, for consistency with other translated files in this PR (like
licensing-faq.mdxwhich has partial translations), consider adding at minimum the Japanese frontmatter translations.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx` around lines 1 - 78, The file's content and frontmatter (title and description) are entirely in English but live in the Japanese i18n folder; update the frontmatter keys "title" and "description" to their Japanese equivalents and either provide a full Japanese translation of the page body (translate headings like "How to Redeem Your Activation Code", "For Unraid 6.10 and later", "For Upgrade Activation Codes", "For Unraid 6.9 and older", "Alternative: Redeem via Account Dashboard", "Important Notes", and "Need Help?") or, if you intend to keep English as a fallback, add Japanese frontmatter translations and a short note indicating the page is pending Crowdin translation to maintain consistency with other i18n files.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (2)
16-27: Multiple section headers and content remain untranslated.Several elements in this Japanese localization file are still in English:
- Line 16: "Connect to the Unraid WebGUI"
- Lines 20-21: Bullet point content
- Lines 23-27: The
:::importantadmonition contentThis creates an inconsistent reading experience. Consider completing the Japanese translation for these sections.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 16 - 27, The Japanese localization still contains untranslated English strings in the "Connect to the Unraid WebGUI" section; update the header text "Connect to the Unraid WebGUI", the two bullet points describing "GUI Mode" and "Web Browser" (including `root` username and `http://tower.local` example and the %%WebGUI|web-gui%% / %%mDNS|mdns%% tokens), and the :::important admonition paragraph so all user-facing copy is fully translated into Japanese while preserving tokens and examples exactly (e.g., keep `root`, `http://tower.local`, and the %%...%% tokens intact); ensure translation matches surrounding tone and format in deploy-and-configure-unraid-os.mdx.
10-14: Untranslated content in Japanese documentation file.This admonition about localization is ironically left untranslated in the Japanese documentation. The content on lines 11-13 remains entirely in English, which creates an inconsistent user experience for Japanese readers.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 10 - 14, The info admonition using :::info[Localize] contains English text that should be translated into Japanese; replace the English sentences between the admonition markers with a Japanese translation while preserving the admonition marker (:::info[Localize]), the relative link reference ([Multi-language support](../../using-unraid-to/customize-your-experience/multi-language-support.mdx)), and the localization token %%WebGUI|web-gui%% exactly as-is so links and tokens still resolve correctly in deploy-and-configure-unraid-os.mdx.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx (2)
37-39: Section header untranslated.Line 37 "Events that cause unclean shutdowns" and line 39's content remain in English while the surrounding content is in Japanese.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx` around lines 37 - 39, Translate the untranslated English section header "## Events that cause unclean shutdowns" and its following paragraph content ("Understanding the main triggers for unclean shutdowns helps you prevent them. The following sections cover the most common scenarios and their solutions.") into Japanese so they match the surrounding locale; update the header string and the paragraph text in unclean-shutdowns.mdx (look for the exact header "Events that cause unclean shutdowns" and the subsequent sentence) to appropriate Japanese equivalents while preserving markdown heading level and sentence meaning.
13-13: Inconsistent admonition title mixing English and Japanese.The admonition title
[Recommendations 不適切なシャットダウンを防ぐためmixes English "Recommendations" with Japanese text. For consistency, this should be fully translated to Japanese.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx` at line 13, Replace the mixed-language admonition title string ":::important[Recommendations 不適切なシャットダウンを防ぐため" with a fully Japanese title; locate the admonition starting token ":::important[Recommendations 不適切なシャットダウンを防ぐため" and update the bracketed title to a Japanese-only phrase such as ":::important[推奨事項 — 不適切なシャットダウンを防ぐため]" (or ":::important[推奨事項：不適切なシャットダウンを防ぐため]") so the admonition title is consistently Japanese.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx (1)
61-61: Mixed language in admonition title.The admonition title
[Reducing セキュリティ上のリスク]mixes English "Reducing" with Japanese. Consider using fully Japanese text for consistency:[セキュリティリスクの軽減].🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx` at line 61, Replace the mixed-language admonition title "Reducing セキュリティ上のリスク" in the MDX admonition (the text inside :::important[...]) with a fully Japanese title; update the bracketed label to "セキュリティリスクの軽減" so the admonition title is consistently Japanese (search for the admonition token containing "Reducing セキュリティ上のリスク" to locate the exact spot).i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx (1)
37-37: Mixed language in admonition titles.Lines 37 and 47 have admonition titles mixing English and Japanese:
[Other RAMテストツール][If RAMエラーが見つかった場合]For consistency, consider fully translating these titles to Japanese.
Also applies to: 47-47
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx` at line 37, Replace the mixed-language admonition titles with fully Japanese titles: change "Other RAMテストツール" to "その他のRAMテストツール" and change "If RAMエラーが見つかった場合" to a fully Japanese variant such as "RAMエラーが見つかった場合" (or "RAMエラーが見つかった場合の対処"), updating the corresponding admonition markers in the MDX so both admonitions use consistent Japanese-only titles.i18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (1)
71-72: Clarify backup scope wording to prevent restore-flow confusion.Line 71 says this is not a full copy, but the restore flow later uses a generated ZIP for USB Creator restoration. Consider wording that explicitly distinguishes “not a raw device image” from “includes OS release + required config”.
Based on learnings: Unraid's flash backup feature creates complete installation ZIP files that include both the Unraid OS and user configuration, and these ZIPs are compatible with the USB Flash Creator's "Use custom" option.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx` around lines 71 - 72, Update the wording at the "Flash backup is designed to store essential configuration files..." paragraph to explicitly state this backup is not a raw device or block-level image but rather a generated ZIP that includes the Unraid OS release plus required user configuration (plugin settings, config files) and is compatible with the USB Flash Creator "Use custom" workflow; mention transient files and large binaries are excluded and individual file and total-size limits still apply to avoid restore-flow confusion.i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx (2)
135-147: Mixed language in admonition labels appears inconsistent.The admonition labels mix English and Japanese in an unusual way:
- Line 135:
:::tip[General ヒント]- Line 143:
:::info[Always 変更]These appear to be partially translated. Consider fully translating to Japanese or keeping fully in English for consistency:
🌐 Suggested translation fixes
-:::tip[General ヒント] +:::tip[一般的なヒント]-:::info[Always 変更] +:::info[常に変化]🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx` around lines 135 - 147, The admonition labels are mixed English/Japanese (:::tip[General ヒント] and :::info[Always 変更]); change them to fully Japanese (e.g., replace :::tip[General ヒント] with :::tip[一般的なヒント] and :::info[Always 変更] with :::info[常に]) or choose fully English equivalents, and apply the same language consistency to any other admonition markers in this file (look for :::tip, :::info, etc.).
88-96: Several sections left in English within Japanese document.Lines 88-96 (VM resources table content and bullets) are in English. If this is intentional for technical terms, it's acceptable. However, the pattern is inconsistent with other translated tables in this document.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx` around lines 88 - 96, Translate the English table rows and following bullets into Japanese while leaving placeholders unchanged (%%VM\|vm%%, %%VMs|vm%%, %%GPU passthrough\|gpu-passthrough%%); e.g., replace "Virtual server" with "仮想サーバー", "Virtual desktop" with "仮想デスクトップ", "Hybrid/gaming %%VM\|vm%%" with "ハイブリッド/ゲーミング %%VM\|vm%%", convert examples ("Lightweight Linux, utility %%VMs|vm%%" → "軽量Linux、ユーティリティ%%VMs|vm%%", "Windows 11, Ubuntu desktop, RDP" → "Windows 11、Ubuntuデスクトップ、RDP", "%%GPU passthrough\|gpu-passthrough%%, gaming, ML" → "%%GPU passthrough\|gpu-passthrough%%、ゲーム、機械学習"), and translate the three bullets into natural Japanese (keeping technical placeholders intact) so the section matches the rest of the document’s localization.
| margen: "auto", | ||
| maxAnchura: "600px", | ||
| display: "flex", | ||
| flexDirection: "columna", | ||
| alignItems: "centro", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Find the file in the repository
find . -name "zfs-storage.mdx" -type f 2>/dev/nullRepository: unraid/docs
Length of output: 708
🏁 Script executed:
#!/bin/bash
# Check file size and read specific line ranges
if [ -f "i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx" ]; then
wc -l "i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx"
fiRepository: unraid/docs
Length of output: 172
🏁 Script executed:
#!/bin/bash
# Read lines 43-47 and several other mentioned ranges to verify the issue
FILE="i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx"
if [ -f "$FILE" ]; then
echo "=== Lines 43-47 ==="
sed -n '43,47p' "$FILE"
echo ""
echo "=== Lines 71-75 ==="
sed -n '71,75p' "$FILE"
echo ""
echo "=== Lines 92-96 ==="
sed -n '92,96p' "$FILE"
echo ""
echo "=== Lines 113-117 ==="
sed -n '113,117p' "$FILE"
fiRepository: unraid/docs
Length of output: 547
🏁 Script executed:
#!/bin/bash
FILE="i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx"
# Check all mentioned line ranges
for range in "127-131" "142-146" "162-166" "174-178" "212-216" "226-230" "247-251" "295-299" "331-335" "356-360" "402-406" "421-425"; do
echo "=== Lines $range ==="
sed -n "${range}p" "$FILE" | head -5
doneRepository: unraid/docs
Length of output: 959
🏁 Script executed:
#!/bin/bash
FILE="i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx"
# Count occurrences of Spanish property names in the file
echo "Spanish property name occurrences:"
echo "margen: $(rg 'margen:' "$FILE" | wc -l)"
echo "maxAnchura: $(rg 'maxAnchura:' "$FILE" | wc -l)"
echo "columna: $(rg 'columna' "$FILE" | wc -l)"
echo "centro: $(rg 'centro' "$FILE" | wc -l)"Repository: unraid/docs
Length of output: 138
Revert all JSX style blocks to use standard English CSS property names instead of Spanish translations.
The file contains 16 style blocks using non-standard Spanish property names (margen, maxAnchura, columna, centro) which CSS will not recognize, breaking all layout and spacing rules. Replace with standard English equivalents: margin, maxWidth, column, center.
Replacement pattern for all style blocks
style={{
-margen: "auto",
-maxAnchura: "600px",
+margin: "auto",
+maxWidth: "600px",
display: "flex",
-flexDirection: "columna",
-alignItems: "centro",
+flexDirection: "column",
+alignItems: "center",
}}Affects lines: 43-47, 71-75, 92-96, 113-117, 127-131, 142-146, 162-166, 174-178, 212-216, 226-230, 247-251, 295-299, 331-335, 356-360, 402-406, 421-425
📝 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.
| margen: "auto", | |
| maxAnchura: "600px", | |
| display: "flex", | |
| flexDirection: "columna", | |
| alignItems: "centro", | |
| 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/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 43 - 47, The JSX style blocks in
unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx use Spanish
CSS property names (margen, maxAnchura, columna, centro) which are invalid;
replace them across all style objects with the English equivalents: change
"margen" to "margin", "maxAnchura" to "maxWidth", set "flexDirection: 'columna'"
to "flexDirection: 'column'", and "alignItems: 'centro'" to "alignItems:
'center'"; update every style block (occurrences around the specified ranges)
and verify components or elements using those style objects (the inline style
objects in the MDX) render correctly after the rename.
| margen: "auto", | ||
| maxAnchura: "600px", | ||
| display: "flex", | ||
| flexDirection: "columna", | ||
| alignItems: "centro", | ||
| }} |
There was a problem hiding this comment.
Invalid React style properties will cause layout to break.
Same issue as other Spanish files: the style object uses Spanish translations of CSS property names that React will not recognize. The image container will not be styled correctly.
🐛 Proposed fix
style={{
-margen: "auto",
-maxAnchura: "600px",
-display: "flex",
-flexDirection: "columna",
-alignItems: "centro",
+margin: "auto",
+maxWidth: "600px",
+display: "flex",
+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.
| margen: "auto", | |
| maxAnchura: "600px", | |
| display: "flex", | |
| flexDirection: "columna", | |
| alignItems: "centro", | |
| }} | |
| 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/system-administration/maintain-and-update/partials/backup-using-webgui.mdx`
around lines 10 - 15, The inline style object uses Spanish property names and
values (margen, maxAnchura, columna, centro) which React won't recognize; update
the style object used for the image container (the object containing margen,
maxAnchura, display, flexDirection, alignItems) to use valid React/CSS-in-JS
property names and values: margin, maxWidth, display, flexDirection with value
"column", and alignItems with value "center" (keep values like "auto" and
"600px" as strings).
| style={{ | ||
| margen: "auto", | ||
| maxAnchura: "600px", | ||
| display: "flex", | ||
| flexDirection: "columna", | ||
| alignItems: "centro", | ||
| margen: "auto", | ||
| maxAnchura: "600px", | ||
| display: "flex", | ||
| flexDirection: "columna", | ||
| alignItems: "centro", | ||
| }} |
There was a problem hiding this comment.
Invalid React style properties will cause layout to break.
Same issue as other Spanish files: the style objects use Spanish translations of CSS property names (margen, maxAnchura, flexDirection: "columna", alignItems: "centro"). React requires the actual English property names and values.
This pattern repeats at lines 24-30 and 40-46.
🐛 Proposed fix for all three style blocks
style={{
-margen: "auto",
-maxAnchura: "600px",
-display: "flex",
-flexDirection: "columna",
-alignItems: "centro",
+margin: "auto",
+maxWidth: "600px",
+display: "flex",
+flexDirection: "column",
+alignItems: "center",
}}Apply this fix to all three <div> style blocks in the file.
📝 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.
| style={{ | |
| margen: "auto", | |
| maxAnchura: "600px", | |
| display: "flex", | |
| flexDirection: "columna", | |
| alignItems: "centro", | |
| margen: "auto", | |
| maxAnchura: "600px", | |
| display: "flex", | |
| flexDirection: "columna", | |
| alignItems: "centro", | |
| }} | |
| 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/system-administration/maintain-and-update/partials/replacement-using-creator.mdx`
around lines 8 - 14, The inline React style objects use Spanish property names
and values which break layout; update each of the three style blocks (the
style={{ ... }} objects) to use the correct English CSS-in-JS names and values:
replace margen → margin, maxAnchura → maxWidth, flexDirection: "columna" →
flexDirection: "column", and alignItems: "centro" → alignItems: "center"; apply
the same corrections to the other two style={{ ... }} blocks in this file so all
three divs use valid React style properties.
| style={{ | ||
| margen: "auto", | ||
| maxAnchura: "600px", | ||
| display: "flex", | ||
| flexDirection: "columna", | ||
| alignItems: "centro", | ||
| margen: "auto", | ||
| maxAnchura: "600px", | ||
| display: "flex", | ||
| flexDirection: "columna", | ||
| alignItems: "centro", | ||
| }} |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Search for Spanish CSS properties in style objects across i18n files
rg -n -A2 -B2 'style=\{\{' i18n/es/ | rg -i '(margen|maxAnchura|columna|centro)' -C3Repository: unraid/docs
Length of output: 30504
Critical: CSS properties and values incorrectly translated to Spanish across multiple files.
React inline styles require CSS property names in English camelCase and standard CSS keyword values. The Spanish translations (margen, maxAnchura, columna, centro) will cause styling to fail silently. This pattern affects at least 25 files in the Spanish translations.
Fix: Revert to English CSS syntax
<div
style={{
-margen: "auto",
-maxAnchura: "600px",
-display: "flex",
-flexDirection: "columna",
-alignItems: "centro",
+margin: "auto",
+maxWidth: "600px",
+display: "flex",
+flexDirection: "column",
+alignItems: "center",
}}
>Configure Crowdin to exclude CSS properties and inline style objects from translation. This is a systemic issue affecting the entire Spanish translation.
📝 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.
| style={{ | |
| margen: "auto", | |
| maxAnchura: "600px", | |
| display: "flex", | |
| flexDirection: "columna", | |
| alignItems: "centro", | |
| margen: "auto", | |
| maxAnchura: "600px", | |
| display: "flex", | |
| flexDirection: "columna", | |
| alignItems: "centro", | |
| }} | |
| 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/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx`
around lines 4 - 10, The inline style object in the component uses
Spanish-translated CSS properties/values (margen, maxAnchura, columna, centro)
which must be reverted to English camelCase and standard CSS keywords; update
the style object keys to margin, maxWidth, display, flexDirection and alignItems
and use values like "auto", "600px", "flex", "column", "center" respectively so
React inline styles work; also add a Crowdin rule to exclude inline style
objects and CSS property names from translation to prevent the same issue across
other Spanish files (search for occurrences of the style object keys 'margen',
'maxAnchura', 'columna', 'centro' to locate affected files).
| margen: "auto", | ||
| maxAnchura: "600px", | ||
| display: "flex", | ||
| flexDirection: "columna", | ||
| alignItems: "centro", | ||
| }} |
There was a problem hiding this comment.
Invalid React style properties will cause layout to break.
The style object uses Spanish translations of CSS property names (margen, maxAnchura, flexDirection: "columna", alignItems: "centro"), but React/CSS requires the actual English property names and values. These will be silently ignored by React, causing the layout styling to not apply.
🐛 Proposed fix to use valid CSS properties
style={{
-margen: "auto",
-maxAnchura: "600px",
-display: "flex",
-flexDirection: "columna",
-alignItems: "centro",
+margin: "auto",
+maxWidth: "600px",
+display: "flex",
+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.
| margen: "auto", | |
| maxAnchura: "600px", | |
| display: "flex", | |
| flexDirection: "columna", | |
| alignItems: "centro", | |
| }} | |
| 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 44 - 49, The inline style object contains Spanish CSS keys/values
(margen, maxAnchura, flexDirection: "columna", alignItems: "centro") which React
will ignore; update the style object used in the MDX component to use valid
React/CSS names and values—replace margen with margin, maxAnchura with maxWidth,
flexDirection: "column", and alignItems: "center" (keeping margin: "auto" and
maxWidth: "600px" as before) so the layout styles are applied correctly.
| margen: "auto", | ||
| maxAnchura: "600px", | ||
| display: "flex", | ||
| flexDirection: "columna", | ||
| alignItems: "centro", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Search for Spanish CSS property names in i18n MDX files to identify similar translation errors
# Check for common Spanish CSS translations that should remain in English
echo "Checking for translated CSS properties in i18n files..."
echo ""
echo "=== Searching for 'margen:' (should be 'margin:') ==="
rg -n 'margen:' --glob 'i18n/**/*.mdx'
echo ""
echo "=== Searching for 'maxAnchura:' (should be 'maxWidth:') ==="
rg -n 'maxAnchura:' --glob 'i18n/**/*.mdx'
echo ""
echo "=== Searching for 'columna' in flexDirection (should be 'column') ==="
rg -n 'flexDirection.*columna' --glob 'i18n/**/*.mdx'
echo ""
echo "=== Searching for 'centro' in alignItems (should be 'center') ==="
rg -n 'alignItems.*centro' --glob 'i18n/**/*.mdx'Repository: unraid/docs
Length of output: 24478
Fix invalid CSS translations in JSX style objects.
CSS property names and values in JSX style objects must always remain in English. Lines 8-12 contain Spanish translations that render them invalid:
margen→marginmaxAnchura→maxWidthflexDirection: "columna"→"column"alignItems: "centro"→"center"
This breaks styling entirely and affects 40+ Spanish translation files across the codebase.
Fix
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.
| margen: "auto", | |
| maxAnchura: "600px", | |
| display: "flex", | |
| flexDirection: "columna", | |
| alignItems: "centro", | |
| 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/partials/syslog-server/remote.mdx`
around lines 8 - 12, The JSX style object contains Spanish translations that
break CSS — replace the keys and values so they are valid English CSS: change
margen to margin, maxAnchura to maxWidth, flexDirection: "columna" to
flexDirection: "column", and alignItems: "centro" to alignItems: "center"
(update the style object used in the remote.mdx snippet where these properties
appear).
|
|
||
| Unraid supports %%ZFS|zfs%% for any storage pool. You can create a new %%ZFS|zfs%% pool, import one from another system, or use Unraid’s unique hybrid %%ZFS|zfs%% setup: add a %%ZFS|zfs%%-formatted disk directly to the Unraid %%array|array%% (not a pool) and combine %%ZFS|zfs%% features with Unraid’s %%parity|parity%% protection. | ||
|
|
||
| :::info\[Example] |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify malformed escaped admonition titles are not present
rg -n ':::[a-zA-Z]+\\\[' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
# Expected: no matchesRepository: unraid/docs
Length of output: 75
Fix invalid admonition syntax at Line 35.
:::info\[Example] contains an escaped bracket that breaks Docusaurus admonition parsing. Remove the backslash escape.
Syntax fix
-:::info\[Example]
+:::info[Example]🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
at line 35, The admonition marker ':::info\[Example]' uses an escaped bracket
which breaks Docusaurus parsing; update the admonition to use a normal bracket
(change ':::info\[Example]' to ':::info[Example]') so the admonition syntax is
valid in the ZFS storage doc (look for the literal string ':::info\[Example]' in
the file and replace it).
| sidebar_label: 起動可能なメディアを作成する | ||
| --- | ||
|
|
||
| import FlashDriveGuidance from '../../partials/flash-drive-selection-guidance.mdx'; |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify the partial file exists in the Japanese i18n directory
fd -t f "flash-drive-selection-guidance.mdx" i18n/ja
# Also check if it exists in the source docs for fallback
fd -t f "flash-drive-selection-guidance.mdx" docsRepository: unraid/docs
Length of output: 113
Fix broken partial import path in Japanese translation file.
The import on line 6 references a partial file that does not exist in the Japanese i18n directory structure:
import FlashDriveGuidance from '../../partials/flash-drive-selection-guidance.mdx';The file exists only at docs/unraid-os/partials/flash-drive-selection-guidance.mdx (source docs), not at the expected path i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/partials/flash-drive-selection-guidance.mdx. Either create the partial in the Japanese i18n structure or adjust the import path to reference the source docs directory.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx`
at line 6, The Japanese translation file imports a non-existent partial via
"import FlashDriveGuidance from
'../../partials/flash-drive-selection-guidance.mdx';" — either create the
missing partial copy under the Japanese i18n partials folder or update the
import in create-your-bootable-media.mdx to point at the upstream source partial
(docs/unraid-os/partials/flash-drive-selection-guidance.mdx) so
FlashDriveGuidance resolves; modify the import line in the file to reference the
chosen location accordingly.
| 変更: | ||
|
|
||
| - 既定の network.cfg 設定を使用している場合のトンネル設定の問題を修正しました。 | ||
| - ルート設定の টাইपोを修正。 |
There was a problem hiding this comment.
Critical translation error: Bengali script in Japanese document.
Line 26 contains Bengali script "টাইপো" instead of Japanese. This breaks the language consistency and will confuse Japanese readers.
🔧 Proposed fix
Replace the Bengali text with proper Japanese:
-- ルート設定の টাইপোを修正。
+- ルート設定のタイポを修正。Alternative (using kanji):
-- ルート設定の টাইপোを修正。
+- ルート設定の誤字を修正。📝 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.
| - ルート設定の টাইपोを修正。 | |
| - ルート設定のタイポを修正。 |
| - ルート設定の টাইपोを修正。 | |
| - ルート設定の誤字を修正。 |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.11.2.md`
at line 26, Replace the Bengali token "টাইপো" in the Japanese sentence "ルート設定の
টাইপোを修正。" with proper Japanese — for example change it to "ルート設定のタイプミスを修正。" or
"ルート設定の誤字を修正。" — updating the string in the document so the line reads correctly
in Japanese.
| :::note[Principle の最小権限 | ||
|
|
||
| 最小権限の原則とは、ユーザーやデバイスに、タスクの実行に必要な最小限のアクセスのみを付与し、それ以上は与えないことです。このアプローチは、侵害されたアカウントや誤操作による潜在的な被害を抑え、ゼロトラストモデルを含む現代のセキュリティにおける中核的な概念です。Unraid の設定全体、特に共有ユーザーの作成や権限の割り当てで、この原則を適用してください。 | ||
|
|
||
| ::: |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify malformed admonition titles and escaped-title patterns in JA MDX docs.
rg -nP ':::[a-zA-Z]+\[[^\]]*$|:::[a-zA-Z]+\\\[' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdxRepository: unraid/docs
Length of output: 101
🏁 Script executed:
cat -n i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx | head -20Repository: unraid/docs
Length of output: 880
🏁 Script executed:
sed -n '60,65p' i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx | cat -nRepository: unraid/docs
Length of output: 437
Malformed admonition syntax in two locations will break MDX rendering.
Line 8 is missing the closing bracket in the title: change :::note[Principle の最小権限 to :::note[Principle の最小権限].
Line 62 has an incorrectly escaped bracket: change :::note\[Example] to :::note[Example].
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/ja/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx`
around lines 8 - 12, Fix the malformed MDX admonitions: close the missing
bracket on the first admonition by changing the title token to :::note[Principle
の最小権限] (replacing :::note[Principle の最小権限) and unescape the second admonition so
it reads :::note[Example] instead of :::note\[Example]; ensure both admonition
lines use the exact :::note[...] form so MDX rendering succeeds.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
unraid-docs | 89f248f | Apr 02 2026, 04:47 PM |
1 participant
Summary by CodeRabbit
New Features
Documentation