New Crowdin updates

[elibosley]

Summary by CodeRabbit

Release Notes

• Documentation & Guides

  • Enhanced documentation across all languages with improved navigation anchors and expanded step-by-step procedures.
  • Added descriptive guidance for API, CLI, OIDC setup, and configuration sections.

• Release Information

  • Published comprehensive release notes for Unraid OS 7.2.4 with security updates and bug fixes.
  • Updated release notes with improved internal linking for easier reference.

• User Interface Improvements

  • Introduced tabbed interfaces for backup methods and safe mode troubleshooting.
  • Reorganized and clarified storage management, network configuration, and VM setup procedures.

• Localization

  • Expanded multi-language support with improved translations and localized guidance in German, Spanish, French, and Chinese.

[coderabbitai]

Actionable comments posted: 9

Note

Due to the large number of review comments, Critical severity comments were prioritized as inline comments.

♻️ Duplicate comments (13)

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx (1)

14-36: ⚠️ Potential issue | 🔴 Critical

Both style blocks still use localized (invalid) JSX property names — layout broken.

Both <div> style objects carry the same untranslated keys from the previous review. React ignores them silently.

🐛 Proposed fix (apply to both occurrences)

-    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/system-administration/maintain-and-update/partials/replacement-manual-method.mdx`
around lines 14 - 36, The two JSX <div> style objects (the ones using keys like
margen, maxAnchura, flexDirection: "columna", alignItems: "centro") use
localized property names and values so React ignores them; update both
occurrences to use valid React style keys and values — replace margen with
margin, maxAnchura with maxWidth, set flexDirection to "column" (not "columna")
and alignItems to "center" (not "centro") so the layout styles in those <div>
elements take effect.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx (1)

4-12: ⚠️ Potential issue | 🔴 Critical

Localized JSX style property names still break layout.

The style object still uses Spanish-translated keys (margen, maxAnchura) and values ("columna", "centro"). React silently ignores unrecognized property names, so the div will render with no centering, no max-width, and no flex layout.

🐛 Proposed fix

 <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/system-administration/maintain-and-update/partials/backup-using-webgui.mdx`
around lines 4 - 12, The style object on the JSX <div> uses Spanish keys/values
(e.g., margen, maxAnchura, "columna", "centro") which React ignores; update the
style object inside that <div> (the inline style passed to the div) to use the
correct English CSS-in-JS property names and values: margin, maxWidth (e.g.,
"600px"), display: "flex", flexDirection: "column", and alignItems: "center" so
the centering and flex layout take effect.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (2)

302-302: ⚠️ Potential issue | 🔴 Critical

Fix unresolved image path causing MDX compile failure.

Line 302 references /img/zfs12.png, which CI reports as missing. Keep image paths consistent with this page’s existing ./assets/... references (or ensure the file exists under static/img before using /img/...).

✅ Minimal safe fix

-![](/img/zfs12.png)
+![](./assets/zfs12.png)

🤖 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`
at line 302, The MDX contains a broken image reference "![](/img/zfs12.png)"
causing CI to fail; fix by replacing that path with the page's local asset path
(e.g. "./assets/zfs12.png") to match other asset references on this doc, or
alternatively add the missing file to the site's static/img directory if you
intend to keep the absolute "/img/..." URL; update the reference in the
zfs-storage.mdx content accordingly.

---

42-47: ⚠️ Potential issue | 🔴 Critical

Use valid React style keys/values in all JSX style objects.

At Line 42 and the listed blocks, margen, maxAnchura, "columna", and "centro" are not valid React/CSS style keys/values, so those rules are ignored at render time.

🐛 Representative fix (apply consistently to all listed blocks)

 style={{
- margen: "auto",
- maxAnchura: "600px",
+ margin: "auto",
+ maxWidth: "600px",
  display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
+ flexDirection: "column",
+ alignItems: "center",
 }}

#!/bin/bash
# Verify invalid React style tokens are fully removed from this file.
rg -n 'margen|maxAnchura|flexDirection:\s*"columna"|alignItems:\s*"centro"' \
  i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx

# Expected result after fix: no matches.

Also applies to: 71-76, 92-97, 113-118, 127-132, 142-147, 162-167, 174-179, 212-217, 226-231, 247-252, 295-300, 331-336, 356-361, 402-407, 421-426

🤖 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 42 - 47, Replace the invalid Spanish-style React style tokens in
all JSX style objects (e.g., the occurrences of margen, maxAnchura,
flexDirection: "columna", alignItems: "centro") with the correct React/CSS keys
and values: use margin instead of margen, maxWidth instead of maxAnchura,
flexDirection: "column" instead of "columna", and alignItems: "center" instead
of "centro"; apply these exact replacements consistently across every style
block listed (lines around the blocks containing the style prop) so no invalid
tokens remain.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx (2)

21-25: ⚠️ Potential issue | 🔴 Critical

Duplicated paragraph and unclosed admonition block persist.

Line 21 duplicates the macOS Sequoia warning from line 17. The :::caution[Before Sie beginnen] block on line 23 is never closed before the ## Erstellen einer Time Machine-Freigabe heading, which will cause rendering issues. The title also mixes English and German.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx`
around lines 21 - 25, Remove the duplicated Sequoia warning paragraph (the
repeated sentence about macOS Sequoia) and close the unclosed admonition started
with ":::caution[Before Sie beginnen]" by adding the closing ":::” before the
"## Erstellen einer Time Machine-Freigabe" heading; also make the admonition
title consistently German (e.g., "Bevor Sie beginnen") so the block renders and
the heading text is not mixed-language. Ensure the unique strings
":::caution[Before Sie beginnen]" and "## Erstellen einer Time Machine-Freigabe"
are updated accordingly.

---

28-29: ⚠️ Potential issue | 🔴 Critical

Invalid admonition keyword :::Vorsicht still present.

Docusaurus only supports English admonition keywords (note, tip, info, caution, danger, warning, important). This block will not render as an admonition.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx`
around lines 28 - 29, The admonition uses an invalid keyword ':::Vorsicht' so it
won't render; replace the invalid marker ':::Vorsicht' with a supported English
admonition keyword such as ':::caution' or ':::warning' (keeping the existing
German heading/body text intact) and ensure the matching closing ':::' is
present so the admonition renders correctly.

i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (2)

121-125: ⚠️ Potential issue | 🔴 Critical

Escaped admonition bracket still unresolved, plus duplicate content inside.

The \[Reminder] escape was previously flagged and remains unfixed. Additionally, the admonition body (Line 123) duplicates the privacy list already stated at Lines 116–119 — the note adds no new information.

🤖 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-connect/automated-flash-backup.mdx`
around lines 121 - 125, Replace the malformed/escaped admonition opener
":::note\[Reminder]" with a proper admonition header (e.g., ":::note Reminder"
or ":::note reminder") and remove the duplicated privacy list inside the
admonition (the repeated items from lines 116–119); instead keep a short
single-sentence reminder or a pointer to the original list to avoid redundancy
while preserving the admonition block (locate and update the admonition using
the ":::note\[Reminder]" token and its inner text).

---

56-64: ⚠️ Potential issue | 🔴 Critical

Spanish CSS property names still present — React runtime crash.

The style object still contains margen, maxAnchura, "columna", and "centro" from the previous round. This was flagged before and remains unresolved.

🤖 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-connect/automated-flash-backup.mdx`
around lines 56 - 64, The inline style object on the JSX <div> contains Spanish
keys/values causing a runtime crash; update the style in that <div> (the style
prop) by renaming keys and values to CSS-in-JS identifiers: change "margen" to
margin, "maxAnchura" to maxWidth, "columna" to "column" for flexDirection, and
"centro" to "center" for alignItems (keep the numeric/px value as-is); ensure
the style object uses these corrected keys so React will accept it at runtime.

i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)

152-158: ⚠️ Potential issue | 🔴 Critical

Spanish CSS props persist at all three occurrences — marked "addressed" but not fixed.

Despite the previous review comment being marked as resolved, margen, maxAnchura, "columna", and "centro" still appear at Lines 152–158, 195–201, and 220–226. These will crash React at runtime.

🐛 Proposed fix (apply identically to all three occurrences)

  style={{
-   margen: "auto",
-   maxAnchura: "600px",
+   margin: "auto",
+   maxWidth: "600px",
    display: "flex",
-   flexDirection: "columna",
-   alignItems: "centro",
+   flexDirection: "column",
+   alignItems: "center",
  }}

Also applies to: 195-201, 220-226

🤖 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-connect/overview-and-setup.mdx`
around lines 152 - 158, The inline style object uses Spanish property
names/values (margen, maxAnchura, "columna", "centro") which will crash React;
replace those with the correct React/CSS keys and values: use margin instead of
margen, maxWidth instead of maxAnchura, flexDirection: "column" instead of
"columna", and alignItems: "center" instead of "centro" in the same style object
where those keys appear; apply this exact fix to all three occurrences so the
style objects are valid JSX style props.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (3)

253-283: ⚠️ Potential issue | 🔴 Critical

Duplicate ## Mindestfreier Speicherplatz für einen Cache-Pool section headings.

Line 253 and line 283 carry the identical H2 heading. This causes:

• The Docusaurus TOC to show two indistinguishable entries.
• The auto-generated anchor #mindestfreier-speicherplatz-für-einen-cache-pool to be suffixed (e.g. -1, -2) on one of the two, silently breaking any cross-links that target this anchor.

The content under line 253 (disk-replacement prerequisites and steps, also flagged in the prior review) is misplaced, so the intended fix is likely to remove or retitle that block. The canonical minimum-free-space content belongs under line 283 only.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 253 - 283, Remove the duplicated H2 "## Mindestfreier Speicherplatz
für einen Cache-Pool" that appears with the disk-replacement prerequisites (the
:::note[Prerequisites] block and steps 1–7) so only the canonical
minimum-free-space section remains under the final heading; alternatively, if
that disk-replacement content should stay, rename its heading to something
unique (e.g., "## Festplatte ersetzen im Cache-Pool" or "## Ersatz einer
Festplatte im Cache-Pool") and ensure the note block (::note[Prerequisites]) and
the step list are under that new heading to avoid duplicate anchors.

---

104-106: Bullet-point text incorrectly used as H2 heading.

Previously flagged — still unresolved.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 104 - 106, The text "## **Verhinderung von versehentlichem
Verlust:** Reduzieren Sie das Risiko von Datenverlusten beim Formatieren oder
Ersetzen von Geräten." is a bullet-like sentence incorrectly marked as an H2;
change that markdown heading to a normal paragraph or a list item so it reads as
explanatory copy rather than a section title (e.g., remove the "##" and keep the
bold phrase or convert to "- **Verhinderung von versehentlichem Verlust:** …"),
and ensure the following line "Um eine Festplatte zu einem %%BTRFS|btrfs%%-Pool
hinzuzufügen:" remains a proper heading or subheading (adjust to H3/H4 if
needed) so document structure and accessibility are preserved.

---

144-144: Missing closing bracket in admonition title.

Previously flagged — still unresolved.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
at line 144, The admonition title is missing its closing bracket: locate the
":::tip[" token and close the title by adding the missing "]" after "Planning
für zukünftige Erweiterung" (so it becomes ":::tip[Planning für zukünftige
Erweiterung]") and ensure the admonition block is properly terminated with a
closing ":::".

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx (1)

274-282: ⚠️ Potential issue | 🔴 Critical

CSS property names translated to Spanish — breaks layout.

margen, maxAnchura, columna, centro are not valid CSS properties. React will silently ignore them, causing the image container to lose its centering and width constraints.

🐛 Fix: revert to valid CSS property names

 <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/create-virtual-machines/windows-on-a-vm.mdx`
around lines 274 - 282, The inline style object on the JSX <div style={{ ... }}>
uses Spanish property names ("margen", "maxAnchura", "columna", "centro") which
are invalid CSS and get ignored; update the style keys to valid CSS/React names
(e.g., use margin, maxWidth, display: "flex", flexDirection: "column",
alignItems: "center") while keeping the existing values (like "auto" and
"600px") so the container is correctly centered and constrained.

🧹 Nitpick comments (5)

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md (1)

24-25: Normalize punctuation and format command text as code.

At Line 25, ip addr should be inline code, and both bullets should end consistently with punctuation.

Suggested consistency cleanup

-- Behebung: Automatisches Neustarten des SSH-Daemons nach Netzwerkwiederherstellung, Dank an [mgutt](https://github.com/mgutt)
-- Behebung: Probleme beim Parsen der ip addr Ausgabe, wenn die Schnittstelle Peer-Informationen enthält, Dank an [ap-wtioit](https://github.com/ap-wtioit)
+- Behebung: Automatisches Neustarten des SSH-Daemons nach Netzwerkwiederherstellung, Dank an [mgutt](https://github.com/mgutt).
+- Behebung: Probleme beim Parsen der Ausgabe von `ip addr`, wenn die Schnittstelle Peer-Informationen enthält, Dank an [ap-wtioit](https://github.com/ap-wtioit).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md`
around lines 24 - 25, Update the two bullet lines mentioning the SSH daemon
restart and the ip addr parsing fix so punctuation and code formatting are
consistent: change the second bullet to mark ip addr as inline code (`ip addr`)
and ensure both bullets end with a period; target the lines containing the text
"Automatisches Neustarten des SSH-Daemons nach Netzwerkwiederherstellung, Dank
an [mgutt](https://github.com/mgutt)" and "Probleme beim Parsen der ip addr
Ausgabe, wenn die Schnittstelle Peer-Informationen enthält, Dank an
[ap-wtioit](https://github.com/ap-wtioit)" and apply these edits.

i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (1)

71-71: Prefer modern German spelling: "essenzielle" over "essentielle".

As flagged by LanguageTool, the current Duden-preferred form is essenzielle.

✏️ Proposed fix

-Das Flash-Backup wurde entwickelt, um essentielle Konfigurationsdateien zu speichern...
+Das Flash-Backup wurde entwickelt, um essenzielle Konfigurationsdateien zu speichern...

🤖 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`
at line 71, In the sentence "Das Flash-Backup wurde entwickelt, um essentielle
Konfigurationsdateien zu speichern..." replace the word "essentielle" with the
modern German spelling "essenzielle" (keep the rest of the sentence unchanged)
so the phrase reads "um essenzielle Konfigurationsdateien zu speichern"; ensure
the change is applied where that exact sentence appears.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)

320-345: Consolidate duplicated import guidance blocks

The same “assign every drive including support vdevs” guidance is repeated in multiple places, including an English duplicate in a German page (Lines 343-345 and again around Lines 449-462). Keep one canonical block and link/reference it.

Also applies to: 449-462

🤖 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 320 - 345, Remove the duplicated import guidance by keeping a
single canonical block (preferably the German paragraph starting "Wenn Sie einen
%%ZFS|zfs%%-Pool in Unraid importieren..." and its translated admonition),
delete the repeated English admonition that begins "When you import a
%%ZFS|zfs%% pool into Unraid..." and any other duplicate occurrences, and
replace those duplicates with a short link or reference to the canonical block
(use an anchor or a cross-reference label near the retained paragraph so other
sections point to it).

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx (1)

156-159: Consolidate duplicated “虚拟化的用户共享” sections.

The subsection title and intro appear twice (Line 156 and Line 186). Please merge into one section to avoid redundant content and TOC noise.

Also applies to: 186-189

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx`
around lines 156 - 159, Remove the duplicated "### 虚拟化的用户共享" subsection and
merge their content into a single section: locate the second occurrence (the
header plus the repeated intro lines around the %%virtualization|virt%% and
%%user shares|user-share%% placeholders) and delete it, keeping one copy of the
header and the paragraph that lists the two default user shares; ensure the
preserved paragraph retains the exact placeholder tokens
(%%virtualization|virt%% and %%user shares|user-share%%) and that any unique
details present only in the second block are merged into the remaining block so
the TOC and content are not redundant.

i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx (1)

186-188: Avoid duplicate section titles for VM shares.

### Partages utilisateurs pour la virtualisation is repeated (also present earlier), which makes navigation less clear. Consider renaming this second heading or merging both share sections.

One possible rename

-### Partages utilisateurs pour la virtualisation
+### Recommandations de partages pour la virtualisation

🤖 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/overview-and-system-prep.mdx`
around lines 186 - 188, The heading "### Partages utilisateurs pour la
virtualisation" is duplicated; locate the second occurrence in the file (the
heading string itself) and either rename it to a distinct title (e.g., "###
Partages utilisateurs — détails" or "### Configuration des partages VM") or
merge its content into the earlier section to avoid duplicate navigation
entries; update any nearby references or anchors that rely on the old heading
text so links and TOC remain correct.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 37977ad and 1a827b2.

📒 Files selected for processing (149)

• i18n/de/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx

✅ Files skipped from review due to trivial changes (51)

• i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx

🚧 Files skipped from review as they are similar to previous changes (24)

• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Space in href produces a broken link

href="./künftige Funktionen" contains a literal space, which creates an invalid URL. The path should use a hyphen (or match whatever the actual file slug is).

🐛 Proposed fix

-  <Card title="Künftige Funktionen" icon="Rakete" href="./künftige Funktionen">
+  <Card title="Künftige Funktionen" icon="rocket" href="./future-features">

🤖 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/index.mdx` around lines 71
- 75, The Card component's href attribute (Card title="Künftige Funktionen"
href="./künftige Funktionen") contains a literal space which makes the link
invalid; update the href value to use a hyphen or the actual doc slug (e.g.,
change "./künftige Funktionen" to "./künftige-funktionen" or the correct slug)
so the generated URL is valid and the Card points to the existing document.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

# First, check if the file exists and view the relevant section around lines 28-30
head -35 "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx" | tail -15

Repository: unraid/docs

Length of output: 1090

---

🏁 Script executed:

# Run the verification script from the review comment to check for malformed admonitions
rg -nP ':::(tip|note|info|caution)\[[^\]]*$' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx

Repository: unraid/docs

Length of output: 104

---

🏁 Script executed:

# Also check for the other issues mentioned in the scratchpad
# Check for duplicate English PuTTY text around lines 30-40
sed -n '28,45p' "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx"

Repository: unraid/docs

Length of output: 985

---

🏁 Script executed:

# Check for duplicate caution paragraphs around lines 578-580
sed -n '575,585p' "i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx"

Repository: unraid/docs

Length of output: 899

---

Fix malformed MDX admonition syntax and untranslated/duplicate content in tip block.

Line 28 opens :::tip[ without closing ], which breaks MDX parsing. The title also contains English ("When") instead of German ("Wann").

Additionally, the English PuTTY text (lines 29-30) is duplicated verbatim later in the document under "Laufwerktests und Überwachung" section, and a caution paragraph is duplicated at lines 578-580 with corrupted escaped markup (\*\* instead of **).

🛠️ Proposed fix

-:::tip[When sollte ich das Terminal verwenden?
+:::tip[Wann sollte ich das Terminal verwenden?]

Remove the duplicate English PuTTY text after the "Laufwerktests und Überwachung" heading and remove one instance of the duplicated caution paragraph.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::tip[When sollte ich das Terminal verwenden?
	If you're using Windows, you might prefer %%PuTTY|putty%% for %%SSH|ssh%% access instead of the built-in terminal. It's lightweight, free, and allows you to save sessions for easy access later.
	:::tip[Wann sollte ich das Terminal verwenden?]
	If you're using Windows, you might prefer %%PuTTY|putty%% for %%SSH|ssh%% access instead of the built-in terminal. It's lightweight, free, and allows you to save sessions for easy access later.

🧰 Tools

🪛 LanguageTool

[typographical] ~28-~28: Zeichen ohne sein Gegenstück: ‚]‘ scheint zu fehlen
Context: ...f Ihren Unraid-Server zugreifen. :::tip[When sollte ich das Terminal verwenden? ...

(UNPAIRED_BRACKETS)

---

[grammar] ~28-~28: Passe das Symbol an
Context: ... Ihren Unraid-Server zugreifen. :::tip[When sollte ich das Terminal verwenden? If ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~30-~30: Hier könnte ein Fehler sein.
Context: ... sollte ich das Terminal verwenden? If you're using Windows, you might prefer %%PuTTY...

(QB_NEW_DE)

---

[grammar] ~30-~30: Hier könnte ein Fehler sein.
Context: ...ccess instead of the built-in terminal. It's lightweight, free, and allows you to sa...

(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/system-administration/advanced-tools/command-line-interface.mdx`
around lines 28 - 30, Fix the malformed MDX tip by closing the admonition title
brackets and correcting the German title: change the open token `:::tip[` to
`:::tip[Wann sollte ich das Terminal verwenden?]` and ensure the admonition
block is properly closed with `:::`; remove the duplicated English PuTTY
sentence (`%%PuTTY|putty%% ... %%SSH|ssh%%`) that appears again under the
"Laufwerktests und Überwachung" section, and delete the extra duplicated caution
paragraph that currently contains corrupted escaped markup (`\*\*`) so only one
correct caution paragraph remains.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Broken admonition title and orphaned closing delimiter.

Two distinct issues:

1. "Keep Sie" (line 29) mixes English and German ("Keep" + German pronoun "Sie"). The intended German title is likely Bitte beachten or Hinweise.
2. Line 39 lone ::: — the admonition already closes at line 37 (:::). The extra ::: on line 39 is an orphaned delimiter that will either open an untitled admonition block or break the surrounding MDX structure.

🐛 Proposed fix

-:::info[Keep Sie]
+:::info[Bitte beachten]

 - **Mehrere Pools:** Sie können verschiedene %%cache pools|cache-pool%% erstellen...
 ...
   :::
-
-:::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 29 - 39, Replace the incorrect admonition title "Keep Sie" with a
proper German title such as "Bitte beachten" or "Hinweise" and remove the
orphaned closing delimiter ':::' that appears after the admonition (the extra
':::' following the existing closing ':::') so the admonition block is properly
titled and only closed once.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicate section title and duplicated paragraph.

Two problems introduced in this block:

1. Line 83 — the H3 heading ### Hinzufügen von Laufwerken zur Erstellung eines Mehrgerätepools is identical to the parent H2 at line 64. Docusaurus will generate two conflicting anchors (#hinzufügen-von-laufwerken-zur-erstellung-eines-mehrgerätepools and a suffixed variant), breaking cross-links and producing a redundant TOC entry.
2. Lines 85–87 — the paragraph beginning "Sobald Ihr Pool als..." (line 85) and the paragraph at line 87 (Die %%Cache-Pools|cache-pool%% in Unraid können...) verbatim repeats lines 66–67. The content at lines 85–94 appears to have been duplicated from elsewhere during the Crowdin sync rather than being a new subsection.

The subsection at lines 83–94 should either be removed (since steps 1–6 at lines 89–94 are already present in the parent section) or given a distinct, accurate title such as ### Laufwerke zu einem bestehenden Pool hinzufügen.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 83 - 94, This block duplicates an existing subsection: remove or
rename the H3 titled "### Hinzufügen von Laufwerken zur Erstellung eines
Mehrgerätepools" and delete the duplicated paragraph that begins "Sobald Ihr
Pool als..." along with the repeated sentence "Die %%Cache-Pools|cache-pool%% in
Unraid können..." (the duplicated steps 1–6 are already present in the parent
section); alternatively, if you intend a distinct subsection, change the H3 to a
unique title such as "### Laufwerke zu einem bestehenden Pool hinzufügen" and
keep only the non-duplicated explanatory text and steps, ensuring the heading
text (the H3) and the paragraph starting "Sobald Ihr Pool als..." are not
repeated elsewhere.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Non-English icon props and spaces in href paths across all three Card blocks

Three issues affecting Cards on Lines 59, 65, and 71:

1. Broken href values — href="./configuración del proveedor OIDC" (Line 65) and href="./características Futuras" (Line 71) contain literal spaces, producing invalid URLs and broken navigation links.
2. Non-English icon names — icon="código", icon="escudo", icon="cohete" are Spanish translations of the English icon keys used elsewhere (code, shield, rocket). The Card component will likely fail to resolve these icons.

🐛 Proposed fix

-  <Card title="Usando la API de Unraid" icon="código" href="./how-to-use-the-api">
+  <Card title="Usando la API de Unraid" icon="code" href="./how-to-use-the-api">

-  <Card title="Configuración OIDC" icon="escudo" href="./configuración del proveedor OIDC">
+  <Card title="Configuración OIDC" icon="shield" href="./oidc-provider-setup">

-  <Card title="Características Futuras" icon="cohete" href="./características Futuras">
+  <Card title="Características Futuras" icon="rocket" href="./future-features">

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	<Card title="Usando la API de Unraid" icon="código" href="./how-to-use-the-api">
	Aprenda a interactuar con la API de GraphQL
	</Card>
	<Card title="Configuración OIDC" icon="escudo" href="./configuración del proveedor OIDC">
	Configure proveedores de autenticación SSO
	</Card>
	<Card title="Características Futuras" icon="cohete" href="./características Futuras">
	Mira qué viene a continuación
	</Card>
	<Card title="Usando la API de Unraid" icon="code" href="./how-to-use-the-api">
	Aprenda a interactuar con la API de GraphQL
	</Card>
	<Card title="Configuración OIDC" icon="shield" href="./oidc-provider-setup">
	Configure proveedores de autenticación SSO
	</Card>
	<Card title="Características Futuras" icon="rocket" href="./future-features">
	Mira qué viene a continuación
	</Card>

🤖 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 59
- 75, The three Card components use Spanish icon names and hrefs with spaces
causing broken icons and links; update the icon props on the Card elements to
the English keys used by the icon set (use "code", "shield", "rocket" for the
cards currently using "código", "escudo", "cohete") and replace href values that
contain spaces with slugified paths (e.g. "./configuracion-del-proveedor-oidc"
and "./caracteristicas-futuras" or whatever slug matches the actual doc
filenames) so routing and icon resolution for the Card components work
correctly.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

CSS property names and values must remain in English — invalid JSX style props will silently drop all styling.

The style object contains four Spanish-translated identifiers that are not valid in JSX or CSS:

Written (Spanish)	Correct (JS/CSS)
margen	margin
maxAnchura	maxWidth
"columna"	"column"
"centro"	"center"

Unlike prose content, JSX style prop keys must be valid camelCase JavaScript CSS property names, and their values must be valid CSS strings — neither should be localized. React silently ignores unrecognized style keys, so this div will render without any of the intended layout styles applied.

🐛 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.

Suggested change

	<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/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx`
around lines 3 - 11, The JSX style object on the div uses Spanish identifiers so
styles are dropped; update the style keys/values in that style prop by replacing
margen → margin, maxAnchura → maxWidth, and the string values "columna" →
"column" and "centro" → "center" so the style object uses valid camelCase JS/CSS
property names and valid CSS values (the style object on the div element shown
in the diff).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Docusaurus admonition types valid keywords documentation

💡 Result:

Docusaurus’ built-in (default) admonition type keywords are:

• note
• tip
• info
• warning
• danger [1]

You can also configure additional valid keywords via the content plugin option admonitions.keywords (and optionally merge with defaults using extendDefaults: true). [1]

Sources:
[1] Docusaurus docs — “Admonitions” https://docusaurus.io/docs/3.8.1/markdown-features/admonitions

---

🏁 Script executed:

# Check the actual file to see the admonition declarations and context
head -250 i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx | tail -200

Repository: unraid/docs

Length of output: 11298

---

Replace Spanish admonition keywords with valid Docusaurus English types.

Docusaurus only recognizes built-in English keywords: note, tip, info, warning, and danger. The Spanish keywords used in this file — :::advertencia, :::importante, :::precaución, :::consejo, and :::nota — are not valid and will fail to render as styled admonitions.

However, note that :::important and :::caution (suggested in the original review) are also not Docusaurus built-in types. The correct mappings are:

• :::advertencia → :::warning
• :::importante → :::warning or :::info (no "important" type exists)
• :::precaución → :::warning (no "caution" type exists)
• :::consejo → :::tip
• :::nota → :::note

Additionally, line 192 has a malformed admonition: :::info[When usando un certificado personalizado, eres responsable de... — the opening bracket is never closed and will cause an MDX parse error.

Also, lines 94 and 133 contain identical duplicate section headers (#### HTTPS con certificado Myunraid.net y sin URL de respaldo). The first instance appears incomplete and should likely be removed or have a different title.

Applies to lines: 63, 86, 106, 127, 150, 170, 218 (admonition types); 192 (malformed bracket); 94 & 133 (duplicate headers).

🧰 Tools

🪛 LanguageTool

[grammar] ~63-~63: Cambia la palabra o signo.
Context: ...a clic en Aplicar. :::advertencia Cualquiera en su red puede interceptar d...

(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_SPACE)

🤖 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/securing-your-connection.mdx`
at line 63, Replace all Spanish admonition keywords with Docusaurus built-ins:
change :::advertencia, :::importante, and :::precaución to :::warning (or
:::info for :::importante where context prefers informational tone), change
:::consejo to :::tip, and change :::nota to :::note; also fix the malformed
admonition opening `:::info[When usando un certificado personalizado, eres
responsable de...` by removing the stray `[` or closing it properly, and remove
or correct the duplicate section header text `#### HTTPS con certificado
Myunraid.net y sin URL de respaldo` (keep only the complete/accurate instance
and delete or rename the incomplete one).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# First, find and display the Spanish file around lines 94 and 133
echo "=== Displaying Spanish file around lines 94 and 133 ==="
fd -e mdx "securing-your-connection" i18n/es --exec wc -l {}

Repository: unraid/docs

Length of output: 241

---

🏁 Script executed:

#!/bin/bash
# Read the Spanish file around the suspected duplicate headings
fd -e mdx "securing-your-connection" i18n/es --exec sed -n '90,140p' {}

Repository: unraid/docs

Length of output: 3059

---

🏁 Script executed:

#!/bin/bash
# Also find the English equivalent to compare
fd -e mdx "securing-your-connection" docs --exec sed -n '90,140p' {}

Repository: unraid/docs

Length of output: 2827

---

Fix mistranslated section heading — first block should be "with fallback URL", not "without".

The heading at line 94 is incorrectly translated. Comparing the Spanish and English files, the structure should be:

• Line 94: #### HTTPS con certificado Myunraid.net y con URL de respaldo (WITH fallback URL)
• Line 133: #### HTTPS con certificado Myunraid.net y sin URL de respaldo (WITHOUT fallback URL)

Currently both sections are labeled "sin URL de respaldo" (without fallback URL). The first section discusses fallback access methods (local IP, hostname, and the alternate myunraid.net URL), which aligns with the "with fallback URL" scenario in the English source. Change line 94's heading to "con URL de respaldo" to match the content and fix anchor navigation.

🤖 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/securing-your-connection.mdx`
at line 94, The heading "#### HTTPS con certificado Myunraid.net y sin URL de
respaldo" is mistranslated and should be the "with fallback URL" section; update
the heading text at that block to "#### HTTPS con certificado Myunraid.net y con
URL de respaldo" so it matches the content (references to local IP/hostname and
alternate myunraid.net URL) and restores correct anchor/navigation; ensure the
later section remains "sin URL de respaldo".

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Docusaurus admonition types supported keywords documentation

💡 Result:

Docusaurus admonitions use the :::<keyword> directive, where the keyword is the admonition “type”.

• Documented built-in types (keywords): note, tip, info, warning, danger (also the same set accepted by the @theme/Admonition component’s type prop in the docs). [1]
• Default parser keyword list (remark plugin defaults used by Docusaurus): secondary, info, success, danger, note, tip, warning, important, caution. [2]
• Where it’s configured: per content plugin (docs, blog, pages) via admonitions.keywords (and extendDefaults, which defaults to true). [1]

Sources:
[1] Docusaurus docs – Admonitions: https://docusaurus.io/docs/3.8.1/markdown-features/admonitions
[2] Docusaurus source (DefaultAdmonitionOptions): https://fossies.org/linux/docusaurus/packages/docusaurus-mdx-loader/src/remark/admonitions/index.ts

---

🏁 Script executed:

# Check if the file exists and examine the actual content at the mentioned lines
fd "securing-your-connection.mdx" --type f

Repository: unraid/docs

Length of output: 647

---

🏁 Script executed:

# Read the Chinese file at the relevant line ranges
cat -n i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx | sed -n '60,75p;83,91p;103,130p;147,175p;215,225p'

Repository: unraid/docs

Length of output: 3216

---

Fix Chinese-language admonition type identifiers to use standard Docusaurus keywords.

The following admonition types use non-standard Chinese characters and will not render with proper icon and color styling. Replace with the English keywords recognized by Docusaurus:

Line	Used	Replace with
63	:::警告	:::warning
86	:::重要	:::caution
106	:::注意	:::note
123	:::信息	:::info
127	:::提示[后备访问]	:::tip[后备访问]
150	:::注意	:::note
170	:::注意	:::note
218	:::提示	:::tip

Proposed fix (representative diff for lines 63–65 and 86–88; apply the same pattern to all occurrences)

-  :::警告
+  :::warning
   您网络上的任何人都可以拦截通过HTTP发送的数据。请尽可能使用HTTPS。
   :::

-  :::重要
+  :::caution
   浏览器将显示证书错误。接受警告后，所有流量仍然加密。
   :::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx`
around lines 63 - 65, Replace the non-standard Chinese admonition markers with
Docusaurus-recognized English keywords so icons and styling render correctly:
change :::警告 to :::warning, :::重要 to :::caution, :::注意 to :::note, :::信息 to
:::info, :::提示 to :::tip and keep any labels after brackets (e.g. :::提示[后备访问] ->
:::tip[后备访问]); update each occurrence listed (lines with the tokens originally
`警告`, `重要`, `注意`, `信息`, `提示`) in the document so all admonitions use the
standard keywords.

[coderabbitai]

Actionable comments posted: 10

Note

Due to the large number of review comments, Critical severity comments were prioritized as inline comments.

♻️ Duplicate comments (12)

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx (1)

6-13: ⚠️ Potential issue | 🔴 Critical

Fix translated JSX style keys/values in the style object (layout currently broken).

On Line 8, Line 9, Line 11, and Line 12, the style keys/values were translated and are invalid in React (margen, maxAnchura, "columna", "centro"). This causes centering/max-width/flex direction to be ignored at runtime.

🐛 Proposed fix

 <div
 style={{
- margen: "auto",
- maxAnchura: "600px",
+ margin: "auto",
+ maxWidth: "600px",
  display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
+ flexDirection: "column",
+ alignItems: "center",
 }}
 >

#!/bin/bash
# Verify this file still contains mistranslated JSX style keys/values.
rg -n 'margen|maxAnchura|flexDirection:\s*"columna"|alignItems:\s*"centro"' i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx

Based on learnings, mdx-code-block is the repo’s Crowdin-safe escape hatch for preserving JSX blocks through translation cycles.

🤖 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 6 - 13, The JSX style object in the div contains mistranslated
keys/values that break layout; update the style object on the div (the inline
style with keys like margen, maxAnchura, flexDirection:"columna",
alignItems:"centro") to use valid React CSS keys/values: change margen → margin,
maxAnchura → maxWidth, flexDirection:"columna" → flexDirection:"column", and
alignItems:"centro" → alignItems:"center" so centering, max-width, and flex
direction behave correctly at runtime.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (1)

212-220: ⚠️ Potential issue | 🔴 Critical

CSS property names and values must not be translated — the div will render unstyled.

The inline style prop still contains Spanish-localized keys and values that are invalid React/CSS identifiers:

Line	Current (broken)	Required
214	margen: "auto"	margin: "auto"
215	maxAnchura: "600px"	maxWidth: "600px"
217	flexDirection: "columna"	flexDirection: "column"
218	alignItems: "centro"	alignItems: "center"

margen and maxAnchura are not recognized React style properties and will be silently dropped; "columna" and "centro" are not valid CSS values and will be ignored, leaving the image uncentered and unconstrained.

🐛 Proposed fix

 <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 - 220, The inline style object on the div uses Spanish
translations for CSS property names and values causing the styles to be ignored;
update the style prop on the div (the style={{ ... }} block) to use standard
React/CSS identifiers: replace margen with margin, maxAnchura with maxWidth,
flexDirection value "columna" with "column", and alignItems value "centro" with
"center" so the element centers and constrains correctly.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx (1)

14-22: ⚠️ Potential issue | 🔴 Critical

Invalid CSS property names in style objects — layout will break.

Both <div> style blocks use translated Spanish property names (margen, maxAnchura, columna, centro) instead of valid CSS/JSX keys, which will cause these properties to be silently ignored at render time, breaking the intended layout.

Also applies to: 28-36

🤖 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-manual-method.mdx`
around lines 14 - 22, The style object on the <div> uses Spanish/nonstandard CSS
keys (margen, maxAnchura, columna, centro) which are ignored; update the style
object in the replacement-manual-method <div> (and the duplicated block at
28-36) to use valid JSX/CSS property names: margin, maxWidth, display,
flexDirection (value "column"), and alignItems (value "center") so the layout
renders correctly.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (3)

144-144: Missing closing bracket in admonition title.

Already flagged in a previous review: :::tip[Planning für zukünftige Erweiterung. is missing the closing ].

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
at line 144, The admonition title string ":::tip[Planning für zukünftige
Erweiterung." is missing its closing bracket; update it to ":::tip[Planning für
zukünftige Erweiterung]" (i.e., add the trailing ]) and confirm the admonition
block is properly closed with a matching terminating ":::". Ensure you edit the
line containing the ":::tip[Planning für zukünftige Erweiterung." token so the
parser recognizes the admonition title correctly.

---

104-106: Bullet-point text incorrectly used as H2 heading.

This issue was flagged in a previous review: the bullet description "Verhinderung von versehentlichem Verlust: ..." was promoted to an H2 heading, breaking the ToC and section structure.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 104 - 106, The heading line "## **Verhinderung von versehentlichem
Verlust:** Reduzieren Sie das Risiko von Datenverlusten beim Formatieren oder
Ersetzen von Geräten." was incorrectly rendered as an H2 and breaks the ToC;
replace that H2 with either a bullet point (e.g., "- Verhinderung von
versehentlichem Verlust: Reduzieren Sie...") or a normal paragraph sentence so
it is not a section header, leaving the following line "Um eine Festplatte zu
einem %%BTRFS|btrfs%%-Pool hinzuzufügen:" as the true section heading; ensure
markdown uses a single-line paragraph or list item instead of "##" for that
text.

---

253-279: Disk replacement content placed in "Minimum free space" section.

Previously flagged: lines 253-279 are headed "Mindestfreier Speicherplatz für einen Cache-Pool" but the body describes disk-replacement prerequisites, a numbered replacement procedure, and a timing recommendation — content that does not belong in a minimum-free-space section.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 253 - 279, The content under the heading "Mindestfreier
Speicherplatz für einen Cache-Pool" is about disk replacement (prerequisites
note block, numbered replacement steps 1–7, and the important timing tip) and
should be relocated; create a new section titled something like "Festplatte
ersetzen in einem Cache-Pool" (or move this content into an existing
disk-replacement section) and move the entire prerequisites :::note block, the
numbered steps, and the :::important timing paragraph there, then replace the
original "Mindestfreier Speicherplatz für einen Cache-Pool" section with content
that actually explains minimum free space settings for cache pools (what the
minimum free space setting does, recommended values, how to view/change it in
the Web GUI via Pool → Individuelle Pooleinstellungen, and any effects on
performance), ensuring the UI references (Main, Pool → Balance Status, WebGUI)
remain accurate.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (2)

42-48: ⚠️ Potential issue | 🔴 Critical

Invalid Spanish CSS property names in all JSX style blocks — layout will break.

All style={{ }} blocks use margen, maxAnchura, flexDirection: "columna", and alignItems: "centro" which are not valid CSS/React style keys. Browsers/React will silently ignore them, so all image containers will render without their intended styling.

🐛 Proposed fix (apply to all ~16 occurrences)

 style={{
-  margen: "auto",
-  maxAnchura: "600px",
+  margin: "auto",
+  maxWidth: "600px",
   display: "flex",
-  flexDirection: "columna",
-  alignItems: "centro",
+  flexDirection: "column",
+  alignItems: "center",
 }}

Also applies to: 70-76, 91-97, 112-118, 126-132, 141-147, 161-167, 173-179, 211-217, 225-231, 246-252, 294-300, 330-336, 354-361, 400-407, 420-426

🤖 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 42 - 48, Replace all Spanish CSS property names used in the JSX
style objects (margen, maxAnchura, flexDirection: "columna", alignItems:
"centro") with the correct React/CSS-in-JS keys and values: use margin,
maxWidth, flexDirection: "column", and alignItems: "center"; update every
style={{ ... }} occurrence that currently uses those Spanish keys (e.g., the
shown style object) so the layout and image containers receive the intended
styling.

---

302-302: ⚠️ Potential issue | 🔴 Critical

Pipeline failure: /img/zfs12.png cannot be resolved.

The CI confirms this path is broken. Additionally, image paths are inconsistent — some reference ./assets/zfsX.png (lines 50, 78, 99, etc.) while others use /img/zfsX.png (lines 302, 338, 363, 409, 428). Either revert to ./assets/ relative paths or ensure all images exist under /img/.

🤖 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`
at line 302, The CI failed because the image path "/img/zfs12.png" is unresolved
and image path usage is inconsistent; update the markdown to use a consistent,
valid relative path pattern (e.g., change "/img/zfs12.png" to
"./assets/zfs12.png" or move the file into the /img/ directory), and audit other
occurrences of "/img/zfsX.png" (examples: "/img/zfs12.png", "/img/zfsX.png")
versus "./assets/zfsX.png" (examples seen at lines referencing
"./assets/zfsX.png") to make all image references uniform and ensure each
referenced file actually exists in the chosen location; specifically modify the
markdown image token "![](/img/zfs12.png)" to the chosen valid path and apply
the same normalization across the file.

i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (2)

121-125: ⚠️ Potential issue | 🔴 Critical

Escaped bracket \[Reminder] will prevent admonition label from rendering.

Same issue flagged previously — the backslash prevents Docusaurus from parsing the admonition label.

🐛 Proposed fix

-:::note\[Reminder]
+:::note[Reminder]

🤖 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-connect/automated-flash-backup.mdx`
around lines 121 - 125, The admonition marker is incorrectly escaped as
:::note\[Reminder], which prevents Docusaurus from rendering the label; update
the token to remove the backslash so it reads :::note[Reminder] (i.e., change
the string ':::note\[Reminder]' to ':::note[Reminder]') so the admonition label
displays correctly in the automated-flash-backup.mdx content.

---

56-64: ⚠️ Potential issue | 🔴 Critical

Spanish CSS property names will break layout.

Same issue flagged previously — margen, maxAnchura, "columna", and "centro" are not valid CSS/React style keys.

🐛 Proposed fix

 <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-connect/automated-flash-backup.mdx`
around lines 56 - 64, The inline style object on the JSX <div> uses
Spanish/invalid CSS keys ("margen", "maxAnchura", "columna", "centro") which
will break layout; update the style in that <div> so the keys are valid
CSS/React style properties (use margin, maxWidth, display, flexDirection with
value "column", and alignItems with value "center") and keep the same intent
(centered container with max width 600px and column flex layout).

i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)

152-158: ⚠️ Potential issue | 🔴 Critical

Spanish CSS property names still present in 3 style blocks — layout will break.

Although this was reportedly addressed in a prior commit, these three style blocks still use invalid Spanish CSS keys (margen, maxAnchura, "columna", "centro"). Note that the block at lines 79–85 was correctly fixed to use English keys, but these three were not. This inconsistency suggests the Crowdin sync may have overwritten the fix.

🐛 Proposed fix (apply to all 3 blocks at lines 152, 195, 220)

 style={{
-  margen: "auto",
-  maxAnchura: "600px",
+  margin: "auto",
+  maxWidth: "600px",
   display: "flex",
-  flexDirection: "columna",
-  alignItems: "centro",
+  flexDirection: "column",
+  alignItems: "center",
 }}

Also applies to: 195-201, 220-226

🤖 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-connect/overview-and-setup.mdx`
around lines 152 - 158, The inline style objects use Spanish property names and
values that must be converted to valid CSS keys/values: replace "margen" with
"margin", "maxAnchura" with "maxWidth", "columna" with "column" and "centro"
with "center" in the style={{ ... }} blocks (the same pattern appears in the
three style blocks shown in the diff); update the three style objects (the ones
matching the provided snippet) to use the English keys/values so layout
properties like margin, maxWidth, display, flexDirection: "column", and
alignItems: "center" are correct.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx (1)

21-29: ⚠️ Potential issue | 🔴 Critical

Fix duplicated warning and invalid admonition syntax before the section header.

Line 21 duplicates the Sequoia warning already stated at Line 17. Line 23 introduces a mixed-language caution title, and Line 28 uses :::Vorsicht, which is not a supported Docusaurus admonition keyword. This combination risks incorrect admonition rendering/scoping around the setup section.

Proposed fix

-Einige Nutzer berichten von sporadischen Problemen mit Time Machine und Netzlaufwerken auf macOS Sequoia. Sollte es bei Ihnen zu Backup-Fehlern kommen, ziehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid.net/community/apps?q=time+machine#r) als Alternative zu nutzen.
-
-:::caution[Before Sie beginnen]
-Stellen Sie sicher, dass **%%SMB|samba%%** im %%WebGUI|web-gui%% aktiviert ist:
-
 ## Erstellen einer Time Machine-Freigabe
 
-:::Vorsicht[Bevor Sie beginnen]
+:::caution[Bevor Sie beginnen]

#!/bin/bash
# Read-only verification for admonition validity and duplicate Sequoia warning
FILE="i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx"

echo "== Admonition starters =="
rg -n ':::[^:]+' "$FILE"

echo
echo "== Non-standard admonition keywords (expected empty) =="
rg -n ':::[^:]+' "$FILE" | rg -v ':::(note|tip|info|caution|danger|warning|important)\b|::::'

echo
echo "== Sequoia warning occurrences (expected 1) =="
rg -n 'Einige Nutzer berichten von sporadischen Problemen mit Time Machine' "$FILE"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx`
around lines 21 - 29, Remove the duplicated Sequoia warning sentence (the
repeated "Einige Nutzer berichten von sporadischen Problemen mit Time
Machine...") so only the original occurrence remains, and normalize the
admonitions by replacing the non-standard/mixed-language starters: change
':::caution[Before Sie beginnen]' to the German title ':::caution[Bevor Sie
beginnen]' and replace ':::Vorsicht[Bevor Sie beginnen]' with the supported
admonition keyword ':::caution[Bevor Sie beginnen]' (or remove the second
admonition if it was meant to be the same block) so only one correctly formatted
':::caution[Bevor Sie beginnen]' block surrounds the setup notice.

🧹 Nitpick comments (5)

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx (1)

31-32: Optional: keep image alt text on a single line.

The soft line break inside ![...]() is processed as a space by the remark parser, so rendering is correct. It's a minor consistency nit — single-line alt text is the norm across the rest of the file.

✏️ Proposed consolidation

-![检查按钮可让您执行校验和读取
-检查](/img/Check_button.PNG)
+![检查按钮可让您执行校验和读取检查](/img/Check_button.PNG)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx`
around lines 31 - 32, Remove the soft line break inside the image alt text in
the Markdown image element shown (the snippet starting with
"![检查按钮可让您执行校验和读取\n检查](/img/Check_button.PNG)"): edit the alt text so it is a
single continuous line (no newline between the bracketed text) to match the rest
of the file's convention and avoid the soft-break; keep the same image path and
surrounding Markdown syntax unchanged.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx (1)

119-120: Optional: consider replacing realizar per LanguageTool suggestion.

LanguageTool flags realizar cambios as a generic verb phrase. A more precise alternative such as efectuar cambios or hacer cambios could improve readability, but this is entirely optional.

🤖 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/upgrading-unraid.mdx`
around lines 119 - 120, Replace the phrase "realizar cambios" in the sentence
containing the tokens %%VM|vm%% and %%WebGUI|web-gui%% with a clearer verb—e.g.,
"efectuar cambios" or "hacer cambios"—so the sentence reads: "Para resolver
esto, edita el %%VM|vm%% en la %%WebGUI|web-gui%% y haz clic en **Aplicar** sin
efectuar cambios." Update that string in the document that contains the
upgrading-unraid text.

i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md (1)

7-7: Consider adding a {#upgrade-notes} anchor to the ## Mise à niveau heading.

The sibling headings ### Problèmes connus and ### Rétrogradation both carry explicit anchors ({#known-issues}, {#rolling-back}), but the parent ## Mise à niveau section does not. Future release notes that need to deep-link directly to the upgrade section of 7.2.4 (e.g., 7.2.4.md#upgrade-notes) would fall back to an auto-generated, locale-sensitive slug rather than a stable ID.

📝 Proposed addition

-## Mise à niveau
+## Mise à niveau {`#upgrade-notes`}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md`
at line 7, Add a stable anchor to the upgrade section by appending
`{`#upgrade-notes`}` to the existing `## Mise à niveau` heading so the section
reads `## Mise à niveau {`#upgrade-notes`}`; this matches the sibling headings
(`### Problèmes connus {`#known-issues`}`, `### Rétrogradation {`#rolling-back`}`)
and ensures stable deep-links like `7.2.4.md#upgrade-notes`.

i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx (1)

141-152: Use consistent terminology for appliance VMs in this tab.

Line 141 uses VMs d'appareil while Line 150 uses VMs d'appliance. Pick one term and keep it consistent in the tab label and note.

Proposed consistency patch

-  <TabItem value="appareil" label="VMs d'appareil">
+  <TabItem value="appareil" label="VMs d'appliance">

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx`
around lines 141 - 152, Choose one term and make it consistent: change the
TabItem label/value and any inline tokens to use "appliance" (e.g., update
TabItem value="appareil" label="VMs d'appareil" to value="appliance" label="VMs
d'appliance") and ensure the note header and any %%VMs|vm%%/%%VMs
d'appliance|vm%% tokens match that same term (e.g., "Pourquoi les machines
virtuelles d'appliance...") so the tab label and the note use the identical
terminology.

i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx (1)

186-186: Avoid duplicate subsection titles in the same section.

Line 186 repeats the same heading used at Line 156, which creates duplicate TOC labels and less clear navigation.

Suggested fix

-### Partages utilisateurs pour la virtualisation
+### Recommandations de partage pour la virtualisation

🤖 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/overview-and-system-prep.mdx`
at line 186, The heading "Partages utilisateurs pour la virtualisation" is
duplicated in this section; remove or rename the second occurrence to a unique
title (e.g., modify the heading text to "Partages utilisateurs — configuration"
or similar) so the TOC labels are distinct and navigation is clear; update any
nearby cross-references if they rely on the original heading text.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 37977ad and 1a827b2.

📒 Files selected for processing (149)

• i18n/de/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx

✅ Files skipped from review due to trivial changes (55)

• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx

🚧 Files skipped from review as they are similar to previous changes (24)

• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check for unclosed admonition brackets
rg -n ':::[a-zA-Z]+\[[^]]*$' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx

Repository: unraid/docs

Length of output: 104

---

🏁 Script executed:

#!/bin/bash
# Read the file content around lines 28-30 to verify the exact syntax
sed -n '25,35p' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx | cat -n

Repository: unraid/docs

Length of output: 788

---

🏁 Script executed:

#!/bin/bash
# Check broader context around the admonition (lines 20-45)
sed -n '20,45p' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx | cat -n

Repository: unraid/docs

Length of output: 1679

---

Fix malformed admonition syntax and untranslated English content.

Line 28 is missing the closing bracket ] in the admonition syntax (:::tip[...]), which breaks MDX rendering. Additionally, the title mixes English ("When") with German and the content body remains untranslated.

✅ Suggested fix

-:::tip[When sollte ich das Terminal verwenden?
+:::tip[Wann sollte ich das Terminal verwenden?]
 
-If you're using Windows, you might prefer %%PuTTY|putty%% for %%SSH|ssh%% access instead of the built-in terminal. It's lightweight, free, and allows you to save sessions for easy access later.
+Wenn Sie Windows verwenden, bevorzugen Sie möglicherweise %%PuTTY|putty%% für den %%SSH|ssh%%-Zugriff anstelle des integrierten Terminals. Es ist leichtgewichtig, kostenlos und erlaubt das Speichern von Sitzungen für den späteren schnellen Zugriff.

Note: The same untranslated English sentence also appears again around line 40 and should be translated there as well.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::tip[When sollte ich das Terminal verwenden?
	If you're using Windows, you might prefer %%PuTTY|putty%% for %%SSH|ssh%% access instead of the built-in terminal. It's lightweight, free, and allows you to save sessions for easy access later.
	:::tip[Wann sollte ich das Terminal verwenden?]
	Wenn Sie Windows verwenden, bevorzugen Sie möglicherweise %%PuTTY|putty%% für den %%SSH|ssh%%-Zugriff anstelle des integrierten Terminals. Es ist leichtgewichtig, kostenlos und erlaubt das Speichern von Sitzungen für den späteren schnellen Zugriff.

🧰 Tools

🪛 LanguageTool

[typographical] ~28-~28: Zeichen ohne sein Gegenstück: ‚]‘ scheint zu fehlen
Context: ...f Ihren Unraid-Server zugreifen. :::tip[When sollte ich das Terminal verwenden? ...

(UNPAIRED_BRACKETS)

---

[grammar] ~28-~28: Passe das Symbol an
Context: ... Ihren Unraid-Server zugreifen. :::tip[When sollte ich das Terminal verwenden? If ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~30-~30: Hier könnte ein Fehler sein.
Context: ... sollte ich das Terminal verwenden? If you're using Windows, you might prefer %%PuTTY...

(QB_NEW_DE)

---

[grammar] ~30-~30: Hier könnte ein Fehler sein.
Context: ...ccess instead of the built-in terminal. It's lightweight, free, and allows you to sa...

(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/system-administration/advanced-tools/command-line-interface.mdx`
around lines 28 - 30, Fix the malformed admonition and untranslated English:
close the missing bracket in the admonition opener ":::tip[...]" so it becomes a
valid MDX admonition, change the title text from the mixed-language "When sollte
ich das Terminal verwenden?" to a proper German title like "Wann sollte ich das
Terminal verwenden?", translate the body sentence "If you're using Windows, you
might prefer %%PuTTY|putty%% for %%SSH|ssh%% access instead of the built-in
terminal. It's lightweight, free, and allows you to save sessions for easy
access later." into German (preserving the PuTTY/ssh tokens), and apply the same
translation fix to the duplicate sentence around the second occurrence noted in
the content.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicate heading, English content in caution block, and orphaned ::: syntax error

Three distinct problems cluster in this block:

1. Duplicate heading (Line 263): ## Upgrade-Methoden already appears at Line 251 as part of the <Tabs> block. This second occurrence is redundant and will produce a duplicate anchor in the page.

2. English content in caution body (Line 267): The body of :::caution[Data Verlustrisiko] is entirely in English ("Expanding or modifying %%vDisk|vdisk%%…"). It should be German. The equivalent German text already exists at Line 271.

3. Orphaned ::: MDX syntax error (Line 272): After the caution block closes at Line 269, there is a stray ::: on Line 272 with no matching opening admonition directive. This will cause an MDX parse/build failure.

4. English word in admonition title (Line 265): :::caution[Data Verlustrisiko] — "Data" should be "Daten-" → :::caution[Datenverlustrisiko].

✏️ Proposed fix

-## Upgrade-Methoden
-
-:::caution[Data Verlustrisiko]
-
-Expanding or modifying %%vDisk|vdisk%% and partition layouts can lead to irreversible data loss if not done carefully. Always create a full backup or [%%snapshot|snapshot%%](./vm-setup.mdx#vm-snapshots) of your %%VM|vm%% before proceeding.
-
-:::
-
-Die Erweiterung oder Änderung von %%vDisk|vdisk%%-Layouts und Partitionierungen kann bei unsachgemäßem Vorgehen zu irreversiblen Datenverlust führen. Erstellen Sie immer eine vollständige Sicherung oder ein [%%Snapshot|snapshot%%](./vm-setup.mdx#vm-snapshots) Ihrer %%VM|vm%%, bevor Sie fortfahren.
-:::
+:::caution[Datenverlustrisiko]
+
+Die Erweiterung oder Änderung von %%vDisk|vdisk%%-Layouts und Partitionierungen kann bei unsachgemäßem Vorgehen zu irreversiblem Datenverlust führen. Erstellen Sie immer eine vollständige Sicherung oder ein [%%Snapshot|snapshot%%](./vm-setup.mdx#vm-snapshots) Ihrer %%VM|vm%%, bevor Sie fortfahren.
+
+:::

🧰 Tools

🪛 LanguageTool

[grammar] ~265-~265: Ergänze ein Satzzeichen
Context: ...s> ## Upgrade-Methoden :::caution[Data Verlustrisiko] Expanding or modifying %...

(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_DATADASHVERLUSTRISIKO)

---

[grammar] ~271-~271: Passe die Wortendung an
Context: ...ngen kann bei unsachgemäßem Vorgehen zu irreversiblen Datenverlust führen. Erstellen Sie imme...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ADJECTIVE_FORM)

🤖 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 263 - 272, Remove the duplicate "## Upgrade-Methoden" header (keep
the first one in the <Tabs> block) and delete the extra orphaned "::: " at the
end; change the admonition title in the opening directive from "Data
Verlustrisiko" to "Datenverlustrisiko" (the directive token is :::caution[Data
Verlustrisiko]) and replace the entire English admonition body ("Expanding or
modifying %%vDisk|vdisk%% and partition layouts...") with the existing German
paragraph so the caution block contains only the German text and properly closes
with a single :::.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Orphaned ::: closing tag breaks page rendering.

Line 39 is a bare ::: that appears two lines after the :::info[Keep Sie] block already closed at line 37. This is a stray tag that will be interpreted as a second admonition boundary and will likely cause a Docusaurus/MDX parse error or render garbage for all content that follows.

🐛 Proposed fix — remove the orphaned tag

   - **Application performance:** By placing Docker containers, app data, and %%VM|vm%% disks on a %%cache pool|cache-pool%%, you enhance access speed and minimize strain on your main storage.
   :::

-:::
-
 ---

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
at line 39, Remove the stray closing admonition tag ":::“ that appears two lines
after the ":::info[Keep Sie]" block (the orphaned ':::' shown in the diff);
delete that bare ':::' so there is only the single matching admonition boundary
for the "Keep Sie" block and the rest of the MDX content renders correctly.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicate H3 heading and duplicate paragraph introduced by Crowdin sync.

Line 83 repeats the H2 title from line 64 (Hinzufügen von Laufwerken zur Erstellung eines Mehrgerätepools) as an H3, and line 87 is a near-verbatim copy of line 66. This creates two identical (or near-identical) headings in the same section, duplicated ToC entries, and confusingly redundant prose. The content on lines 89-94 (stop array → assign devices → start array → balance) then partially duplicates the BTRFS and ZFS sub-sections that follow.

🐛 Proposed fix — remove the duplicate block

-### Hinzufügen von Laufwerken zur Erstellung eines Mehrgerätepools
-
-Sobald Ihr Pool als %%BTRFS|btrfs%% oder %%ZFS|zfs%% formatiert ist, können Sie weitere Laufwerke für mehr Redundanz und zur Erweiterung des Speichers hinzufügen. Für detaillierte Anweisungen zum Hinzufügen von Festplatten zu bestehenden Pools, siehe [Festplatten zu einem Pool hinzufügen](`#adding-disks-to-a-pool`).
-
-Die %%Cache-Pools|cache-pool%% in Unraid können von einem Einzelgerät auf mehrere Geräte erweitert werden, was eine erhöhte Kapazität und Redundanz ermöglicht. Um den Mehrgerätemodus zu nutzen, muss Ihr Pool als %%BTRFS|btrfs%% oder %%ZFS|zfs%% formatiert sein.
-
-1. Stoppen Sie das %%array|array%%.
-2. Weisen Sie im **Main**-Tab ein oder mehrere neue Geräte Ihrem Pool zu.
-3. Starten Sie das %%array|array%%.
-4. Unraid integriert automatisch die neuen Geräte und startet eine **Balance** (%%BTRFS|btrfs%%) oder **Resilver** (%%ZFS|zfs%%).
-5. Klicken Sie im **Main**-Tab auf das erste Poolgerät und überprüfen Sie den **Balance-Status** (%%BTRFS|btrfs%%) oder den **Zpool-Status** (%%ZFS|zfs%%), um den Fortschritt zu verfolgen.
-6. Wenn abgeschlossen, arbeitet der Pool im **Mehrgeräte-Modus** mit erhöhter Kapazität und Redundanz.
-
 :::tip

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 83 - 95, Remove the duplicated H3 block that repeats the heading
"Hinzufügen von Laufwerken zur Erstellung eines Mehrgerätepools" plus the
near-duplicate paragraph about adding drives to existing pools and the numbered
steps (the entire block that begins with the repeated H3 and includes the "Die
%%Cache-Pools|cache-pool%%..." sentence and steps 1–6). Keep the original
H2/section content and the following BTRFS/ZFS subsections intact; delete only
the duplicate heading, paragraph, and list to prevent redundant ToC entries and
duplicated instructions.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Misplaced :::note[Timing] block — disk-replacement content inside the RAID-level-changing section.

Lines 227-231 describe disk replacement ("Das Ersetzen einer Festplatte…") but are nested inside the "Ändern von Pool-RAID-Leveln" section, immediately after the step list for changing RAID profiles. This block has no logical relationship to the RAID-level change instructions. It belongs in a dedicated disk-replacement section (or in the "Mindestfreier Speicherplatz" section that already discusses replacement at lines 253-255).

🐛 Proposed fix — remove the misplaced note block from this section

 6. Überwachen Sie den Fortschritt im %%WebGUI|web-gui%%.
 
-:::note\[Timing]
-
-Das Ersetzen einer Festplatte in Ihrem %%cache pool|cache-pool%% ist eine wichtige Aufgabe, die dazu beiträgt, die Leistung und Zuverlässigkeit Ihres Speichersystems aufrechtzuerhalten.
-
-:::
-
 <details>

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::note\[Timing]
	Das Ersetzen einer Festplatte in Ihrem %%cache pool|cache-pool%% ist eine wichtige Aufgabe, die dazu beiträgt, die Leistung und Zuverlässigkeit Ihres Speichersystems aufrechtzuerhalten.
	:::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 227 - 231, Remove the misplaced ":::note[Timing]" block containing
"Das Ersetzen einer Festplatte..." from the "Ändern von Pool-RAID-Leveln"
section (the note starting with :::note[Timing]) and relocate it into the
dedicated disk-replacement guidance or the existing "Mindestfreier
Speicherplatz" section so the content sits with related replacement
instructions; ensure the note syntax is preserved and update surrounding text so
the step list for changing RAID profiles is not interrupted.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicate H2 heading — "Mindestfreier Speicherplatz für einen Cache-Pool" appears twice.

This exact heading already appears at line 253. Having two identical H2 anchors on the same page breaks anchor navigation (only the first will be reachable) and produces a malformed ToC. One of the two sections must be renamed or merged.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
at line 283, The document contains a duplicate H2 heading "Mindestfreier
Speicherplatz für einen Cache-Pool" which breaks anchors and the ToC; locate the
second occurrence of the H2 with that exact text and either remove it, merge its
content into the first "Mindestfreier Speicherplatz für einen Cache-Pool"
section, or rename the second H2 to a distinct, accurate heading (update any
internal links if renamed) so there are no identical H2 anchors.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

:::caution block is empty — its list content was displaced to a different section.

The caution block opens at line 315 with "When accessing a user share from multiple pools and array disks, Unraid merges the directory listings in this order:" but closes immediately at line 319 without the ordered list. The list (items 1-3: pool assigned to share, array disks, other pools) appears far later at lines 387-391 under "Mehrere Pools". This leaves the caution with an opening sentence and no enumerated content, which is misleading and incomplete.

🐛 Proposed fix — either move the list into the caution block or remove the displaced caution

 :::caution
 
 When accessing a [%%user share|user-share%%](./shares.mdx) from multiple pools and %%array|array%% disks, Unraid merges the directory listings in this order:
 
+1. Pool dem Share zugewiesen
+2. %%Array|array%%-Festplatten (disk1, disk2, ..., disk28)
+3. Andere Pools (in dieser Reihenfolge)
+
 :::

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::caution
	Beim Zugriff auf [%%user shares|user-share%%](./shares.mdx) aus mehreren Pools und %%array|array%%-Laufwerken werden Verzeichnislisten in dieser Reihenfolge zusammengeführt:
	1. Zuerst der Freigabe zugewiesene Pool.
	2. %%Array|array%%-Laufwerke (`disk1`, `disk2`, `disk3`, ...).
	3. Danach andere Pools.
	When accessing a [%%user share|user-share%%](./shares.mdx) from multiple pools and %%array|array%% disks, Unraid merges the directory listings in this order:
	:::
	:::caution
	When accessing a [%%user share|user-share%%](./shares.mdx) from multiple pools and %%array|array%% disks, Unraid merges the directory listings in this order:
	1. Pool dem Share zugewiesen
	2. %%Array|array%%-Festplatten (disk1, disk2, ..., disk28)
	3. Andere Pools (in dieser Reihenfolge)
	:::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 315 - 319, The caution block starting with ":::caution" is empty
because the enumerated list describing how Unraid merges directory listings was
moved later under "Mehrere Pools"; fix by relocating the ordered list items (the
three list entries explaining pool-assigned share, array disks, other pools)
back inside the caution block immediately after the opening sentence in the
:::caution block, or alternatively remove the :::caution block entirely if you
prefer to keep the list only under "Mehrere Pools"; update surrounding
punctuation and spacing so the caution block properly encloses the list and
renders correctly with Docusaurus.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Invalid admonition types cause pipeline failures — replace Spanish keywords with Docusaurus-recognized English types.

Docusaurus only accepts the following fixed admonition type identifiers: note, tip, info, caution, warning. The Spanish-language variants used here (advertencia, importante, precaución, nota, consejo) are treated as unknown directives and silently dropped, meaning none of these callout boxes render at all. This is confirmed by the five pipeline failures (lines 63, 86, 127, 170, 218).

🐛 Required replacements

-  :::advertencia
+  :::warning

-  :::importante
+  :::important

-  :::precaución
+  :::caution

-  :::nota
+  :::note

-  :::consejo[Acceso alternativo]
+  :::tip[Acceso alternativo]

-  :::consejo
+  :::tip

Apply the same substitution pattern at all 7 occurrences (Lines 63, 86, 106, 127, 150, 170, 218).

Also applies to: 86-86, 106-106, 127-127, 150-150, 170-170, 218-218

🧰 Tools

🪛 LanguageTool

[grammar] ~63-~63: Cambia la palabra o signo.
Context: ...a clic en Aplicar. :::advertencia Cualquiera en su red puede interceptar d...

(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_SPACE)

🤖 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/securing-your-connection.mdx`
at line 63, Replace the Spanish admonition directives with Docusaurus-recognized
English types so the callouts render: change "advertencia" -> "warning",
"importante" -> "note", "precaución" -> "caution", "nota" -> "note", and
"consejo" -> "tip"; update every occurrence of those tokens (e.g., instances
like ":::advertencia") in the document so the admonition blocks use the allowed
identifiers (note, tip, info, caution, warning).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

FILE="$(fd 'deploy-and-configure-unraid-os\.mdx$' | head -n1)"

echo "File found: $FILE"
echo
echo "Inspecting target range (lines 96-108):"
nl -ba "$FILE" | sed -n '96,108p'

echo
echo "Check for non-ASCII admonition types (likely invalid/custom):"
rg -nP '^\s*:::[^\x00-\x7F]+' "$FILE" || true

echo
echo "Check for literal escaped newline before admonition closing marker:"
rg -n '\\n\s*:::' "$FILE" || true

Repository: unraid/docs

Length of output: 247

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

FILE="$(fd 'deploy-and-configure-unraid-os\.mdx$' | head -n1)"

echo "File found: $FILE"
echo
echo "Inspecting target range (lines 96-108):"
cat -n "$FILE" | sed -n '96,108p'

echo
echo "Check for non-ASCII admonition types:"
rg -n '^\s*:::[^\x00-\x7F]+' "$FILE" || echo "(none found)"

echo
echo "Check for literal escaped newline before closing marker:"
rg -n '\\n.*:::' "$FILE" || echo "(none found)"

Repository: unraid/docs

Length of output: 1048

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Searching for i18n/zh path:"
fd 'deploy-and-configure-unraid-os\.mdx' | head -20

echo
echo "Searching specifically in i18n/zh directory:"
fd 'deploy-and-configure-unraid-os\.mdx' 'i18n/zh' || echo "(not found in i18n/zh)"

Repository: unraid/docs

Length of output: 818

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

FILE="i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx"

echo "Inspecting target range (lines 96-110):"
cat -n "$FILE" | sed -n '96,110p'

echo
echo "Full content around the admonition:"
cat -n "$FILE" | sed -n '100,107p'

Repository: unraid/docs

Length of output: 835

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "=== Checking admonition usage in other i18n files ==="
echo

echo "German (de) admonitions:"
rg -n '^\s*:::' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx | head -10

echo
echo "Spanish (es) admonitions:"
rg -n '^\s*:::' i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx | head -10

echo
echo "French (fr) admonitions:"
rg -n '^\s*:::' i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx | head -10

echo
echo "English (en) admonitions:"
rg -n '^\s*:::' docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx | head -10

echo
echo "=== Checking docusaurus config for admonition types ==="
find . -name "docusaurus.config.*" -o -name "*.config.js" -o -name "*.config.ts" | head -5

Repository: unraid/docs

Length of output: 795

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

FILE="i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx"

echo "=== Exact bytes around closing marker (lines 102-106) ==="
sed -n '102,106p' "$FILE" | od -c | head -40

echo
echo "=== Readable view (lines 102-106) ==="
sed -n '102,106p' "$FILE"

Repository: unraid/docs

Length of output: 172

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

FILE="i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx"

echo "=== Raw content (lines 101-106) ==="
sed -n '101,106p' "$FILE"

echo
echo "=== Comparison with German file (lines 101-106) ==="
sed -n '101,106p' i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx

Repository: unraid/docs

Length of output: 983

---

Fix admonition syntax to match other language versions and prevent MDX parse errors.

Line 101 uses :::重要 (Chinese) instead of the standard :::important keyword used in all other language translations (de, es, fr, en). Additionally, line 104 embeds the closing delimiter as literal text (\n :::) instead of placing ::: on its own line, breaking the proper admonition structure observed in all other language files.

🛠️ Proposed fix

-  :::重要
+  :::important
   许多主板将可启动设备限制为 12 个硬盘。如果您的 USB 闪存驱动器被识别为硬盘，则在安装 12 个物理硬盘后，您可能无法从中启动。在可能的情况下，将 BIOS 配置为将闪存驱动器视为可移动设备。
 
-  如果使用附加的 HBA，则您可以禁用 INT 13h 支持，以防止其连接的驱动器出现在可启动设备列表中，从而帮助保持在 12 驱动器限制范围内。\n  :::
+  如果使用附加的 HBA，则您可以禁用 INT 13h 支持，以防止其连接的驱动器出现在可启动设备列表中，从而帮助保持在 12 驱动器限制范围内。
+  :::

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::重要
	许多主板将可启动设备限制为 12 个硬盘。如果您的 USB 闪存驱动器被识别为硬盘，则在安装 12 个物理硬盘后，您可能无法从中启动。在可能的情况下，将 BIOS 配置为将闪存驱动器视为可移动设备。
	如果使用附加的 HBA，则您可以禁用 INT 13h 支持，以防止其连接的驱动器出现在可启动设备列表中，从而帮助保持在 12 驱动器限制范围内。\n :::
	:::important
	许多主板将可启动设备限制为 12 个硬盘。如果您的 USB 闪存驱动器被识别为硬盘，则在安装 12 个物理硬盘后，您可能无法从中启动。在可能的情况下，将 BIOS 配置为将闪存驱动器视为可移动设备。
	如果使用附加的 HBA，则您可以禁用 INT 13h 支持，以防止其连接的驱动器出现在可启动设备列表中，从而帮助保持在 12 驱动器限制范围内。
	:::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
around lines 101 - 105, Replace the nonstandard Chinese admonition marker and
malformed closing from the snippet: change the opening ":::重要" to the standard
":::important" and move the closing "::: " to its own line (remove the embedded
"\n  :::" text) so the admonition block uses the exact ":::important" ... "::: "
structure used in other languages; leave the internal paragraph text unchanged.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Invalid admonition markers (::提示, ::注意) — missing one colon.

Lines 184, 207, and 240 use ::提示 / ::注意 instead of :::tip / :::note. Docusaurus will not recognise these as admonitions and will render the raw text instead.

🐛 Proposed fix

-    ::提示[最佳实践]
+    :::tip[最佳实践]

-    ::提示
+    :::tip

-    ::注意[数据丢失警告]
+    :::note[数据丢失警告]

Also applies to: 207-208, 240-241

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx`
around lines 184 - 188, Replace the invalid two-colon Chinese admonition markers
(::提示 and ::注意) with proper Docusaurus admonitions using three colons and the
English keywords (e.g., change "::提示" to ":::tip" and "::注意" to ":::note"),
ensure each admonition block is opened with the triple-colon form and closed
with a matching ":::", and update all occurrences (the markers shown in the
diff) so Docusaurus will render them as admonitions.

[coderabbitai]

Actionable comments posted: 31

Note

Due to the large number of review comments, Critical severity comments were prioritized as inline comments.

♻️ Duplicate comments (42)

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx (1)

36-44: ⚠️ Potential issue | 🔴 Critical

Restore valid React style keys/values in both image containers.

Line 38-42 and Line 89-93 contain translated style keys/values (margen, maxAnchura, "columna", "centro"), so React drops those declarations and layout breaks.

🐛 Proposed fix (both blocks) + Crowdin-safe wrapping

-<div
-style={{
- margen: "auto",
- maxAnchura: "600px",
- display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
-}}
->
-![Interoperabilidad mejorada con macOS](/img/enhancedmacos.png)
-</div>
+```mdx-code-block
+<div
+  style={{
+    margin: "auto",
+    maxWidth: "600px",
+    display: "flex",
+    flexDirection: "column",
+    alignItems: "center",
+  }}
+>
+  ![Interoperabilidad mejorada con macOS](/img/enhancedmacos.png)
+</div>
+```

-<div
-style={{
- margen: "auto",
- maxAnchura: "600px",
- display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
-}}
->
-![Editor de Time Machine](/img/TimeMachineEditor.png)
-</div>
+```mdx-code-block
+<div
+  style={{
+    margin: "auto",
+    maxWidth: "600px",
+    display: "flex",
+    flexDirection: "column",
+    alignItems: "center",
+  }}
+>
+  ![Editor de Time Machine](/img/TimeMachineEditor.png)
+</div>
+```

#!/bin/bash
# Verify there are no translated style keys/values left in this file.
FILE="i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx"

echo "Checking for invalid translated style tokens..."
rg -nP 'margen|maxAnchura|flexDirection:\s*"columna"|alignItems:\s*"centro"' "$FILE"

echo
echo "Checking mdx-code-block wrappers near the two image sections..."
rg -nP 'mdx-code-block|enhancedmacos\.png|TimeMachineEditor\.png' "$FILE"

Based on learnings: In Docusaurus MDX files, mdx-code-block is a Crowdin escape hatch to preserve JSX during translation syncs.

Also applies to: 87-95

🤖 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/apple-time-machine.mdx`
around lines 36 - 44, Restore the valid React style keys/values for both image
container <div> blocks by replacing the translated tokens (margen → margin,
maxAnchura → maxWidth, "columna" → "column", "centro" → "center") and ensure the
style object uses margin: "auto", maxWidth: "600px", display: "flex",
flexDirection: "column", alignItems: "center"; also wrap each corrected JSX
<div>...</div> block with Crowdin-safe fences using mdx-code-block so the JSX is
preserved during translation syncs (update both occurrences that reference
enhancedmacos.png and TimeMachineEditor.png).

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx (1)

48-49: ⚠️ Potential issue | 🔴 Critical

Remove the orphan admonition close marker at Line 48.

:::important is already closed at Line 46; the extra ::: at Line 48 is unmatched and can break MDX rendering/build.

Proposed fix

 :::
-
-:::
 
 ### Herunterladen und entpacken

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx`
around lines 48 - 49, Remove the unmatched orphan admonition close marker by
deleting the extra ":::” that follows the already-closed ":::important" block
(the stray closing token shown in the diff); ensure only the single matching
":::important" open/close pair remains so the MDX admonition is correctly
balanced.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx (1)

61-61: ⚠️ Potential issue | 🔴 Critical

Anchor {#troubleshooting-with-safe-mode} is still absent from this heading.

The current code does not include the explicit anchor despite the prior review noting it was addressed. The four cross-referencing documents (boot-and-startup-failures.mdx and system-crashes-and-stability.mdx in both docs/ and i18n/de/) still link to #troubleshooting-with-safe-mode. Without it, Docusaurus will auto-generate a German anchor (likely #problemlösung-im-abgesicherten-modus) that won't match those existing links, causing silent broken anchors in critical troubleshooting pages.

Either restore the anchor on the heading:

🔗 Proposed fix — restore explicit anchor

-## Problemlösung im abgesicherten Modus
+## Problemlösung im abgesicherten Modus {`#troubleshooting-with-safe-mode`}

...or verify that all four referencing files have been updated to use the new auto-generated anchor.

#!/bin/bash
# Verify whether the four referencing files still use the old anchor
echo "=== Checking for troubleshooting-with-safe-mode references ==="
grep -rn "troubleshooting-with-safe-mode" \
  i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/ \
  docs/unraid-os/troubleshooting/ 2>/dev/null || echo "No references found"

echo ""
echo "=== Current heading in plugins.mdx ==="
grep -n "Problemlösung im abgesicherten Modus" \
  i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.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/using-unraid-to/customize-your-experience/plugins.mdx`
at line 61, The German heading "Problemlösung im abgesicherten Modus" is missing
the explicit anchor `{`#troubleshooting-with-safe-mode`}` referenced elsewhere;
restore the anchor by editing the heading in plugins.mdx to include
`{`#troubleshooting-with-safe-mode`}` (i.e., change the line containing the
heading "Problemlösung im abgesicherten Modus" to include the anchor) so the
four cross-references (`boot-and-startup-failures.mdx` and
`system-crashes-and-stability.mdx` in both docs and i18n/de) resolve correctly,
or alternatively update those four files to point to the auto-generated German
anchor—pick one consistent approach and apply it across the affected files.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (3)

576-581: Duplicate caution paragraph with escaped markdown — already flagged.

Lines 578 and 580 are identical paragraphs, and both contain \*\*Docker-Safe New Perms \*\* with escaped asterisks instead of proper bold markdown (**Docker-Safe New Perms**). One instance should be removed and the remaining one fixed. This was already identified in a prior review.

🤖 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/advanced-tools/command-line-interface.mdx`
around lines 576 - 581, The caution block contains a duplicate paragraph and
uses escaped asterisks for bold around "Docker-Safe New Perms"; remove the
repeated paragraph so only one caution remains, and fix the markdown by
replacing `\*\*Docker-Safe New Perms \*\*` with proper bold syntax **Docker-Safe
New Perms** (preserve the rest of the text including "Neue Berechtigungen" and
the %%WebGUI|web-gui%% tag) so the caution appears once and the Docker tool name
renders correctly.

---

28-30: Malformed admonition syntax and untranslated content — already flagged.

The :::tip[ is missing its closing ], and "When" should be "Wann". The English PuTTY sentence on line 30 is untranslated. These were already identified in a prior review.

🤖 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/advanced-tools/command-line-interface.mdx`
around lines 28 - 30, Fix the malformed admonition and untranslated sentence:
close the admonition header by changing ":::tip[" to ":::tip[Wann sollte ich das
Terminal verwenden?]" and replace the English PuTTY sentence ("If you're using
Windows, you might prefer %%PuTTY|putty%% for %%SSH|ssh%% access instead of the
built-in terminal. It's lightweight, free, and allows you to save sessions for
easy access later.") with a German translation (e.g., "Wenn Sie Windows
verwenden, können Sie für %%SSH|ssh%%-Zugriff %%PuTTY|putty%% anstelle des
integrierten Terminals bevorzugen; es ist leichtgewichtig, kostenlos und erlaubt
das Speichern von Sitzungen.") so the admonition content is fully translated and
the admonition syntax is valid.

---

40-41: Duplicate untranslated English PuTTY text — already flagged.

This is the same English PuTTY/SSH sentence from line 30, duplicated here outside of any admonition or contextual block. Already covered in a prior review.

🤖 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/advanced-tools/command-line-interface.mdx`
around lines 40 - 41, Duplicate untranslated English sentence present: remove or
replace the duplicated line "If you're using Windows, you might prefer
%%PuTTY|putty%% for %%SSH|ssh%% access instead of the built-in terminal. It's
lightweight, free, and allows you to save sessions for easy access later." (the
repeated PuTTY/SSH sentence) — delete this duplicate occurrence or replace it
with the proper German translation consistent with the earlier instance; ensure
only one localized instance remains and keep the markup tokens %%PuTTY|putty%%
and %%SSH|ssh%% intact if used.

i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)

152-158: ⚠️ Potential issue | 🔴 Critical

Spanish CSS property names still present — React runtime crash (regression).

The previous fix was marked resolved but Crowdin has re-introduced margen, maxAnchura, "columna", and "centro" across all three style blocks. JSX style props require valid camelCase CSS property names and English string values; these will cause a runtime error.

🐛 Proposed fix (apply identically to lines 152–158, 195–201, and 220–226)

  style={{
-   margen: "auto",
-   maxAnchura: "600px",
+   margin: "auto",
+   maxWidth: "600px",
    display: "flex",
-   flexDirection: "columna",
-   alignItems: "centro",
+   flexDirection: "column",
+   alignItems: "center",
  }}

Also applies to: 195-201, 220-226

🤖 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-connect/overview-and-setup.mdx`
around lines 152 - 158, Replace the Spanish CSS identifiers inside the JSX style
objects with valid camelCase English names and English string values: change
margen to margin, maxAnchura to maxWidth, "columna" to "column", and "centro" to
"center"; ensure the style objects read { margin: "auto", maxWidth: "600px",
display: "flex", flexDirection: "column", alignItems: "center" } and apply this
exact replacement to all three style blocks referenced (the ones around lines
152–158, 195–201, and 220–226).

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (2)

140-140: ⚠️ Potential issue | 🔴 Critical

Unresolved: anchor #converting-to-a-new-file-system-type is broken for external documents.

The heading ## 转换到新的文件系统类型 at line 187 still lacks an explicit {#converting-to-a-new-file-system-type} anchor. External documents (release notes 7.0.0, 7.2.0, 7.2.1 and their i18n counterparts, plus securing-your-data.mdx) still reference this anchor.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
at line 140, The anchor referenced externally is missing: add an explicit HTML
anchor to the Chinese heading by changing the "## 转换到新的文件系统类型" heading to
include the anchor token {`#converting-to-a-new-file-system-type`} (i.e., "##
转换到新的文件系统类型 {`#converting-to-a-new-file-system-type`}") so external documents
(release notes and securing-your-data.mdx) can link to it; locate the heading
text "转换到新的文件系统类型" in file i18n/zh/.../file-systems.mdx and append the exact
anchor slug converting-to-a-new-file-system-type.

---

163-163: ⚠️ Potential issue | 🔴 Critical

Unresolved: three intra-document anchor links remain broken.

The same three explicit English anchors removed in a prior commit are still missing, leaving their corresponding links broken:

Heading (line)	Missing anchor	Broken reference (line)
## 更改文件系统类型 (163)	{#changing-a-file-system-type}	Line 230
### 使用未分配设备插件 (410)	{#using-the-unassigned-devices-plugins}	Line 93
### 检查文件系统 (433)	{#checking-a-file-system}	Line 451

Additionally, ### 检查文件系统 appears twice (lines 433 and 483); without an explicit anchor on line 433, Docusaurus auto-deduplicates them, making the link at line 451 unresolvable.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
at line 163, Add the missing explicit anchor IDs for the three headings so their
intra-document links resolve: insert "{`#changing-a-file-system-type`}"
immediately after the "## 更改文件系统类型" heading, insert
"{`#using-the-unassigned-devices-plugins`}" after "### 使用未分配设备插件", and add
"{`#checking-a-file-system`}" after the first "### 检查文件系统" (line 433) to avoid
Docusaurus auto-deduplication and make the link at line 451 point to the correct
anchor; ensure the anchor tokens exactly match the referenced IDs.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx (1)

21-29: ⚠️ Potential issue | 🔴 Critical

Fix the admonition block structure and keyword before merge.

Line [21] duplicates the Sequoia warning already stated above. Line [23] opens an admonition with a mixed-language title and does not close it before the heading. Line [28] uses :::Vorsicht, which is not a supported Docusaurus admonition type.

Proposed fix

-Einige Nutzer berichten von sporadischen Problemen mit Time Machine und Netzlaufwerken auf macOS Sequoia. Sollte es bei Ihnen zu Backup-Fehlern kommen, ziehen Sie in Betracht, den [Time Machine Docker-Container](https://unraid.net/community/apps?q=time+machine#r) als Alternative zu nutzen.
-
-:::caution[Before Sie beginnen]
+:::caution[Bevor Sie beginnen]
 Stellen Sie sicher, dass **%%SMB|samba%%** im %%WebGUI|web-gui%% aktiviert ist:
+:::
 
 ## Erstellen einer Time Machine-Freigabe
 
-:::Vorsicht[Bevor Sie beginnen]
-
 Stellen Sie sicher, dass **%%SMB|samba%%** im %%WebGUI|web-gui%% aktiviert ist:

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx`
around lines 21 - 29, Remove the duplicated Sequoia warning and fix the
malformed admonitions: replace the mixed-language ":::caution[Before Sie
beginnen]" title with a single-language admonition (e.g., German
":::caution[Bevor Sie beginnen]" or English ":::caution[Before you begin]"),
ensure that this admonition is properly closed with a matching ":::". Also
replace the unsupported ":::Vorsicht[Bevor Sie beginnen]" with a supported
Docusaurus admonition type (e.g., ":::caution" or ":::note") and close it;
verify the SMB keyword line remains intact ("**%%SMB|samba%%** im
%%WebGUI|web-gui%% aktiviert ist") and remove the duplicate line 21.

i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)

57-65: LGTM — indentation and whitespace changes are formatting-only and consistent with other locales.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
around lines 57 - 65, The changes in the MDX snippet are formatting-only
(whitespace/indentation) and match other locales, so no functional edits are
required; approve the PR as-is but verify the two JSX <div> blocks (the ones
wrapping ![Commencer](/img/Upc_get_started.png) and ![Installer clé
d'essai](/img/Upc_install_trial_key.png)) retain their exact image paths and alt
text and that indentation matches the project style used by other locale files.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (2)

302-302: ⚠️ Potential issue | 🔴 Critical

Resolve broken image path blocking MDX compilation.

Line [302] points to /img/zfs12.png, which fails CI resolution. Switch back to the working local asset path (or add the missing file under static /img).

✅ Minimal unblock fix

-![](/img/zfs12.png)
+![](./assets/zfs12.png)

🤖 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`
at line 302, Replace the broken image reference `/img/zfs12.png` in the MDX (the
image tag shown on the diff) with the correct working local asset path used
elsewhere in this doc (or add the missing `zfs12.png` into the static `/img`
folder); locate the image inclusion line that shows "![](/img/zfs12.png)" and
either update it to the proper relative/local path used by other images in this
file or add the file under static `/img` so CI can resolve it.

---

42-48: ⚠️ Potential issue | 🟠 Major

Fix invalid React inline style keys/values in all image wrapper blocks.

On Line [43] and repeated blocks, translated keys/values (margen, maxAnchura, "columna", "centro") are not valid React/CSS style entries, so layout styling is dropped.

🛠️ Representative fix (apply to each repeated style block)

 style={{
- margen: "auto",
- maxAnchura: "600px",
+ margin: "auto",
+ maxWidth: "600px",
  display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
+ flexDirection: "column",
+ alignItems: "center",
 }}

#!/bin/bash
set -euo pipefail

file="i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx"

# Expect 0 matches after the fix.
rg -n 'margen|maxAnchura|flexDirection:\s*"columna"|alignItems:\s*"centro"' "$file"

Also applies to: 70-76, 91-97, 112-118, 126-132, 141-147, 161-167, 173-179, 211-217, 225-231, 246-252, 294-300, 330-336, 355-361, 401-407, 420-426

🤖 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 42 - 48, Replace the invalid Spanish style keys/values in each
image wrapper style prop with valid React/CSS names: change "margen" to margin,
"maxAnchura" to maxWidth, flexDirection: "columna" to flexDirection: "column",
and alignItems: "centro" to alignItems: "center"; apply this same fix in every
repeated style={{ ... }} block (examples shown around the existing style block
and at the other listed occurrences) so the inline styles are recognized by
React.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx (1)

3-11: Previously flagged CSS translation issue remains unresolved.

The style block at Lines 3–11 still contains margen, maxAnchura, "columna", and "centro". The AI-generated summary for this file claims these were replaced with valid English CSS-in-JS keys, but the code does not reflect that change.

🤖 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 3 - 11, The style object in the JSX div still uses incorrect
Spanish keys—margen, maxAnchura, "columna", and "centro"—so update the inline
style in the div (the style prop on the top-level <div>) to use correct
CSS-in-JS property names and values (e.g., margin, maxWidth, flexDirection:
"column", alignItems: "center") so the component renders correctly; locate the
style prop on the div in wireguard-configure-mobile.mdx and replace each Spanish
key/value with the corresponding English CSS-in-JS key/value.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx (1)

274-282: Previously flagged CSS translation issue is still unresolved.

The style block at Lines 274–282 still contains margen, maxAnchura, "columna", and "centro". The AI-generated summary for this file incorrectly states these were replaced with valid English equivalents, but the code contradicts that claim.

🤖 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 - 282, The JSX style object on the <div> still uses Spanish
keys/values (margen, maxAnchura, "columna", "centro"); update the style prop in
that <div> to use valid React/CSS names and values: change margen -> margin,
maxAnchura -> maxWidth (include units like "600px"), flexDirection from
"columna" -> "column", and alignItems from "centro" -> "center", preserving
other properties (display: "flex") so the layout behaves correctly.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx (1)

14-22: Previously flagged CSS translation issue remains unresolved in both style blocks.

Both style blocks (Lines 14–22 and 28–36) still contain margen, maxAnchura, "columna", and "centro" rather than valid CSS-in-JS property names.

Also applies to: 28-36

🤖 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-manual-method.mdx`
around lines 14 - 22, The JSX style objects in the <div> elements use Spanish
property names; update the style objects (the style prop on the <div> in the
replacement-manual-method.mdx) to use valid CSS-in-JS keys: replace "margen"
with margin, "maxAnchura" with maxWidth, "columna" with "column" for
flexDirection, and "centro" with "center" for alignItems in both the first style
block and the second style block (the style prop around lines 14–22 and the
similar block at 28–36).

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx (2)

54-54: ⚠️ Potential issue | 🔴 Critical

:::nota is not a valid Docusaurus admonition type — still unresolved.

The past review flagged this; the fix has not been applied. :::nota will not render as an admonition and may cause an MDX parse error. Replace with :::note.

🤖 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/changing-the-flash-device.mdx`
at line 54, The MDX admonition token ":::nota" is invalid and should be replaced
with the correct Docusaurus admonition ":::note"; locate the offending token
":::nota" in the document (the admonition block starting with ":::nota") and
change it to ":::note" so the admonition renders correctly and avoids MDX parse
errors.

---

65-67: ⚠️ Potential issue | 🔴 Critical

:::precaución is invalid and duplicates the :::caution opener below it — still unresolved.

The past review flagged both of these lines. The invalid Spanish admonition at line 65 and the valid :::caution at line 67 are back-to-back with no closing ::: between them, causing a parse error. Remove line 65.

🤖 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/changing-the-flash-device.mdx`
around lines 65 - 67, Remove the invalid Spanish admonition opener
":::precaución" that duplicates the valid ":::caution" opener; locate the
consecutive lines containing ':::precaución' and ':::caution' and delete the
':::precaución' line so only the valid ':::caution' remains, then verify there
is a matching closing ':::' for the ':::caution' block (add one if it's
missing).

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx (1)

4-12: ⚠️ Potential issue | 🔴 Critical

Localized JSX style keys still present — layout will be broken.

The past review flagged that margen, maxAnchura, "columna", and "centro" are silently ignored by React. Despite the AI summary claiming these were fixed, the actual code still contains all four Spanish keys. The <div> will render with no centering, no max-width, and incorrect flex direction.

🤖 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 4 - 12, The JSX style object on the <div> uses Spanish keys
(margen, maxAnchura, columna, centro) which React ignores; update the style keys
in this <div> to use the correct React/CSS-in-JS names: replace "margen" with
margin, "maxAnchura" with maxWidth (preserve the "600px" value), "columna" with
flexDirection: "column", and "centro" with alignItems: "center" so the
centering, max-width and flex layout work as intended.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx (1)

6-13: ⚠️ Potential issue | 🔴 Critical

Unresolved: translated React style keys/values still break the container layout.

Line 8-Line 12 still contain invalid JSX style keys/values for React.

🐛 Proposed fix

 <div
 style={{
- margen: "auto",
- maxAnchura: "600px",
+ margin: "auto",
+ maxWidth: "600px",
  display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
+ flexDirection: "column",
+ alignItems: "center",
 }}
 >

#!/bin/bash
# Verify unresolved translated style tokens in this file.
rg -n -C2 'margen|maxAnchura|flexDirection:\s*"columna"|alignItems:\s*"centro"' \
  i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx

Based on learnings, wrapping style-bearing JSX in mdx-code-block in source docs can help prevent Crowdin from translating JSX tokens.

🤖 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 6 - 13, Replace the translated/invalid JSX style tokens with the
correct React style keys and values: change "margen" to margin, "maxAnchura" to
maxWidth, flexDirection: "columna" to flexDirection: "column", and alignItems:
"centro" to alignItems: "center" in the JSX style object (the element containing
style={{ ... }}). After fixing those keys/values, consider protecting
style-bearing JSX from future translations by wrapping it in an mdx-code-block
in the source document to prevent Crowdin from altering the tokens.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx (2)

94-94: ⚠️ Potential issue | 🟠 Major

Fix duplicated section title: first block should be “con URL de respaldo”.

Line 94 and Line 133 currently use the same “sin URL de respaldo” heading. The first block describes fallback access behavior and should be the “con URL de respaldo” section.

🔧 Proposed fix

-#### HTTPS con certificado Myunraid.net y sin URL de respaldo
+#### HTTPS con certificado Myunraid.net y con URL de respaldo

Also applies to: 133-133

🤖 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/securing-your-connection.mdx`
at line 94, The section heading "#### HTTPS con certificado Myunraid.net y sin
URL de respaldo" is duplicated; update the first occurrence (the block that
describes fallback access behavior) to read "#### HTTPS con certificado
Myunraid.net y con URL de respaldo" so the two headings correctly reflect their
respective blocks; search for the two identical headings and change the first
one to "con URL de respaldo" to match the described content.

---

63-63: ⚠️ Potential issue | 🔴 Critical

Use valid Docusaurus admonition types instead of localized keywords.

:::advertencia, :::importante, :::precaución, :::consejo, and :::nota are not standard admonition types and can render incorrectly. Use supported type keywords and localize only the body/title text.

🔧 Proposed fix

-  :::advertencia
+  :::warning
@@
-  :::importante
+  :::warning
@@
-  :::precaución
+  :::warning
@@
-  :::consejo[Acceso alternativo]
+  :::tip[Acceso alternativo]
@@
-  :::precaución
+  :::warning
@@
-  :::nota
+  :::note
@@
-  :::consejo
+  :::tip

#!/bin/bash
# Verify non-standard admonition types in this file.
FILE="i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx"
rg -n '^\s*:::(advertencia|importante|precaución|consejo|nota)\b' "$FILE"
# Expected: no matches

Also applies to: 86-86, 106-106, 127-127, 150-150, 170-170, 218-218

🤖 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/securing-your-connection.mdx`
at line 63, Replace non-standard localized admonition markers (:::advertencia,
:::importante, :::precaución, :::consejo, :::nota) with Docusaurus-supported
admonition types and keep the Spanish titles as the visible label; e.g., change
:::advertencia to :::danger (or :::danger Advertencia), :::precaución to
:::caution (or :::caution Precaución), :::consejo to :::tip (or :::tip Consejo),
:::nota to :::note (or :::note Nota), and map :::importante to an appropriate
supported type such as :::info or :::note while preserving the Spanish title
(e.g., :::info Importante); update every occurrence (the diff shows
:::advertencia and additional instances at the other listed locations) so the
admonition keyword is valid but the displayed title remains localized.

i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (2)

56-66: ⚠️ Potential issue | 🔴 Critical

Fix invalid JSX style keys/values (still unresolved).

The inline style object uses Spanish identifiers/values (margen, maxAnchura, columna, centro), which are invalid in React style props and can break rendering.

✅ Proposed fix

 <div
 style={{
- margen: "auto",
- maxAnchura: "600px",
+ margin: "auto",
+ maxWidth: "600px",
  display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
+ flexDirection: "column",
+ alignItems: "center",
 }}
 >

#!/bin/bash
# Verify invalid React style keys/values in this file
rg -n 'margen|maxAnchura|flexDirection:\s*"columna"|alignItems:\s*"centro"' i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx

🤖 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-connect/automated-flash-backup.mdx`
around lines 56 - 66, The JSX inline style on the <div style={...}> uses Spanish
keys/values and must be replaced with valid React style names/values: change
"margen" to margin, "maxAnchura" to maxWidth, set flexDirection to "column" (not
"columna") and alignItems to "center" (not "centro"); keep the existing values
(e.g., margin: "auto", maxWidth: "600px") and ensure the object uses camelCase
keys so the <div style={...}> renders correctly.

---

121-125: ⚠️ Potential issue | 🔴 Critical

Unescape admonition label so Docusaurus parses it correctly (still unresolved).

:::note\[Reminder] should be :::note[Reminder].

✅ Proposed fix

-:::note\[Reminder]
+:::note[Reminder]

#!/bin/bash
# Verify escaped admonition labels in this file
rg -n ':::note\\\[' i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx

🤖 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-connect/automated-flash-backup.mdx`
around lines 121 - 125, Replace the escaped admonition label
`:::note\[Reminder]` with the correct Docusaurus syntax `:::note[Reminder]` so
the admonition parses properly; search for the exact token `:::note\[Reminder]`
in the document and update it to `:::note[Reminder]` (ensure there are no other
backslashes escaping the bracket in nearby admonitions).

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx (1)

362-364: ⚠️ Potential issue | 🔴 Critical

Malformed admonition syntax will break tip rendering.

:::提示 is not a valid Docusaurus admonition type, and the closing fence must be on its own line.

🐛 Proposed fix

-  :::提示
-  如果您不使用 GPLPV 驱动程序，可以跳过接下来的几个步骤，并从进入 %%KVM|kvm%% 模式部分继续。  :::
+  :::tip
+  如果您不使用 GPLPV 驱动程序，可以跳过接下来的几个步骤，并从进入 %%KVM|kvm%% 模式部分继续。
+  :::

#!/bin/bash
# Verify non-standard admonition types and inline close fences in this file.
rg -n ':::提示|:::\S+\s.*:::$|::提示|::注意' i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx`
around lines 362 - 364, The admonition uses an invalid type and inline closing
fence: replace the invalid ":::提示" with a valid Docusaurus admonition token
(e.g., ":::tip" or ":::note") and ensure the closing fence is on its own line as
":::". Specifically, update the offending block that starts with ":::提示" so it
becomes ":::tip" (or ":::note") and move the trailing " :::" to a separate line
containing only ":::", preserving the admonition content between them (search
for the exact ":::提示" token to locate the block).

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx (1)

65-72: ⚠️ Potential issue | 🔴 Critical

Duplicate admonition opener and broken list structure around lines 65–72.

Two issues persist in this block:

1. :::注意 在你替换之前 on line 65 is a non-standard (Chinese) admonition keyword and duplicates the valid :::note 在你替换之前 opener on line 67. The :::注意 line should be removed (flagged in a previous review).
2. The closing ::: on line 72 falls inside numbered list item 3 (indented), which closes the note block mid-list and leaves items 4 onward (lines 73–74) outside the admonition, breaking the intended structure.

🐛 Proposed fix

-:::注意 在你替换之前
-
 :::note 在你替换之前

 1. 定期备份您的闪存设备，尤其是在进行重大配置更改后。
 2. 在服务器之外存储备份（在另一台计算机或云存储上）。
 3. 在任何硬件更改后保留磁盘分配的截图。
-   :::
 4. 如果发现并修复错误，您可以继续使用设备。如果问题持续或重复，建议更换。
+
+:::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx`
around lines 65 - 72, Remove the duplicate non-standard admonition opener ":::注意
在你替换之前" and keep only the valid ":::note 在你替换之前"; then ensure the admonition
closing marker ":::" is moved out of the indented numbered list (so it appears
after the full list, not indented inside item 3) to preserve the list inside the
note block and restore correct MDX admonition structure.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx (1)

63-65: ⚠️ Potential issue | 🔴 Critical

Non-standard Chinese admonition keywords still present — these were flagged in a previous review.

All Chinese-character admonition type identifiers remain unfixed. Docusaurus will not apply icon, color, or heading styling to these blocks. Replace each with the standard English keyword:

Line	Current	Replace with
63	:::警告	:::warning
86	:::重要	:::caution
106	:::注意	:::note
123	:::信息	:::info
127	:::提示[后备访问]	:::tip[后备访问]
150	:::注意	:::note
170	:::注意	:::note
218	:::提示	:::tip

Also applies to: 86-88, 106-108, 123-125, 127-129, 150-151, 170-172, 218-220

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx`
around lines 63 - 65, Replace all non-standard Chinese admonition markers with
Docusaurus standard English keywords: change :::警告 → :::warning, :::重要 →
:::caution, :::注意 → :::note, :::信息 → :::info, :::提示[...] → :::tip[...] and :::提示
→ :::tip; locate each Chinese-marker instance (e.g., ":::警告", ":::重要", ":::注意",
":::信息", ":::提示", ":::提示[后备访问]") in the MDX and update them to the exact
replacements so Docusaurus will apply correct icon, color, and heading styling.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (5)

104-106: Bullet-point text still incorrectly used as H2 heading.

This was flagged in the previous review and remains unfixed. The bullet description has been promoted to a heading, which breaks the TOC and section structure.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 104 - 106, The line currently rendered as an H2 ("## **Verhinderung
von versehentlichem Verlust:** Reduzieren Sie das Risiko von Datenverlusten beim
Formatieren oder Ersetzen von Geräten.") should be changed back into a
bullet-point/paragraph under the surrounding section so it does not become a
top-level heading; locate that exact heading text in
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
and replace the leading "## " and heading markup with a normal bullet or
sentence (e.g., "- Verhinderung von versehentlichem Verlust: Reduzieren Sie das
Risiko..." or plain paragraph) so the TOC and section hierarchy remain intact
and the subsequent "Um eine Festplatte zu einem %%BTRFS|btrfs%%-Pool
hinzuzufügen:" stays as the proper subsection.

---

83-94: Duplicate subsection and repeated content still present.

The H3 at line 83 duplicates the H2 at line 64, and lines 85–94 repeat content already present in the parent section. This was flagged in a previous review and remains unfixed.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 83 - 94, Remove the duplicated subsection titled "Hinzufügen von
Laufwerken zur Erstellung eines Mehrgerätepools" and the repeated paragraph and
list content that duplicates the parent "Mehrgerätemodus" section; retain the
canonical H2 content (the original section at “Mehrgerätemodus” / the parent
explanation) and delete the redundant H3 block and its steps (the paragraph
starting with "Sobald Ihr Pool..." and the numbered steps) so the document no
longer repeats the same instructions. Ensure any unique guidance that exists
only in the duplicated block is merged into the parent section instead of
keeping both.

---

29-39: Broken admonition title and orphaned closing delimiter persist.

Line 29 :::info[Keep Sie] still mixes English and German. Line 39 still has an orphaned ::: delimiter. These issues remain unfixed from the previous review.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 29 - 39, Replace the mixed-language admonition title and remove the
orphaned closing delimiter: change the opening marker ":::info[Keep Sie]" to a
proper German title such as ":::info[Hinweis]" (or another appropriate German
phrase) so the admonition reads consistently, and remove the extra trailing ":::
" so there is exactly one matching closing ":::". Ensure the content between the
":::info[...]" and its single "::: " remains intact.

---

144-144: Missing closing bracket in admonition title still present.

:::tip[Planning für zukünftige Erweiterung. is still missing the closing ]. Previously flagged.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
at line 144, The admonition title token ':::tip[Planning für zukünftige
Erweiterung.' is missing the closing bracket; locate that string and add the
closing ']' so it becomes ':::tip[Planning für zukünftige Erweiterung]' (ensure
you do not alter surrounding punctuation or remove the leading/triple-colon
admonition marker).

---

253-279: Disk replacement content still misplaced in "Minimum free space" section.

Lines 253–279 remain scrambled: the "Mindestfreier Speicherplatz" heading contains disk replacement prerequisites, mixed numbered steps, and an unrelated timing note. Previously flagged.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 253 - 279, The "Mindestfreier Speicherplatz für einen Cache-Pool"
section currently contains disk-replacement prerequisites and procedural steps
that belong to the disk-replacement guide; remove the unrelated content from
this heading and keep only information about viewing/setting minimum free space
(e.g., the sentence about clicking the pool name in Main → Individuelle
Pooleinstellungen and the recommendation about setting 10–20 GB), then relocate
the prerequisites note block (the :::note with RAID/hot-swap/drive size
guidance), the numbered replacement steps (the array stop, assign new drive,
start array, monitor recovery), and any mention of assigning the new drive slot
into the appropriate disk-replacement section titled something like "Ersetzen
einer Festplatte im Cache-Pool" so the heading "Mindestfreier Speicherplatz für
einen Cache-Pool", the :::note\[Prerequisites], the numbered list items, and the
:::important\[Timing] block are each placed under the correct headings (search
for those exact headings/blocks to find and move them).

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (2)

418-425: Stray ::: inside bullet list still present.

The orphaned ::: at line 422 between bullet points remains unfixed from the previous review. This will cause an MDX parse error.

🤖 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 418 - 425, Remove the orphaned "::: " token that sits between
bullet points in the Markdown list (the stray line with ":::") so the MDX parser
no longer errors; if the intent was to open/close an admonition, instead wrap
the related list items in a proper admonition block (e.g., start with ":::note"
before the list and end with "::: " after) and ensure the closing "::: " is not
left inline between list items—update the section around the bullet list to
either remove the stray "::: " or correctly place the admonition start/end
markers.

---

38-48: Duplicate ZFS heading and heading-content mismatch still present.

Line 38 ### %%ZFS|zfs%% labels EXT4 content, and line 46 ### ZFS duplicates the heading for the actual ZFS content. Previously flagged.

🤖 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 38 - 48, The file has a duplicated/mismatched heading: the block
starting with "### %%ZFS|zfs%%" contains EXT4 content, while a later "### ZFS"
repeats ZFS; update the first heading to match the EXT4 content (e.g., change
"### %%ZFS|zfs%%" to "### %%EXT4|ext4%%" or "### EXT4") and ensure any inline
cross-ref tokens in that block (like %%XFS|xfs%%, %%BTRFS|btrfs%%, %%ZFS|zfs%%,
%%parity|parity%%) remain correct; remove or consolidate the duplicate "### ZFS"
heading if necessary so there is a single, correctly labeled ZFS section
(referencing the "### %%ZFS|zfs%%" / "### ZFS" headings and the EXT4 paragraph).

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx (1)

283-283: ⚠️ Potential issue | 🟠 Major

Restore explicit anchors to prevent broken internal links.

Links at Line 100 and Line 101 still point to #allocation-method and #split-level. Without explicit IDs on these headings, those links will not resolve reliably.

🔧 Suggested fix

-### 分配方法
+### 分配方法 {`#allocation-method`}
...
-### 分级水平
+### 分级水平 {`#split-level`}

Also applies to: 362-362

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx`
at line 283, The internal links pointing to `#allocation-method` and `#split-level`
are broken because the headings lack explicit IDs; update the headings "分配方法"
and the corresponding "分割级别" heading to include explicit anchor IDs that match
the links (e.g., change the Markdown headings to include {`#allocation-method`}
and {`#split-level`} respectively, such as "### 分配方法 {`#allocation-method`}" and
"### 分割级别 {`#split-level`}") so the existing links resolve reliably.

i18n/de/docusaurus-plugin-content-docs/current/API/index.mdx (1)

71-75: Previously reported issue still present: broken card link target.

Line 71 still uses href="./künftige Funktionen" (contains a space), so this remains the same unresolved link-path concern already raised in earlier review feedback.

🤖 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/index.mdx` around lines 71
- 75, The Card component's href contains an invalid space ("href=\"./künftige
Funktionen\"") which breaks the link target; update the Card's href in the Card
title="Künftige Funktionen" element to a filesystem/URL-safe path (e.g. replace
the space with a hyphen or percent-encode it) such as
href="./künftige-funktionen" or href="./künftige%20Funktionen" so the link
resolves correctly to the target document.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (1)

212-223: Previously flagged critical issue — translated CSS property names are still unresolved.

Lines 214–218 still contain Spanish-translated CSS keys/values (margen, maxAnchura, "columna", "centro") that are invalid in React's style prop and will cause the image wrapper to render completely unstyled.

🤖 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 JSX style object on the div (the inline style passed
to the <div> wrapper around the image) uses Spanish property names — update the
style keys to valid React/CSS-in-JS camelCase names: replace "margen" with
margin, "maxAnchura" with maxWidth, "columna" with "column" for flexDirection,
and "centro" with "center" for alignItems so the inline style on that div
renders correctly.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (2)

178-190: Previously flagged malformed admonition title :::tip[Optimizing 硬盘数量 (missing closing ]) is still unresolved.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 178 - 190, The admonition opener ':::tip[Optimizing 硬盘数量' is
missing its closing bracket; update it to ':::tip[Optimizing 硬盘数量]' (or use the
alternative ':::tip Optimizing 硬盘数量') so the admonition parses correctly,
keeping the existing closing ':::' as-is; locate the string ':::tip[Optimizing
硬盘数量' in the ZFS storage doc and fix that token.

---

141-155: Previously flagged issues — stray :::, misplaced strip warning, and duplicate image are still unresolved.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 141 - 155, Remove the stray ":::” block, move the striped-volume
warning sentence ("**条带** 只适用于非关键性、临时数据 - 如果任何磁盘故障，您将失去所有数据。") so it directly
follows the step that creates a striped vdev (keep the bold "条带" text intact),
and delete the duplicated image block referencing "/img/zfs9.png" so only one
illustrative image remains; locate these in the zfs-storage.mdx content around
the steps that mention Main, stop array, select disks, and 文件系统 to apply the
fixes.

i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx (1)

252-254: ⚠️ Potential issue | 🔴 Critical

Remove the orphan closing admonition token.

Line 254 adds an extra ::: after the info block is already closed at Line 252, which can break MDX rendering.

Proposed fix

 :::
-
-:::

🤖 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/how-to-use-the-api.mdx`
around lines 252 - 254, The file contains an orphan closing admonition token
":::": the info block opened/closed around the content is already terminated
(the closing ":::") and there is an extra standalone ":::” that should be
removed; locate the duplicated closing token (the second ":::") and delete it so
the admonition block is properly balanced and MDX rendering won't break.

i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx (1)

59-75: ⚠️ Potential issue | 🔴 Critical

Non-English icon props and spaces in href paths remain unresolved.

The issues previously flagged on these lines are still present:

• icon="código" / icon="escudo" / icon="cohete" will fail to resolve.
• href="./configuración del proveedor OIDC" and href="./características Futuras" contain literal spaces, producing broken navigation.

🤖 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 59
- 75, The Card components use non-English icon names and hrefs with spaces which
will break resolution; update the icon props in the three Card instances (titles
"Usando la API de Unraid", "Configuración OIDC", "Características Futuras") to
the expected English icon keys (e.g., "code", "shield", "rocket") and replace
the href values that contain spaces with valid paths that match the actual
filenames (e.g., kebab-case or URL-encoded names such as
"./configuracion-del-proveedor-oidc" and "./caracteristicas-futuras" or the
exact existing file slugs), ensuring the hrefs point to existing doc files.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx (1)

141-150: ⚠️ Potential issue | 🔴 Critical

::::Hinweis is not a valid Docusaurus admonition keyword.

The German word "Hinweis" is not recognized by Docusaurus. The admonition will not render.

🤖 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/shares.mdx`
around lines 141 - 150, The admonition header "::::Hinweis[Alternative
Methoden]" is invalid; replace the custom German tag with a supported Docusaurus
admonition such as ":::note[Alternative Methoden]" or ":::tip[Alternative
Methoden]" and update the closing "::::" to ":::". Locate the block containing
"::::Hinweis[Alternative Methoden]" and the matching closing "::::" and change
both to the chosen valid admonition markers so the admonition renders correctly.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Section heading/content mismatch and duplicated image.

Three issues in this block:

1. "### Virtuelle Maschinen" (Line 170) contains Power Mode description (Line 172) — the heading says VMs but the body describes the power-mode setting.
2. "### Bestätigungen" (Line 180) has a %%User shares|user-share%% description on Line 182, which belongs to a shares section, not a confirmations section.
3. The image ![Leistungsmodus](/img/settings-powermode.png) at Lines 184–186 is a verbatim duplicate of the one at Lines 176–178.

This appears to be garbled content introduced during Crowdin translation sync.

🧰 Tools

🪛 LanguageTool

[grammar] ~172-~172: Ersetze das Satzzeichen
Context: ...en. Sie können aus den verfügbaren Modi - Beste Energieeffizienz, **Ausgewoge...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_DASH_–)

---

[grammar] ~172-~172: Passe die Groß- und Kleinschreibung an
Context: ...Sie können aus den verfügbaren Modi - Beste Energieeffizienz, **Ausgewogener Betr...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)

---

[grammar] ~172-~172: Passe die Groß- und Kleinschreibung an
Context: ...en Modi - Beste Energieeffizienz, Ausgewogener Betrieb oder Beste Leistung - wäh...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)

---

[grammar] ~172-~172: Passe die Groß- und Kleinschreibung an
Context: ...ienz**, Ausgewogener Betrieb oder Beste Leistung - wählen, um Ihren Arbeitsla...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)

---

[grammar] ~172-~172: Ersetze das Satzzeichen
Context: ...gener Betrieb** oder Beste Leistung - wählen, um Ihren Arbeitslasten und Ener...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_DASH_–)

🤖 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`
around lines 170 - 186, The block has mismatched headings and a duplicated
image: move the Power Mode paragraph (the text referencing Power Mode) under a
correct heading (replace or rename "### Virtuelle Maschinen" to "###
Leistungsmodus" or move the paragraph to a "Power Mode"/"Leistungsmodus"
section), relocate the %%User shares|user-share%% paragraph out of "###
Bestätigungen" into a proper "User shares"/"Freigaben" section (or rename "###
Bestätigungen" if it was meant to be "### Freigaben"), and remove the duplicate
image reference to /img/settings-powermode.png so the screenshot appears only
once next to the Power Mode section; ensure headings "### Virtuelle Maschinen",
"### Bestätigungen", the "Power Mode" paragraph, and the %%User
shares|user-share%% text are consistently matched after the change.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Multiple additional section heading/content mismatches.

• "### Bestätigungen {#ups-settings}" (Line 188): The body text (Line 190) describes console settings (keyboard layout, screen timeout, Bash history) — the heading says "Bestätigungen" (Confirmations) and the anchor says #ups-settings (UPS Settings). Neither matches the content.
• "### Benachrichtigungseinstellungen" (Lines 206–214): The content on Line 206 is the English "Network Services" paragraph about NFSv4/FTP, and Line 210 is an NFS screenshot. None of this is notification-related.
• "### Benutzerprogramme" (Line 216): The image on Lines 220–222 shows settings-smb.png (SMB settings), which does not match a third-party plugins section.

These all appear to be content blocks from other sections accidentally inserted here during the Crowdin sync. Please reconcile each heading with its intended body.

🧰 Tools

🪛 LanguageTool

[grammar] ~198-~198: Passe das Symbol an
Context: ...an, indem Sie das Datums- und Zeitformat, das Zahlenformat anpassen und zwischen ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~198-~198: Passe die Groß- und Kleinschreibung an
Context: ... zwischen Registerkartensicht und nicht registerkartensicht umschalten. Sie können auch die Tempera...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_LOWERCASE)

---

[grammar] ~206-~206: Korrigiere die Fehler
Context: ... Network Services let you configure network communication protocols on your Unraid ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~206-~206: Korrigiere die Fehler
Context: ...rk Services** let you configure network communication protocols on your Unraid server, which ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~206-~206: Korrigiere die Fehler
Context: ...let you configure network communication protocols on your Unraid server, which are essential for ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~206-~206: Korrigiere die Fehler
Context: ...k communication protocols on your Unraid server, which are essential for user and disk ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~206-~206: Korrigiere die Fehler
Context: ...cation protocols on your Unraid server, which are essential for user and disk shares....

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~206-~206: Korrigiere die Fehler
Context: ... protocols on your Unraid server, which are essential for user and disk shares. You...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~206-~206: Korrigiere die Fehler
Context: ...tocols on your Unraid server, which are essential for user and disk shares. You can also ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~206-~206: Korrigiere die Fehler
Context: ...your Unraid server, which are essential for user and disk shares. You can also enab...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~206-~206: Korrigiere die Fehler
Context: ... Unraid server, which are essential for user and disk shares. You can also enable an...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~206-~206: Korrigiere die Fehler
Context: ...id server, which are essential for user and disk shares. You can also enable an %%F...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~206-~206: Korrigiere die Fehler
Context: ...erver, which are essential for user and disk shares. You can also enable an %%FTP|ftp%% ser...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~210-~210: Korrigiere das Wort
Context: ...in Unraid. You can enable or disable it for %%user shares|user-share%% and adjust t...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPELLING)

🤖 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`
around lines 188 - 214, Summary: Several headings and anchors don't match their
following content—sections were mixed during sync. Fix by reconciling
headings/anchors and content: replace "### Bestätigungen {`#ups-settings`}" with
"### Konsoleneinstellungen" (or move the console paragraph into the UPS section
if that was intended) and correct/remove the `#ups-settings` anchor; ensure the
console text matches settings-console.png and function name references; change
the duplicated "### Anzeigeneinstellungen" to match the display paragraph and
settings-display.png; replace the English "Network Services" paragraph under
"### Benachrichtigungseinstellungen" with the proper notification settings
content (or retitle that heading to "Netzwerkdienste"/"NFS und Dienste" and
update anchor) so it matches settings-nfs.png and the NFSv4/FTP text; finally
ensure "### Benutzerprogramme" either contains third-party plugins text or swap
in the SMB content and settings-smb.png where appropriate—move misplaced blocks
back to their correct sections and update anchors and headings to uniquely
identify each section (Konsoleneinstellungen, Anzeigeeinstellungen,
Netzwerkdienste, Benutzerprogramme) so headings, anchors, body text, and images
align.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Remove placeholder/draft artifact — not release-note content.

Line 157 (- vielleicht hatten wir keinen Platz mehr, i.e. "maybe we had no more space") is an editorial draft note accidentally committed as a list item in the Docker shares section. This text has no counterpart in the source release notes and will appear verbatim to German-speaking readers.

🐛 Proposed fix

 - appdata - wird von Docker-Anwendungen verwendet, um Anwendungsdaten zu speichern.
-- vielleicht hatten wir keinen Platz mehr
-
-### Vorhandene Freigaben verwalten

🧰 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`
around lines 157 - 158, Remove the accidental draft list item "- vielleicht
hatten wir keinen Platz mehr" from the German release notes file (present in the
Docker shares section) so it no longer appears in the rendered document; edit
the functionally named content in "7.0.0.md" by deleting that specific bullet,
ensure no other draft artifacts remain in the same section, and run a quick
local render or spellcheck to confirm the release-note content is clean before
committing.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

## powerdown section description is about file transfers, not shutdown.

Line 444 is ## powerdown, but line 446 reads: "Diese Methoden helfen Ihnen, Dateien von externen Netzwerkspeicherfreigaben … zu übertragen." This description belongs to the file-transfer/copy section, not the powerdown (shutdown) command.

🧰 Tools

🪛 LanguageTool

[grammar] ~446-~446: Ergänze ein Satzzeichen
Context: ...rkspeicherfreigaben (Windows- oder Linux SMB/CIFS-Freigaben) auf Ihren Unraid-Ser...

(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_LINUXDASHSMB)

🤖 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/advanced-tools/command-line-interface.mdx`
around lines 444 - 446, The "## `powerdown`" header currently has a paragraph
about transferring files from network shares (the SMB/CIFS description) which is
incorrect; under the section identified by the header symbol `powerdown` remove
or replace that file-transfer paragraph with a concise description of the
shutdown command (what `powerdown` does, that it cleanly shuts down the server,
and any common usage/flags or how to invoke it from the CLI). Alternatively, if
the SMB/CIFS paragraph belongs elsewhere, move that text into the appropriate
file-transfer/copy section and ensure the `powerdown` section only contains
shutdown-specific content and examples.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Stray ::: — orphaned admonition closing marker.

Line 161–162 contains a bare ::: indented inside the last list item of the "Um den Zugriff wiederherzustellen:" block, with no corresponding opening ::: in scope. The :::caution block earlier (lines 151–153) is already properly closed. This orphan marker may trigger an MDX parse error or render as unwanted literal text.

🐛 Proposed fix

   - Sobald %%DNS|dns-name-resolution%% wiederhergestellt ist, setzen Sie **SSL/TLS verwenden** zurück auf *Strikt* für volle Sicherheit.
-    :::

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::
	- Sobald %%DNS|dns-name-resolution%% wiederhergestellt ist, setzen Sie **SSL/TLS verwenden** zurück auf *Strikt* für volle Sicherheit.

🤖 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/securing-your-connection.mdx`
around lines 161 - 162, Remove the stray orphaned admonition closing marker
":::“ found inside the last list item of the "Um den Zugriff
wiederherzustellen:" block; ensure the earlier :::caution block (around lines
where :::caution is used) remains unchanged and fully closed, and delete the
lone ":::“ token so the MDX parses correctly and no extra literal text is
rendered.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Removing the explicit anchor breaks an internal link.

Line 451 references #checking-a-file-system:

[Vérification d'un système de fichiers](`#checking-a-file-system`)

That anchor came from the {#checking-a-file-system} that was removed from this heading. Without it, the auto-generated French slug will differ and the link will break.

🐛 Proposed fix — restore the anchor

-### Vérifier un système de fichiers
+### Vérifier un système de fichiers {`#checking-a-file-system`}

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	### Vérifier un système de fichiers
	### Vérifier un système de fichiers {`#checking-a-file-system`}

🤖 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/manage-storage/file-systems.mdx`
at line 483, Restore the explicit anchor that was removed so internal link
`[Vérification d'un système de fichiers](`#checking-a-file-system`)` resolves: add
the anchor `{`#checking-a-file-system`}` to the heading "### Vérifier un système
de fichiers" (e.g., append the anchor directly after the heading text) so the
slug matches the referenced fragment and the internal link is not broken.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

# Check if the file exists and read lines 55-65 for context
if [ -f "i18n/zh/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx" ]; then
  echo "=== File content (lines 55-65) ==="
  sed -n '55,65p' "i18n/zh/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx"
  echo ""
  echo "=== Checking for unclosed admonition brackets ==="
  rg -nP '^:::[a-zA-Z]+\[[^\]]*$' "i18n/zh/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx"
else
  echo "File not found"
fi

Repository: unraid/docs

Length of output: 308

---

Fix malformed admonition syntax: missing closing bracket ] on Line 58.

The opening bracket in :::note[Server 需要上下文 is never closed, breaking MDX parsing. Change to:

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.

Suggested change

	:::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 admonition opener ":::note[Server 需要上下文" is missing a
closing bracket which breaks MDX parsing; edit the admonition to ":::note[Server
需要上下文]" (i.e., add the trailing ]) and ensure the block is properly terminated
with a closing ":::", so update the ":::note[Server 需要上下文" line and verify the
corresponding closing ":::” exists after the admonition content.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Invalid admonition fence: four colons :::: should be three :::.

::::tip[Rules 替换规则] uses four colons, which is not valid Docusaurus admonition syntax and will render the block as raw text.

🐛 Proposed fix

-::::tip[Rules 替换规则]
+:::tip[Rules 替换规则]

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	::::tip[Rules 替换规则]
	:::tip[Rules 替换规则]

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx`
at line 48, Replace the invalid four-colon admonition fence `::::tip[Rules
替换规则]` with the correct three-colon Docusaurus admonition `:::tip[Rules 替换规则]`
so the tip block renders as an admonition; locate the string `::::tip[Rules
替换规则]` in the file and change it to `:::tip[Rules 替换规则]`.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Non-standard admonition keyword :::注 — replace with :::note.

:::注 uses a Chinese character as the admonition type, which Docusaurus does not recognise. This block will not render with the expected icon or styling.

🐛 Proposed fix

-  :::注
+  :::note

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx`
at line 54, Replace the non-standard admonition token `:::注` with the standard
Docusaurus admonition `:::note` so the block renders correctly; search for the
string `:::注` in the document and change it to `:::note`, preserving the block
content and closing token (if any) to retain the original text and styling.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

# Find all cache-pools.mdx files in the repo
echo "=== All cache-pools.mdx files ==="
fd --type f "cache-pools.mdx" --full-path

# Check the zh locale version specifically
echo -e "\n=== Checking zh locale cache-pools.mdx for btrfs-pools anchor ==="
CACHE_POOLS_ZH="i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/cache-pools.mdx"
if [ -f "$CACHE_POOLS_ZH" ]; then
    echo "File exists at: $CACHE_POOLS_ZH"
    echo -e "\n--- Searching for btrfs-pools anchor ---"
    grep -n "btrfs-pools" "$CACHE_POOLS_ZH" || echo "No btrfs-pools anchor found"
else
    echo "File NOT found at expected location: $CACHE_POOLS_ZH"
fi

# Verify the relative path resolution
echo -e "\n=== Path resolution verification ==="
echo "File under review: i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx"
echo "Relative path in link: ../cache-pools.mdx"
echo "Expected resolved path: i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/cache-pools.mdx"
if [ -f "$CACHE_POOLS_ZH" ]; then
    echo "✓ Resolved path EXISTS"
else
    echo "✗ Resolved path DOES NOT EXIST"
fi

Repository: unraid/docs

Length of output: 1107

---

🏁 Script executed:

#!/bin/bash

# Check for btrfs-pools anchor in the correct location
CACHE_POOLS_ZH="i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx"
echo "=== Checking for btrfs-pools anchor in correct file ==="
if [ -f "$CACHE_POOLS_ZH" ]; then
    echo "File EXISTS at: $CACHE_POOLS_ZH"
    echo -e "\n--- Searching for btrfs-pools anchor/heading ---"
    grep -n "btrfs-pools\|BTRFS.*池" "$CACHE_POOLS_ZH" | head -20
else
    echo "File NOT found"
fi

Repository: unraid/docs

Length of output: 1524

---

Fix the relative path for the BTRFS pools link — it resolves to a non-existent file.

The link ../cache-pools.mdx#btrfs-pools incorrectly goes up one directory level. Both file-systems.mdx and cache-pools.mdx are in the same directory (manage-storage/), so the path should be ./cache-pools.mdx#btrfs-pools or cache-pools.mdx#btrfs-pools. The #btrfs-pools anchor does exist in the target file at line 114, but the broken relative path prevents the link from working.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
at line 102, The relative link in file-systems.mdx currently points to
"../cache-pools.mdx#btrfs-pools" which goes up one directory and breaks; update
the link in the sentence referencing %%BTRFS|btrfs%% to use the correct
same-directory path "cache-pools.mdx#btrfs-pools" (or
"./cache-pools.mdx#btrfs-pools") so it resolves to the anchor in
cache-pools.mdx; locate the link string in file-systems.mdx and replace the path
accordingly.

[coderabbitai]

Actionable comments posted: 19

Note

Due to the large number of review comments, Critical severity comments were prioritized as inline comments.

♻️ Duplicate comments (47)

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx (1)

48-49: ⚠️ Potential issue | 🔴 Critical

Stray ::: still breaks page rendering.

The :::important block is already closed at line 46. The orphaned ::: at line 48 has no matching opening directive and will either fail the MDX build or silently corrupt all subsequent content into an unclosed admonition.

🐛 Proposed fix — remove the stray directive

 :::

-:::
-
 ### Herunterladen und entpacken

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx`
around lines 48 - 49, Remove the stray closing admonition token ':::' that has
no opening directive (the orphaned ':::' after the ':::important' block); locate
the orphaned ':::' in the MDX content (the lone closing directive following the
':::important' block) and delete it so the admonition is properly closed only
once and the remainder of the document renders correctly.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx (1)

283-283: ⚠️ Potential issue | 🟠 Major

Restore explicit anchors to keep current fragment links working.

Line 100 and Line 101 still link to #allocation-method and #split-level. After removing IDs on Line 283 and Line 362, those links will no longer resolve to these sections.

🐛 Suggested fix

-### 分配方法
+### 分配方法 {`#allocation-method`}
...
-### 分级水平
+### 分级水平 {`#split-level`}

Also applies to: 362-362

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx`
at line 283, Restore explicit HTML id anchors on the headings so existing
fragment links keep working: add id="allocation-method" to the "分配方法" heading
(the heading text currently shown as 分配方法) and id="split-level" to the "拆分级别"
heading (the heading where you removed the ID at the other location); ensure the
headings include the corresponding explicit anchors (e.g., <h3
id="allocation-method">分配方法</h3>) so links pointing to `#allocation-method` and
`#split-level` resolve correctly.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (2)

42-48: ⚠️ Potential issue | 🔴 Critical

Invalid CSS property names are still present in all style={{}} blocks — the AI summary claiming this was fixed is incorrect.

The AI-generated summary states the CSS was corrected, but the actual code still uses untranslatable Spanish tokens as React style keys across every <div style={{...}}> block. Browsers and React silently discard unrecognised style keys, so none of the centering, max-width, or margin styling renders.

Current (invalid)	Must be
margen	margin
maxAnchura	maxWidth
flexDirection: "columna"	flexDirection: "column"
alignItems: "centro"	alignItems: "center"

🐛 Proposed fix (apply to all ~15 occurrences)

 <div
   style={{
-    margen: "auto",
-    maxAnchura: "600px",
-    display: "flex",
-    flexDirection: "columna",
-    alignItems: "centro",
+    margin: "auto",
+    maxWidth: "600px",
+    display: "flex",
+    flexDirection: "column",
+    alignItems: "center",
   }}
 >

Also applies to: 70-76, 91-97, 112-118, 126-132, 141-147, 161-167, 173-179, 211-217, 225-231, 246-252, 294-300, 330-336, 354-362, 400-407, 419-427

🤖 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 42 - 48, Fix all inline React style objects in the MDX by replacing
Spanish property names/values with valid React/CSS keys: change margen to
margin, maxAnchura to maxWidth, flexDirection: "columna" to flexDirection:
"column", and alignItems: "centro" to alignItems: "center" in every
style={{...}} block (the repeated style blocks around the mentioned ranges);
ensure other occurrences use standard camelCase CSS keys so the centering and
max-width take effect.

---

302-302: ⚠️ Potential issue | 🔴 Critical

Pipeline still fails: /img/zfs12.png cannot be resolved.

The CI error from the pipeline confirms this is still broken:

MDX compilation failed: Markdown image with URL /img/zfs12.png couldn't be resolved to an existing local image file.

The German counterpart file uses ./assets/zfs12.png at the equivalent location. The quickest safe fix is to revert line 302 to the relative path that is already working:

🐛 Proposed fix

-![](/img/zfs12.png)
+![](./assets/zfs12.png)

🤖 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`
at line 302, In the MDX file
i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
replace the absolute image URL `/img/zfs12.png` with the working relative path
`./assets/zfs12.png` (i.e., update the image tag `![](/img/zfs12.png)` to
`![](./assets/zfs12.png)`) so the Markdown image resolves during MDX
compilation.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx (2)

63-63: ⚠️ Potential issue | 🔴 Critical

Localized admonition directives are likely invalid for Docusaurus rendering.

At Line 63, Line 86, Line 106, Line 127, Line 150, Line 170, and Line 218, directives like :::advertencia/:::consejo are not default admonition types. Unless your config explicitly registers these keywords, these callouts will not render correctly.

🔧 Proposed fix

-  :::advertencia
+  :::warning
...
-  :::importante
+  :::info
...
-  :::precaución
+  :::warning
...
-  :::consejo[Acceso alternativo]
+  :::tip[Acceso alternativo]
...
-  :::precaución
+  :::warning
...
-  :::nota
+  :::note
...
-  :::consejo
+  :::tip

#!/bin/bash
set -euo pipefail

echo "== Check Docusaurus config for custom admonition keywords =="
fd -HI 'docusaurus\.config\.(js|cjs|mjs|ts)' --exec rg -n 'admonitions|keywords|extendDefaults' {}

echo
echo "== Find localized admonition directives in this file =="
rg -n ':::(advertencia|importante|precaución|consejo|nota)\b' \
  i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx

Also applies to: 86-86, 106-106, 127-127, 150-150, 170-170, 218-218

🤖 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/securing-your-connection.mdx`
at line 63, The localized admonition directives (e.g., :::advertencia,
:::consejo, :::importante, :::precaución, :::nota) are not standard Docusaurus
admonitions and will not render unless registered; either replace each instance
with a standard admonition key (like :::warning, :::tip, :::important,
:::caution, :::note) in the MDX content or add those localized keywords to your
Docusaurus admonitions configuration (extendDefaults/keywords in the admonitions
plugin) so they map to the correct types; update every occurrence of the tokens
mentioned (:::advertencia, :::consejo, :::importante, :::precaución, :::nota)
accordingly.

---

94-94: ⚠️ Potential issue | 🟠 Major

First Myunraid section title is mismatched with its own content.

Line 94 and Line 133 currently use the same sin URL de respaldo heading. The first block includes fallback methods (IP/local hostname and alternate URL), so Line 94 should be the con URL de respaldo section title.

🔧 Proposed fix

-#### HTTPS con certificado Myunraid.net y sin URL de respaldo
+#### HTTPS con certificado Myunraid.net y con URL de respaldo

Also applies to: 133-133

🤖 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/securing-your-connection.mdx`
at line 94, Update the first section heading that currently reads "#### HTTPS
con certificado Myunraid.net y sin URL de respaldo" to "#### HTTPS con
certificado Myunraid.net y con URL de respaldo" so it matches the content (which
describes fallback methods); leave the later duplicate heading (the one that
should represent the no-fallback case) as "sin URL de respaldo" to preserve the
correct distinction between the two sections.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx (1)

63-65: Use standard Docusaurus admonition keywords (still unresolved).

The Chinese admonition markers (:::警告, :::重要, :::注意, :::信息, :::提示) are non-standard keywords for Docusaurus and may not render with expected style/icon. This concern was already raised previously and still appears in current content.

#!/bin/bash
# Verify non-standard admonition markers in this file
rg -n ':::(警告|重要|注意|信息|提示)' i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx

Also applies to: 86-88, 106-109, 123-125, 127-129, 150-152, 170-172, 218-220

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx`
around lines 63 - 65, Replace the non-standard Chinese admonition markers
(:::警告, :::重要, :::注意, :::信息, :::提示) with Docusaurus standard keywords
(:::warning, :::important, :::note, :::info, :::tip) so they render with the
correct style and icons; update every occurrence in the file (the instances
shown around the diff and the other listed occurrences) and ensure the
opening/closing admonition fences remain paired and spacing/indentation is
preserved.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx (2)

21-25: Previously flagged: duplicated paragraph and unclosed admonition with mixed-language title — still unresolved.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx`
around lines 21 - 25, Remove the duplicated paragraph and fix the unclosed
admonition: change the mixed-language admonition title "Before Sie beginnen" to
proper German "Bevor Sie beginnen", ensure the admonition block starting with
":::caution[Bevor Sie beginnen]" is properly closed with a trailing ":::", and
delete the repeated paragraph about Time Machine so only one instance remains;
locate the admonition by the token ":::caution[Before Sie beginnen]" and the
duplicated text referencing the Time Machine Docker-Container to apply these
edits.

---

28-29: Previously flagged: invalid :::Vorsicht admonition keyword — still unresolved.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx`
around lines 28 - 29, The admonition token ":::Vorsicht" is invalid; replace it
with a supported Docusaurus admonition keyword and include the German title,
e.g. change ":::Vorsicht" to ":::caution Vorsicht" (or ":::warning
Vorsicht"/":::danger Vorsicht" if stronger) so the admonition renders correctly;
update the block where ":::Vorsicht" appears in apple-time-machine.mdx
accordingly.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (2)

178-190: ⚠️ Potential issue | 🔴 Critical

Close the admonition title bracket to keep MDX valid.

Line 178 uses :::tip[Optimizing 硬盘数量 without the closing ], which breaks admonition syntax.

Proposed fix

-:::tip[Optimizing 硬盘数量
+:::tip[Optimizing 硬盘数量]

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 178 - 190, The MDX admonition opening ":::tip[Optimizing 硬盘数量" is
missing the closing bracket which invalidates the admonition syntax; fix by
adding the missing closing bracket so it reads ":::tip[Optimizing 硬盘数量]" (ensure
there is a matching closing ":::") and verify the block content between
":::tip[...]" and the terminating ":::” remains intact.

---

141-155: ⚠️ Potential issue | 🔴 Critical

Fix misplaced step content, orphan ::: marker, and duplicate screenshot usage.

Line 143 inserts a Stripe warning as a numbered action step, Line 144 has an orphan closing :::, and Line 148/Line 154 use the same screenshot for different steps. This is still structurally broken in the workflow section.

Proposed structural fix

 1. 在 %%WebGUI|web-gui%% 中转到 **Main** 标签。
 2. 停止%%array|array%%。
-3. **条带** 只适用于非关键性、临时数据 - 如果任何磁盘故障，您将失去所有数据。
-   :::
-4. 选择您要添加的磁盘。
+3. 选择您要添加的磁盘。

Also replace one of the duplicate image references so “选择磁盘” and “选择文件系统” use distinct screenshots.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
around lines 141 - 155, Remove the stray Stripe warning from the numbered steps
(the line containing "条带 只适用于非关键性、临时数据") and delete the orphan closing marker
":::", then convert that warning into a separate admonition block placed after
step "选择您要添加的磁盘" (or otherwise outside the sequential list) so it no longer
appears as a list item; also replace one of the duplicate image references
"![](/img/zfs9.png)" so that the "选择您要添加的磁盘" step and the "在 **文件系统** 下，选择 `zfs`
或 `zfs-encrypted`" step each use distinct screenshots, and renumber the steps if
needed to keep the ordered list contiguous.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (2)

418-428: Stray ::: at line 422 inside a bullet list — already flagged.

The orphaned ::: between bullet points at line 422 was raised in a previous review and remains unaddressed.

🤖 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 418 - 428, Remove the stray "::: " token that appears between
bullet list items (it breaks markdown/admonition parsing); either delete this
orphaned "::: " or, if an admonition was intended, wrap the intended block
correctly with matching ":::note" (or other admonition marker) starting before
the content and a closing "::: " after the block so the bullets remain valid —
look for the orphaned "::: " between the bullets mentioning posting to the
Unraid forum and automating mounts to locate the exact spot (the "::: " token is
the unique symbol to remove or properly pair).

---

38-46: Duplicate ZFS heading and EXT4 content mismatch — already flagged.

The ### %%ZFS|zfs%% heading at line 38 still covers EXT4 content (lines 40–44), and a second ### ZFS heading appears at line 46. This issue was raised in a previous review and has not yet been resolved.

🤖 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 38 - 46, The heading "### %%ZFS|zfs%%" currently contains
EXT4-specific copy (the paragraph and bullet list describing EXT4) and there is
a duplicate "### ZFS" heading later; fix by moving the EXT4 paragraph and its
bullets under the correct EXT4 heading token (e.g., replace "### %%ZFS|zfs%%"
with "### %%EXT4|ext4%%" or relocate the EXT4 content to an existing
%%EXT4|ext4%% section), and remove the duplicate "### ZFS" heading so the ZFS
section uses only the correct "%%ZFS|zfs%%" heading with ZFS-specific content
(ensure headings and content match for %%ZFS|zfs%%, %%EXT4|ext4%%, and remove
any duplicated ZFS header).

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx (1)

141-150: ⚠️ Potential issue | 🔴 Critical

Invalid admonition keyword ::::Hinweis.

::::Hinweis[Alternative Methoden] uses the German word "Hinweis" as the admonition type. Docusaurus only recognizes English keywords (note, tip, info, caution, danger, warning, important). This will not render as an admonition and will appear as raw text.

Proposed fix

-::::Hinweis[Alternative Methoden]
+::::note[Alternative Methoden]

🤖 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/shares.mdx`
around lines 141 - 150, Replace the invalid German admonition marker
'::::Hinweis[Alternative Methoden]' with a supported Docusaurus keyword (e.g.,
':::note[Alternative Methoden]' or ':::info[Alternative Methoden]') and ensure
the block uses the matching triple-colon closing token (':::') instead of
'::::'; update the opening marker in the shares.mdx content where
'::::Hinweis[Alternative Methoden]' appears and change the trailing '::::' to
':::' so the admonition renders correctly.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx (1)

6-13: This previously reported JSX style translation issue is still present.

The translated style keys/values still prevent the intended layout from applying (margin/maxWidth/column/center expected).

#!/bin/bash
# Re-verify unresolved translated React style tokens in this partial
rg -n -C2 'margen:|maxAnchura:|flexDirection:\s*"columna"|alignItems:\s*"centro"' \
  i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx

🤖 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 6 - 13, The inline JSX style object uses translated Spanish
keys/values (margen, maxAnchura, "columna", "centro") which prevents CSS from
applying; update the style prop object so the keys/values are the correct
React/CSS identifiers (margin, maxWidth, flexDirection: "column", alignItems:
"center") while keeping the existing values (e.g., "auto", "600px") to restore
the intended layout.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (1)

212-223: ⚠️ Potential issue | 🟠 Major

Fix localized React style properties in this JSX block.

Line 214/215/217/218 translate React style keys/values (margen, maxAnchura, columna, centro), so the styles are ignored.

🐛 Proposed fix

 <div
 style={{
- margen: "auto",
- maxAnchura: "600px",
+ margin: "auto",
+ maxWidth: "600px",
  display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
+ flexDirection: "column",
+ alignItems: "center",
 }}
 >

#!/bin/bash
# Verify localized React style keys/values in this file
rg -n 'margen|maxAnchura|flexDirection:\s*"columna"|alignItems:\s*"centro"' \
  i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx

Based on learnings: mdx-code-block is used in this repo to preserve JSX through Crowdin translation cycles.

🤖 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 JSX style object inside the <div> uses localized
Spanish keys/values (margen, maxAnchura, flexDirection: "columna", alignItems:
"centro") so React ignores them; update the style keys/values on that div to the
correct React props and English values (margin, maxWidth, flexDirection:
"column", alignItems: "center") to restore styling (locate the div with the
style object and the image/caption JSX in the cache-pools.mdx content).

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx (1)

36-45: ⚠️ Potential issue | 🟠 Major

Restore valid React inline style keys/values in both image containers.

Line 38/39/41/42 and Line 89/90/92/93 use localized identifiers (margen, maxAnchura, columna, centro). React ignores these, so centering/max-width styling is dropped.

🐛 Proposed fix

 <div
 style={{
- margen: "auto",
- maxAnchura: "600px",
+ margin: "auto",
+ maxWidth: "600px",
  display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
+ flexDirection: "column",
+ alignItems: "center",
 }}
 >

Apply the same replacement in both blocks (Line 36-45 and Line 87-96).

#!/bin/bash
# Verify localized React style keys/values that break runtime styling
rg -n 'margen|maxAnchura|flexDirection:\s*"columna"|alignItems:\s*"centro"' \
  i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx

Based on learnings: In Docusaurus MDX files, mdx-code-block can be used as a Crowdin-safe wrapper to preserve complex JSX across translation syncs.

Also applies to: 87-96

🤖 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/apple-time-machine.mdx`
around lines 36 - 45, The inline React style object for the image container uses
localized keys/values (margen, maxAnchura, flexDirection: "columna", alignItems:
"centro") which React ignores; replace them with valid React style keys/values
(margin, maxWidth, flexDirection: "column", alignItems: "center") in the style
prop used around the image (the JSX block with style={{ ... }} and the image
markdown), and apply the same replacements in the second identical JSX image
container block; optionally wrap the corrected JSX in an mdx-code-block to keep
the JSX intact during Crowdin translation syncs.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx (1)

274-282: ⚠️ Potential issue | 🔴 Critical

CSS inline style properties still translated to Spanish — breaks layout.

Lines 274–282 still contain Spanish-translated React style prop keys/values (margen, maxAnchura, columna, centro) that were flagged in a prior review. These are not valid CSS property names/values and will be silently ignored by the browser, causing the image container to lose its centering and max-width constraints.

🤖 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 - 282, The inline style object on the JSX <div style={{ ... }}>
uses Spanish keys/values (margen, maxAnchura, columna, centro) which are
invalid; update the style object in the <div> inside the Windows VM MDX to use
the correct React/CSS property names and values: margin, maxWidth (e.g.,
"600px"), display: "flex", flexDirection: "column", and alignItems: "center" so
the container centers and respects the max width.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx (1)

263-272: ⚠️ Potential issue | 🔴 Critical

Previously flagged critical issues remain unresolved: duplicate heading, English caution body, orphaned :::, wrong admonition title.

This block still contains all four problems flagged in the prior review:

1. Duplicate ## Upgrade-Methoden (Line 263) — ## Upgrade-Methoden already exists at Line 251.
2. English admonition body (Lines 267–268) — "Expanding or modifying %%vDisk|vdisk%%..." is English in a German document.
3. Orphaned ::: (Line 272) — closes nothing; will cause an MDX parse error.
4. Mixed-language admonition title (Line 265) — :::caution[Data Verlustrisiko] should be :::caution[Datenverlustrisiko].

🤖 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 263 - 272, Remove the duplicate heading "## Upgrade-Methoden" in
this block, replace the English admonition body ("Expanding or modifying
%%vDisk|vdisk%% and partition layouts...") with the German translation already
present below, correct the admonition title to German by changing
":::caution[Data Verlustrisiko]" to ":::caution[Datenverlustrisiko]", and remove
the stray closing ":::“ that has no opening (or ensure the admonition is
properly opened/closed so the admonition wraps the German text and the
[%%snapshot|snapshot%%] link).

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx (1)

61-61: ⚠️ Potential issue | 🟠 Major

Keep the explicit safe-mode anchor to preserve existing links.

Line 61 drops {#troubleshooting-with-safe-mode}. If any docs or external references still target that id, this silently breaks deep links.

🔧 Proposed fix

-## Problemlösung im abgesicherten Modus
+## Problemlösung im abgesicherten Modus {`#troubleshooting-with-safe-mode`}

#!/bin/bash
# Verify whether the removed anchor is still referenced anywhere.
rg -n 'troubleshooting-with-safe-mode' --type md --type mdx

# Confirm whether the German plugins heading still defines the explicit anchor.
rg -n 'Problemlösung im abgesicherten Modus|{`#troubleshooting-with-safe-mode`}' \
  i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.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/using-unraid-to/customize-your-experience/plugins.mdx`
at line 61, Re-add the explicit anchor {`#troubleshooting-with-safe-mode`} to the
German heading "Problemlösung im abgesicherten Modus" so existing deep links
keep working: restore the anchor directly after the heading text (e.g., "##
Problemlösung im abgesicherten Modus {`#troubleshooting-with-safe-mode`}") and
verify no other headings were accidentally changed; search the repo for the id
"troubleshooting-with-safe-mode" to confirm references still match.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx (2)

11-11: ⚠️ Potential issue | 🟡 Minor

Same invalid \[ admonition title syntax as in the French counterpart — fix applies here too.

The correct form removes the backslash and uses the localized Spanish label.

🐛 Proposed fix

-:::important\[Prerequisites]
+:::important[Prerrequisitos]

🤖 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/remove-data-disk-parity-preserve.mdx`
at line 11, Replace the invalid admonition token ":::important\[Prerequisites]"
with the correct localized admonition syntax by removing the backslash and using
the Spanish label (e.g., ":::important Prerrequisitos" or the project's chosen
Spanish term); locate the token in remove-data-disk-parity-preserve.mdx (search
for ":::important\[Prerequisites]") and update it to the proper form
":::important Prerrequisitos" so the admonition renders correctly.

---

11-11: ⚠️ Potential issue | 🟡 Minor

Admonition title "Prerequisites" is not translated into Spanish.

The label should use the Spanish equivalent, e.g. Prerrequisitos, consistent with the rest of this locale. The same backslash-escape concern flagged in the French file applies here — see that comment for context.

🌐 Suggested fix

-:::important\[Prerequisites]
+:::important[Prerrequisitos]

🤖 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/remove-data-disk-parity-preserve.mdx`
at line 11, Replace the admonition title token :::important\[Prerequisites] with
the Spanish label :::important[Prerrequisitos] (or match the exact escaping
style used by other Spanish docs — e.g., remove the backslash if they use plain
brackets). Update any duplicate occurrences in the same file so the admonition
title is consistently translated to "Prerrequisitos" and follows the same
bracket-escaping convention as other locale files.

i18n/de/docusaurus-plugin-content-docs/current/API/index.mdx (1)

71-75: Broken href with literal space and German icon name "Rakete"

🤖 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/index.mdx` around lines 71
- 75, The Card usage has a broken href containing a literal space and an
incorrect icon name; update the Card with title "Künftige Funktionen" to use a
slugified href (no spaces) such as "./kuenftige-funktionen" or
"./künftige-funktionen" instead of "./künftige Funktionen", and replace the icon
value "Rakete" with the expected icon identifier (e.g., "Rocket" or the
project's canonical icon key) so the link and icon render correctly.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx (1)

3-11: Spanish CSS property names still unresolved from the previous review.

The style object on this <div> still contains margen, maxAnchura, "columna", and "centro" — all invalid JSX/CSS identifiers. This was flagged in the prior review with a proposed fix; the fix has not been applied.

🤖 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 3 - 11, The style object on the <div> uses Spanish property
names—replace margen with margin, maxAnchura with maxWidth, columna with column
(for flexDirection), and centro with center (for alignItems); update the style
keys in the same JSX <div> (the style object shown in the diff) so they are
valid CSS-in-JS identifiers (e.g., margin, maxWidth, display, flexDirection:
"column", alignItems: "center") and keep the same values/types.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (2)

140-140: Cross-document links to #converting-to-a-new-file-system-type remain broken.

The anchor that cross-docs reference is still missing. ## 转换到新的文件系统类型 at line 187 was restored, but it lacks an explicit English anchor {#converting-to-a-new-file-system-type}. Docusaurus will auto-generate a URL-encoded Chinese slug, so all incoming English-slug links from securing-your-data.mdx, release notes (7.0.0.md, 7.2.0.md, 7.2.1.md), and their i18n counterparts will continue to 404.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
at line 140, The Chinese header "## 转换到新的文件系统类型" is missing the explicit English
anchor expected by cross-doc links; update that header by adding the explicit
anchor {`#converting-to-a-new-file-system-type`} immediately after the header text
so incoming English-slug links (from secur­ing-your-data.mdx and the 7.x release
notes) resolve correctly—look for the header string "## 转换到新的文件系统类型" and append
the anchor token "{`#converting-to-a-new-file-system-type`}".

---

163-163: Anchor removal on ## 更改文件系统类型, ### 使用未分配设备插件, and ### 检查文件系统 still unresolved.

These three headings still lack their explicit English anchors, breaking the intra-document links at lines 230, 93, and 451 respectively, and the auto-deduplication issue for the two ### 检查文件系统 headings (lines 433 and 483) remains.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
at line 163, Add explicit English anchor IDs to the problematic headings so
intra-document links resolve and duplicate anchors are unique: append a Markdown
heading ID to "## 更改文件系统类型" (e.g., {`#change-file-system-type`}), to "###
使用未分配设备插件" (e.g., {`#use-unassigned-devices-plugin`}), and to both "### 检查文件系统"
headings using distinct IDs (e.g., {`#check-filesystem`} and
{`#check-filesystem-2`}); update any internal links if needed to point to those
English IDs. Ensure you modify the headings themselves (the exact strings
"更改文件系统类型", "使用未分配设备插件", and the two "检查文件系统") so Docusaurus can use the
provided IDs.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (6)

144-148: ⚠️ Potential issue | 🔴 Critical

Missing ] in admonition title syntax.

:::tip[Planning für zukünftige Erweiterung. is malformed and should be closed as :::tip[... ].

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 144 - 148, The admonition opening token is malformed: the title for
the tip uses ":::tip[Planning für zukünftige Erweiterung." and is missing the
closing bracket; update the admonition start to include the closing bracket
(e.g., ":::tip[Planning für zukünftige Erweiterung]" ) so the admonition parser
recognizes the title; verify the corresponding closing ":::“ remains after the
block.

---

83-95: ⚠️ Potential issue | 🟠 Major

This full subsection is duplicated and should be removed or renamed.

The heading/content repeats nearby section material and creates redundant TOC entries.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 83 - 95, The subsection titled "Hinzufügen von Laufwerken zur
Erstellung eines Mehrgerätepools" is duplicated; remove the redundant copy or
rename it to a distinct heading to avoid duplicate TOC entries and content
repetition. Locate the block starting with the heading "Hinzufügen von
Laufwerken zur Erstellung eines Mehrgerätepools" (containing references like
%%BTRFS|btrfs%%, %%ZFS|zfs%%, and %%Cache-Pools|cache-pool%%) and either delete
the entire duplicate paragraph/list block or change its heading and adjust
linking so it no longer duplicates the nearby section.

---

104-106: ⚠️ Potential issue | 🟠 Major

H2 heading is accidental body text from a list item.

Line 104 uses explanatory bullet text as a section heading; this breaks hierarchy and anchor semantics.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 104 - 106, The line starting with "## **Verhinderung von
versehentlichem Verlust:**" is an accidental H2 taken from a list item; change
it to normal body text (remove the leading "## " and the bold markup so it reads
as a sentence), ensure it remains part of the explanatory list or paragraph
before "Um eine Festplatte zu einem %%BTRFS|btrfs%%-Pool hinzuzufügen:" so
heading hierarchy and anchors are preserved, and verify there are no leftover
heading anchors referring to that string.

---

315-319: ⚠️ Potential issue | 🟠 Major

Caution block is empty while its ordered content is detached later.

The warning sentence at Line 317 introduces an order list, but the list appears at Lines 389-391 instead of inside the caution block.

Also applies to: 387-391

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 315 - 319, The caution block starting with the :::caution marker is
left empty while the ordered list describing the directory-merge order is placed
later; move the ordered list into the body of the :::caution ... ::: block so
the warning sentence and its ordered list are contiguous, ensure the closing :::
comes after the list, and verify MDX syntax (triple-colon admonition and list
indentation) around the caution block and the ordered list currently found after
it so the list renders inside the caution admonition.

---

29-40: ⚠️ Potential issue | 🔴 Critical

Malformed info admonition plus orphaned closing delimiter.

The block around Line 29 has an extra standalone ::: at Line 39 after an already closed admonition, which can break MDX structure.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 29 - 40, The MDX admonition starting with ":::info[Keep Sie]" is
closed correctly but there's an extra orphaned closing delimiter ":::” after it;
remove the stray ":::” (the standalone closing delimiter) so the admonition
block only has a single matching closing delimiter, and verify the admonition
content around ":::info[Keep Sie]", the internal markdown lines (e.g., "%%cache
pools|cache-pool%%", "%%Mover|mover%%"), and the final ":::” only appear once to
restore valid MDX structure.

---

253-279: ⚠️ Potential issue | 🟠 Major

Two “Mindestfreier Speicherplatz” sections are conflicting and mixed with unrelated workflows.

The first section is disk-replacement prerequisites/steps, while the second is actual minimum-free-space guidance. Split topics cleanly and keep only one H2 with this title.

Also applies to: 283-286

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx`
around lines 253 - 279, The "## Mindestfreier Speicherplatz für einen
Cache-Pool" heading currently mixes disk-replacement prerequisites/steps and
minimum-free-space guidance; split these into two distinct sections: keep the H2
"## Mindestfreier Speicherplatz für einen Cache-Pool" solely for guidance about
free-space values (retain the :::important block about 10–20 GB and any
explanatory text about setting the minimum free space), and move the disk
replacement content (the :::note\[Prerequisites] block and the numbered
replacement workflow steps including stopping/starting the %%array|array%% and
assigning the new drive) into a new, clearly named section (e.g., "## Festplatte
ersetzen im Cache-Pool" or "## Ersatz einer Festplatte") that contains the
prerequisites and step-by-step instructions; also remove the
duplicated/redundant lines referenced (the duplicate content around 283–286) so
only one "Mindestfreier Speicherplatz" H2 remains.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx (2)

578-580: ⚠️ Potential issue | 🟡 Minor

Duplicate caution paragraph should be deduplicated (and unescape bold markup).

The same paragraph appears twice, and \*\*Docker-Safe New Perms \*\* should be normalized to proper Markdown emphasis.

🤖 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/advanced-tools/command-line-interface.mdx`
around lines 578 - 580, Remove the duplicated caution paragraph (keep a single
instance) that mentions using the **Neue Berechtigungen** tool in the **Tools**
menu and the %%WebGUI|web-gui%%; also unescape and normalize the bold markup for
the Docker helper by replacing "\*\*Docker-Safe New Perms \*\*" with proper
Markdown emphasis like **Docker-Safe New Perms** so the text reads cleanly and
only appears once.

---

28-30: ⚠️ Potential issue | 🔴 Critical

Fix malformed admonition syntax and duplicated untranslated PuTTY guidance.

Line 28 is missing ] in :::tip[...], and the English PuTTY sentence is duplicated (Line 30 and Line 40).

Suggested fix

-:::tip[When sollte ich das Terminal verwenden?
+:::tip[Wann sollte ich das Terminal verwenden?]

-If you're using Windows, you might prefer %%PuTTY|putty%% for %%SSH|ssh%% access instead of the built-in terminal. It's lightweight, free, and allows you to save sessions for easy access later.
+Wenn Sie Windows verwenden, bevorzugen Sie möglicherweise %%PuTTY|putty%% für den %%SSH|ssh%%-Zugriff statt des integrierten Terminals. Es ist leichtgewichtig, kostenlos und erlaubt das Speichern von Sitzungen für schnellen späteren Zugriff.

(And remove the duplicate sentence at Line 40.)

Also applies to: 40-40

🤖 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/advanced-tools/command-line-interface.mdx`
around lines 28 - 30, Fix the malformed admonition opener by closing the bracket
in the admonition header ":::tip[When sollte ich das Terminal verwenden?" (add
the missing ]), and remove the duplicated English PuTTY guidance sentence "If
you're using Windows, you might prefer %%PuTTY|putty%% for %%SSH|ssh%% access
instead of the built-in terminal. It's lightweight, free, and allows you to save
sessions for easy access later." so it appears only once (keep the intended
localized/translated content and delete the duplicate occurrence).

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx (3)

65-67: ⚠️ Potential issue | 🔴 Critical

Remove the invalid :::precaución opener and keep only :::caution.

This creates conflicting admonition delimiters in the same section.

Suggested fix

-:::precaución[Antes de reemplazar]
-
 :::caution[Antes de reemplazar]

🤖 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/changing-the-flash-device.mdx`
around lines 65 - 67, Remove the invalid Spanish admonition opener by deleting
the `:::precaución` token and leaving only the standard `:::caution` admonition
opener so there is a single, non-conflicting admonition delimiter; locate the
duplicated lines containing `:::precaución` and `:::caution` in the
changing-the-flash-device.mdx section and keep only `:::caution`, ensuring the
corresponding closing delimiter (if present) matches it.

---

152-158: ⚠️ Potential issue | 🟠 Major

Use valid React style keys/values in all three image wrappers.

margen, maxAnchura, columna, and centro are not valid JSX style keys/values, so those styles won’t apply as intended.

Suggested fix (apply to all 3 blocks)

 style={{
-  margen: "auto",
-  maxAnchura: "600px",
+  margin: "auto",
+  maxWidth: "600px",
   display: "flex",
-  flexDirection: "columna",
-  alignItems: "centro",
+  flexDirection: "column",
+  alignItems: "center",
 }}

Also applies to: 195-201, 220-226

🤖 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/changing-the-flash-device.mdx`
around lines 152 - 158, The three image wrapper JSX blocks in
changing-the-flash-device.mdx use invalid Spanish style keys (margen,
maxAnchura, columna, centro); update each wrapper's style prop to use valid
React/CSS-in-JS keys/values (e.g., replace margen with margin, maxAnchura with
maxWidth, columna with column or flexDirection:'column' depending on intent, and
centro with justifyContent:'center' and/or alignItems:'center'), ensuring values
are valid CSS strings or numbers; apply the same replacements to the other two
image wrapper blocks mentioned so all three use proper JSX style keys.

---

54-54: ⚠️ Potential issue | 🔴 Critical

:::nota is not a valid Docusaurus admonition type.

Use :::note here; otherwise this block may not render correctly.

Suggested fix

-  :::nota
+  :::note

🤖 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/changing-the-flash-device.mdx`
at line 54, Replace the incorrect Docusaurus admonition token ":::nota" with the
correct token ":::note" in the changing-the-flash-device.mdx file so the
admonition renders properly; search for the string ":::nota" (the faulty
admonition marker) and change it to ":::note" and verify the surrounding
admonition block begins and ends correctly.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx (1)

184-188: ⚠️ Potential issue | 🔴 Critical

Use valid Docusaurus admonition markers (::: + English type).

::提示 / ::注意 should be :::tip / :::note (or other supported type), with proper closing :::.

Suggested fix pattern

-    ::提示[最佳实践]
+    :::tip[最佳实践]
...
-    ::提示
+    :::tip
...
-    ::注意[数据丢失警告]
+    :::note[数据丢失警告]

Also applies to: 207-208, 240-241

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx`
around lines 184 - 188, Replace non-standard Chinese admonition markers like
"::提示[最佳实践]" and "::注意" with valid Docusaurus admonitions: use English type
names prefixed by three colons (e.g., ":::tip" or ":::note") at the start and
add a matching closing ":::". For each occurrence (e.g., the lines containing
"::提示[最佳实践]" and any "::注意"), wrap the list content between a starting ":::tip"
/ ":::note" and a closing ":::", preserving the inner bullet text and
translation; ensure the admonition type matches intent (use "tip" for
suggestions, "note" for notes).

i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)

152-158: ⚠️ Potential issue | 🟠 Major

Inline style objects use invalid JSX style keys/values in three places.

margen, maxAnchura, columna, and centro should be replaced with React/CSS-in-JS equivalents (margin, maxWidth, column, center).

Also applies to: 195-201, 220-226

🤖 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-connect/overview-and-setup.mdx`
around lines 152 - 158, The JSX inline style object uses Spanish keys/values
that are invalid in React; update the style prop by replacing margen → margin,
maxAnchura → maxWidth, flexDirection: "columna" → flexDirection: "column", and
alignItems: "centro" → alignItems: "center" (preserve the original values and
types), and apply the same fixes to the other occurrences mentioned (the other
style objects at the same pattern).

i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (2)

121-121: ⚠️ Potential issue | 🟠 Major

Unescape the note label so Docusaurus parses it correctly.

Line 121 uses :::note\[Reminder], which should be :::note[Reminder].

Proposed fix

-:::note\[Reminder]
+:::note[Reminder]

#!/bin/bash
# Verify escaped admonition labels in this file
rg -n ':::(info|note|tip|warning|important|caution)\\\[' i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx

🤖 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-connect/automated-flash-backup.mdx`
at line 121, The admonition label is incorrectly escaped as the token
":::note\\[Reminder]" so Docusaurus won't parse it; update the markdown at the
token ":::note\\[Reminder]" to the unescaped form ":::note[Reminder]" so the
admonition is recognized, ensuring any other occurrences of escaped admonition
labels (e.g., matching ":::info\\[", ":::tip\\[", ":::warning\\[", etc.) are
similarly unescaped.

---

56-63: ⚠️ Potential issue | 🔴 Critical

Use valid JSX style keys/values to prevent rendering/runtime issues.

Line 58+ uses invalid style keys/values for React (margen, maxAnchura, "columna", "centro").

Proposed fix

 <div
 style={{
- margen: "auto",
- maxAnchura: "600px",
+ margin: "auto",
+ maxWidth: "600px",
  display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
+ flexDirection: "column",
+ alignItems: "center",
 }}
 >

#!/bin/bash
# Verify invalid JSX style keys/values in this file
rg -n 'margen:|maxAnchura:|flexDirection:\s*"columna"|alignItems:\s*"centro"' i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx

🤖 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-connect/automated-flash-backup.mdx`
around lines 56 - 63, The JSX style object in the <div> uses Spanish/incorrect
keys and values (margen, maxAnchura, flexDirection: "columna", alignItems:
"centro"); update the style object used in that <div> (the inline style prop) to
use valid React/CSS keys and values: margin instead of margen, maxWidth instead
of maxAnchura, flexDirection: "column" (not "columna"), and alignItems: "center"
(not "centro"), keeping the existing values (e.g., "auto" and "600px") as
appropriate so the component renders correctly.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx (1)

4-13: Invalid JSX style keys remain in this block.

Line 6-10 uses localized keys/values (margen, maxAnchura, columna, centro) that React does not apply in style.

Proposed fix

 <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/system-administration/maintain-and-update/partials/backup-using-webgui.mdx`
around lines 4 - 13, The JSX style object on the div contains localized/invalid
keys (margen, maxAnchura, columna, centro) so React ignores them; update the
style object used on that div to use valid CSS-in-JS properties (e.g., use
margin, maxWidth, display, flexDirection: "column", alignItems: "center") so the
layout is applied correctly; ensure the JSX element (the div in the
backup-using-webgui.mdx fragment) uses those corrected keys and values and
remove any remaining localized variants.

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx (1)

14-37: Localized CSS keys are still invalid in both style blocks.

Line 16/17/19/20 and Line 30/31/33/34 use non-React style keys/values (margen, maxAnchura, columna, centro), so these styles will be ignored.

Proposed fix

 <div
 style={{
- margen: "auto",
- maxAnchura: "600px",
+ margin: "auto",
+ maxWidth: "600px",
  display: "flex",
- flexDirection: "columna",
- alignItems: "centro",
+ flexDirection: "column",
+ alignItems: "center",
 }}
 >

Apply the same replacement in both updated blocks.

🤖 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-manual-method.mdx`
around lines 14 - 37, The style props in the two JSX <div style={{ ... }}>
blocks use localized keys "margen", "maxAnchura", "columna", "centro" which are
invalid in React; update both blocks to use standard React/CSS keys: margin,
maxWidth, flexDirection: "column", and alignItems: "center" so the styles are
applied correctly (search for the <div style={{ ... }}> occurrences that contain
those localized keys and replace them in both places).

i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx (1)

59-75: Spanish icon names and space-containing href paths on Card components — previously flagged.

🤖 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 59
- 75, The Card components contain non-standard icon names and href values with
spaces; update the three Card usages (the Card titled "Usando la API de Unraid",
"Configuración OIDC", and "Características Futuras") to use valid icon
identifiers (use the icon keys expected by the Card component, e.g., "code",
"shield", "rocket" instead of localized words) and normalize the hrefs to
URL-safe paths (replace spaces with hyphens or use slugified names like
"./how-to-use-the-api", "./oidc-provider-configuration", "./future-features").
Ensure you only change the icon and href attributes on those Card elements so
they match the component's accepted icon keys and do not contain spaces.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)

101-104: Admonition marker :::重要 and malformed closing delimiter — previously flagged.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
around lines 101 - 104, Replace the nonstandard admonition marker ":::重要" and
the malformed closing delimiter with a valid Docusaurus admonition: use the
supported English key ":::important" (or ":::note" if preferred) and ensure the
closing delimiter is a bare ":::“ on its own line (remove the stray "\n" and any
extra characters). Update the block that currently contains ":::重要" and the
following closing ":::” so the opening is ":::important" and the closing is a
single line ":::", preserving the inner content.

i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx (1)

253-254: Orphaned ::: closing tag — previously flagged.

🤖 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/how-to-use-the-api.mdx`
around lines 253 - 254, There is an orphaned closing MDX admonition tag ":::".
Remove the stray ":::” (or if it was intended, add the matching opening ":::
<admonition-type>" block and content) in the how-to-use-the-api.mdx document so
the MDX admonition pairs are balanced; search for the standalone ":::” token and
either delete it or insert the corresponding opening admonition tag and content
to restore proper block structure.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx (1)

65-67: Previously flagged invalid admonition opener is still present.

Line 65 (:::注意 在你替换之前) should be removed so only the valid opener remains.

🔧 Proposed fix

-:::注意 在你替换之前
-
 :::note 在你替换之前

Quick verification:

#!/bin/bash
file="$(fd -p 'changing-the-flash-device.mdx' | head -n 1)"
rg -n ':::注意 在你替换之前|:::note 在你替换之前' "$file"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx`
around lines 65 - 67, Remove the duplicate/invalid Chinese admonition opener
string ":::注意 在你替换之前" so only the valid ":::note 在你替换之前" remains; locate the
duplicate in the changing-the-flash-device.mdx content (the line containing the
exact text ":::注意 在你替换之前") and delete that line, leaving a single correct
admonition opener.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

# First, check if the file exists and read its content
FILE="i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-btrfs.mdx"

echo "=== File contents with line numbers ==="
wc -l "$FILE"
cat -n "$FILE"

echo ""
echo "=== Running fence balance check ==="
python - <<'PY'
from pathlib import Path

f = Path("i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-btrfs.mdx")
stack = 0
lines_content = []
for ln, line in enumerate(f.read_text(encoding="utf-8").splitlines(), 1):
    s = line.lstrip()
    lines_content.append((ln, line, s))
    if s.startswith(":::"):
        if s.strip() == ":::":
            stack -= 1
            print(f"Line {ln}: closing ::: (stack now: {stack}) | Content: {repr(line)}")
            if stack < 0:
                print(f"  ERROR: unmatched closing :::")
                stack = 0
        else:
            stack += 1
            print(f"Line {ln}: opening {s.split()[0]} (stack now: {stack}) | Content: {repr(line)}")

print(f"\nFinal state: remaining open directives = {stack}")
if stack != 0:
    print(f"ERROR: Unbalanced fences detected!")
PY

Repository: unraid/docs

Length of output: 1237

---

Remove the extra closing ::: fence on line 10.

Line 8 already closes the :::note block opened on line 4. Line 10 creates an unmatched closing fence that breaks the directive balance.

Proposed fix

-  :::
-
-:::
+:::

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::
	:::
	:::
	:::

🤖 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/partials/data-recovery/repair-btrfs.mdx`
around lines 8 - 10, Remove the unmatched closing directive fence by deleting
the extra ":::". Specifically, keep the single closing "::: " that matches the
opening ":::note" block and remove the second closing "::: " (the extra fence)
so the ":::note" directive is properly balanced.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

cat -n i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-xfs.mdx | sed -n '10,25p'

Repository: unraid/docs

Length of output: 533

---

🏁 Script executed:

#!/bin/bash
python - <<'PY'
from pathlib import Path

f = Path("i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-xfs.mdx")
stack = 0
for ln, line in enumerate(f.read_text(encoding="utf-8").splitlines(), 1):
    s = line.lstrip()
    if s.startswith(":::"):
        if s.strip() == ":::":  # closing fence
            stack -= 1
            if stack < 0:
                print(f"{f}: Line {ln} unmatched closing :::")
                stack = 0
        else:  # opening fence, e.g. :::note
            stack += 1
print(f"{f}: remaining open directives = {stack}")
PY

Repository: unraid/docs

Length of output: 366

---

Remove the extra closing fence and fix English text in German locale file.

Line 19 contains an unmatched closing ::: that breaks MDX parsing. Additionally, line 16 contains English text in a German localization file—it should be translated to German.

Proposed fix

- Reparaturen erhalten den %%parity|parity%% Schutz und können viel Zeit in Anspruch nehmen.
- Both %%WebGUI|web-gui%% and command-line options are supported for %%XFS|xfs%% repair (commands shown below).
-  :::
-
-:::
+ Reparaturen erhalten den %%parity|parity%% Schutz und können viel Zeit in Anspruch nehmen.
+ [TRANSLATE TO GERMAN] Both %%WebGUI|web-gui%% and command-line options are supported for %%XFS|xfs%% repair (commands shown below).
+ :::

🤖 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/partials/data-recovery/repair-xfs.mdx`
around lines 17 - 19, Remove the unmatched closing fence ":::“ (the extra line
containing only ":::") so MDX parsing isn't broken, and replace the English
sentence currently in the German locale file (the English text on the paragraph
above the fences) with an appropriate German translation; ensure the remaining
":::“ fences form a proper matched container and the translated sentence
preserves original meaning/context.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Wrong content in "Erweiterte Grafik- und GPU-Sharing-Optionen" summary — content/label mismatch and duplicate section header.

The first <details> block at Line 100 is labeled "Erweiterte Grafik- und GPU-Sharing-Optionen" but its body (Lines 102–107) contains VM-clone, snapshot, user-template, inline-XML, and autostart items — none of which are GPU-related. The identical summary label reappears at Line 131 with the correct GPU/graphics content. This produces two collapsed sections with the same title, with swapped/incorrect content in the first one.

The content in lines 102–107 belongs to a "%%VM|vm%%-Manager-Grundfunktionen" or equivalent block, not a GPU-sharing block. Please verify the intended section structure and correct both the label of the first block and the placement of the second block.

🧰 Tools

🪛 LanguageTool

[grammar] ~102-~102: Ergänze ein Wort
Context: ...haring-Optionen - %%VM|vm%%-Klonen & Snapshots: ...

(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_NOUN)

---

[grammar] ~103-~103: Hier könnte ein Fehler sein.
Context: ...ts oder Backups. - Benutzer %%VM|vm%% Vorlagen: Speichern Sie Ihre benutzerdefinierte...

(QB_NEW_DE)

---

[grammar] ~103-~103: Ergänze ein Leerzeichen
Context: ...kups. - Benutzer %%VM|vm%% Vorlagen: Speichern Sie Ihre benutzerdefinierten %...

(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)

---

[grammar] ~105-~105: Ersetze das Satzzeichen
Context: ...arbeitungen. - Autostart deaktivieren: Wählen Sie aus, welche %%VMs|vm%% autom...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_COLONASTERISKASTERISK_COLON)

---

[grammar] ~106-~106: Ersetze das Satzzeichen
Context: ...ch mit Ihrem %%array|array%% starten. - Timer/Offset-Konfigurationsoptionen </detail...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_TIMERSLASHOFFSETDASHKONFIGURATIONSOPTIONEN_TIMERDASHSLASHOFFSETDASHKONFIGURATIONSOPTIONEN)

🤖 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/vm-setup.mdx`
around lines 99 - 108, Rename the first <details> summary that currently reads
"Erweiterte Grafik- und GPU-Sharing-Optionen" to a VM-manager label like
"%%VM|vm%%-Manager-Grundfunktionen" and ensure its body retains the VM-related
items (%%VM|vm%%-Klonen, [Snapshots], Benutzer %%VM|vm%% Vorlagen,
Inline-XML-Ansicht/Bearbeitung referencing %%WebGUI|web-gui%%, and Autostart
deaktivieren with %%array|array%%); then verify the later "Erweiterte Grafik-
und GPU-Sharing-Optionen" block remains only with GPU/graphics content so there
are no duplicate summaries or swapped content.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Wrong <details> content under "HDMI-Audio mit MSI-Interrupts beheben" section.

The <details> block at Lines 205–228 is nested under the HDMI-Audio/MSI section (Line 205) but its <summary> reads "Wie man den Remote-Desktop-Zugriff (RDP) aktiviert" and the body contains RDP steps (Lines 212–226), not HDMI/MSI interrupt instructions. The correct MSI content (checking lspci output, enabling MSI via registry) has been partially merged into the wrong block (Lines 217–222 present MSI steps intermixed with RDP steps).

This is a structural merge conflict artifact: the HDMI-Audio section is missing its proper guide body, and the RDP <details> block from the earlier section has been transplanted here.

🧰 Tools

🪛 LanguageTool

[style] ~214-~214: ‚Info‘ ist umgangssprachlich.
Context: ...nen, navigieren Sie dann zu System → Info und klicken Sie auf **Erweiterte Sys...

(MATHE)

---

[grammar] ~221-~221: Hier könnte ein Fehler sein.
Context: ...y) oder nutzen Sie das MSI Mode Utility, um die Windows-Registrierungseinstellungen zu ändern. - Starten Sie die %%VM|vm%% nach den Änder...

(QB_NEW_DE)

---

[grammar] ~224-~224: Korrigiere das Wort
Context: ...|vm%% nach den Änderungen neu. :::tip Offizielle Microsoft RDP-Clients sind fü...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPACE)

---

[grammar] ~225-~225: Entferne ein Leerzeichen
Context: ...en neu. :::tip Offizielle Microsoft RDP-Clients sind für Windows, Mac, Andro...

(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)

---

[grammar] ~225-~225: Korrigiere die Fehler
Context: ...ellen Sie sicher, dass Ihr %%VM|vm%% in einem Netzwerkbridge ist, das LAN-Zugriff erm...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~225-~225: Korrigiere die Fehler
Context: ...Sie sicher, dass Ihr %%VM|vm%% in einem Netzwerkbridge ist, das LAN-Zugriff ermöglicht. ::: ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~225-~225: Korrigiere die Wortform
Context: ... %%VM|vm%% in einem Netzwerkbridge ist, das LAN-Zugriff ermöglicht. ::: </detail...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_DETERMINER_FORM)

🤖 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 <details> block currently under the "HDMI-Audio mit
MSI-Interrupts beheben" section is incorrect: its <summary> ("Wie man den
Remote-Desktop-Zugriff (RDP) aktiviert") and RDP steps were accidentally merged
into the HDMI/MSI section and the true MSI instructions are missing or split.
Fix by removing or relocating the RDP <details> (summary text and steps about
enabling Remote Desktop) back to the proper RDP section and restore the
MSI-specific content inside the "HDMI-Audio mit MSI-Interrupts beheben"
section—ensure the <details> (or plain paragraphs) under that heading contain
the lspci command example (`lspci -v -s 01:00.0`), the MSI capability line
(`Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+`), and the guidance
to enable MSI via the Microsoft registry doc or MSI Mode Utility, keeping the
existing tip about bridge networking intact.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Double admonition closer will break MDX parsing.

The :::note[Additional Anmerkungen] block opened at line 87 has two ::: closers: one at line 94 (indented inside the last list item) and another bare ::: at line 96. MDX admonition blocks must have exactly one block-level ::: closer; the indented one at line 94 is inside a list item and Docusaurus will not parse it as a valid closer, leaving the block open until line 96. The result is unpredictable rendering or a build error.

Remove the duplicate and ensure exactly one closing ::: at the block level:

🛠️ Proposed fix

- Für Übertragungslaufwerke oder externe Geräte wird empfohlen, das **[Nicht zugewiesene Geräte](`#using-the-unassigned-devices-plugins`)** Plugin zu verwenden, welches zusätzliche Dateisysteme unterstützt.
-  :::
-
-:::
+- Für Übertragungslaufwerke oder externe Geräte wird empfohlen, das **[Nicht zugewiesene Geräte](`#verwendung-der-plugins-für-nicht-zugewiesene-geräte`)** Plugin zu verwenden, welches zusätzliche Dateisysteme unterstützt.
+
+:::

Additionally, the anchor target #using-the-unassigned-devices-plugins used in the link at line 93 will not match the German heading ### Verwendung der Plugins für nicht zugewiesene Geräte at line 410; the auto-generated anchor from that heading would differ. Verify or correct the anchor.

🧰 Tools

🪛 LanguageTool

[grammar] ~89-~89: Passe das Symbol an
Context: ...tional Anmerkungen] - Mixing different file system types in your Unraid system is perfectly acce...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~89-~89: Korrigiere die Fehler
Context: ...- Mixing different file system types in your Unraid system is perfectly acceptable; ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~89-~89: Korrigiere die Fehler
Context: ...ing different file system types in your Unraid system is perfectly acceptable; the Unr...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~89-~89: Korrigiere die Fehler
Context: ...ferent file system types in your Unraid system is perfectly acceptable; the Unraid %%p...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~89-~89: Korrigiere die Fehler
Context: ...file system types in your Unraid system is perfectly acceptable; the Unraid %%pari...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~89-~89: Korrigiere die Fehler
Context: ...e system types in your Unraid system is perfectly acceptable; the Unraid %%parity|parity%...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~89-~89: Passe das Symbol an
Context: ...ypes in your Unraid system is perfectly acceptable; the Unraid %%parity|parity%% system works i...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~89-~89: Hier könnte ein Fehler sein.
Context: ...tem is perfectly acceptable; the Unraid %%parity|parity%% system works independently of the file ...

(QB_NEW_DE)

---

[grammar] ~89-~89: Korrigiere die Fehler
Context: ...cceptable; the Unraid %%parity|parity%% system works independently of the file system ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~89-~89: Korrigiere die Fehler
Context: ...le; the Unraid %%parity|parity%% system works independently of the file system used. ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~89-~89: Korrigiere die Fehler
Context: ...e Unraid %%parity|parity%% system works independently of the file system used. - Immer innerh...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~89-~89: Korrigiere die Fehler
Context: ...ity|parity%% system works independently of the file system used. - Immer innerhalb...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~89-~89: Korrigiere die Fehler
Context: ...|parity%% system works independently of the file system used. - Immer innerhalb von...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~89-~89: Korrigiere die Fehler
Context: ...ity%% system works independently of the file system used. - Immer innerhalb von Unraid formatier...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~93-~93: Entferne ein Leerzeichen
Context: ...#using-the-unassigned-devices-plugins)** Plugin zu verwenden, welches zusätzliche...

(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_ORTHOGRAPHY_SPACE)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx`
around lines 87 - 96, Remove the extra indented admonition closer so the block
opened by :::note[Additional Anmerkungen] has exactly one top-level closing :::
(keep the final bare ::: and delete the indented ::: inside the list), and then
fix the link target by replacing '#using-the-unassigned-devices-plugins' with
the correct German anchor derived from the heading "### Verwendung der Plugins
für nicht zugewiesene Geräte" (or add an explicit HTML id on that heading) so
the link matches the actual generated anchor.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Invalid JSX style props — Spanish property names/values will be silently dropped by React.

The style object still contains localized (Spanish) identifiers that are not valid CSS property names or values. React will silently ignore them, so this <div> renders with no layout styling applied.

Written (Spanish)	Required (JS/CSS)
margen	margin
maxAnchura	maxWidth
"columna"	"column"
"centro"	"center"

The AI summary states these were converted from Spanish to English, but the conversion is not reflected in the code.

🐛 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.

Suggested change

	<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/customize-your-experience/multi-language-support.mdx`
around lines 41 - 49, The inline JSX style object on the <div> uses Spanish
property names/values and must be converted to valid JS/CSS identifiers so React
applies them: update the style object (the object passed to the <div>'s style
prop) to use margin instead of margen, maxWidth instead of maxAnchura,
flexDirection: "column" instead of "columna", and alignItems: "center" instead
of "centro" (keep maxWidth value "600px" and display: "flex" as-is).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
target_file="i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx"

echo "=== Checking file exists ==="
if [ -f "$target_file" ]; then
  echo "File found"
  wc -l "$target_file"
else
  echo "File not found"
  exit 1
fi

echo ""
echo "=== Searching for explicit anchors with 'system-preparation' ==="
rg -n '{`#system-preparation`}' "$target_file"

echo ""
echo "=== Searching for links to '#system-preparation' ==="
rg -n '#system-preparation' "$target_file"

echo ""
echo "=== Content around line 152 (heading) ==="
sed -n '150,155p' "$target_file" | cat -n

echo ""
echo "=== Content around line 209 (link) ==="
sed -n '207,212p' "$target_file" | cat -n

echo ""
echo "=== All headings (##) in the file ==="
rg -n '^##' "$target_file"

Repository: unraid/docs

Length of output: 1951

---

Fix broken in-page link to system preparation.

Line 209 links to #system-preparation, but the heading at Line 152 (## Préparation du système) has no explicit anchor. Docusaurus will auto-generate an anchor from the French heading text, which won't match the English slug in the link, causing the link to fail.

Proposed fix

-## Préparation du système
+## Préparation du système {`#system-preparation`}

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	## Préparation du système
	## Préparation du système {`#system-preparation`}

🤖 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/overview-and-system-prep.mdx`
around lines 152 - 153, The in-page link to “#system-preparation” fails because
the French heading "## Préparation du système" generates a different auto-slug;
update the heading to include an explicit anchor that matches the link (for
example add a heading ID such as "Préparation du système {`#system-preparation`}"
or insert an HTML anchor like "<a id=\"system-preparation\"></a>" immediately
before the "## Préparation du système" heading) so the existing link to
"#system-preparation" resolves correctly.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Search for any references to the removed anchor
rg -rn 'troubleshooting-with-safe-mode' --type=md --type=mdx

Repository: unraid/docs

Length of output: 82

---

🏁 Script executed:

#!/bin/bash
# Also search for direct links to plugins.mdx with this anchor
rg -rn 'plugins\.mdx.*troubleshooting-with-safe-mode|plugins.*#troubleshooting-with-safe-mode' --type=md --type=mdx

Repository: unraid/docs

Length of output: 82

---

🏁 Script executed:

#!/bin/bash
# Search for any markdown links that might reference this anchor (e.g., in French docs)
rg -rn '#troubleshooting-with-safe-mode' --type=md --type=mdx

Repository: unraid/docs

Length of output: 82

---

🏁 Script executed:

#!/bin/bash
# Search for references to the removed anchor in markdown and mdx files
rg 'troubleshooting-with-safe-mode' -g '*.md' -g '*.mdx'

Repository: unraid/docs

Length of output: 2930

---

🏁 Script executed:

#!/bin/bash
# Search for any files that link to plugins.mdx with this anchor
rg 'plugins.*#troubleshooting-with-safe-mode|plugins\.mdx#troubleshooting-with-safe-mode' -g '*.md' -g '*.mdx'

Repository: unraid/docs

Length of output: 2930

---

🏁 Script executed:

#!/bin/bash
# Broader search for the anchor without extension restrictions
rg 'troubleshooting-with-safe-mode'

Repository: unraid/docs

Length of output: 2930

---

Critical: 10+ inbound links to this anchor will break across the codebase.

Multiple pages in English and all locales (French, German, Spanish, Chinese) link to plugins.mdx#troubleshooting-with-safe-mode:

• docs/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• docs/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx

Either preserve the anchor or update all these links.

🤖 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, The heading "## Dépannage en mode sans échec" changed or removed the
anchor used by multiple links (plugins.mdx#troubleshooting-with-safe-mode);
either restore the original anchor on that heading (add an explicit HTML anchor
or the English slug as an ID) so existing links continue to work, or update
every referring document that links to
plugins.mdx#troubleshooting-with-safe-mode (the listed docs in English and all
locales) to point to the new anchor/slug; locate the heading in plugins.mdx and
adjust it (or add <a id="troubleshooting-with-safe-mode"></a> above it), or
change the target in the referring files to the new anchor name.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Stray ::: closing marker will break rendering.

The :::info block at lines 94–97 is already properly closed at line 97. The newly added ::: at line 99 has no matching opening admonition, so it will either render as a visible ::: literal or cause an MDX parse error.

🐛 Proposed fix — remove the orphaned closing marker

 :::info

 您可以在**主页面**选项卡的同一**阵列操作**部分中使用相应按钮停止阵列、关闭或重启。
 :::
-
-:::

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::
	:::info
	您可以在**主页面**选项卡的同一**阵列操作**部分中使用相应按钮停止阵列、关闭或重启。
	:::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx`
around lines 98 - 99, Remove the stray closing admonition marker ":::" that
follows the existing ":::info" block; locate the orphaned ":::"
directly after the closed ":::info" block and delete it so there is only the
single matching ":::info" opening/closing pair.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

The admonition syntax errors from the prior review are still present in these changed lines.

Both defects remain:

1. :::提示 uses a non-English keyword — Docusaurus only recognises tip, note, info, warning, caution.
2. The closing ::: is on the same line as the content body — it must be on its own line.

Although the previous review marked this as addressed, lines 362–363 are still annotated as changed (~) in this diff yet still carry the broken syntax.

🐛 Proposed fix

-  :::提示
-  如果您不使用 GPLPV 驱动程序，可以跳过接下来的几个步骤，并从进入 %%KVM|kvm%% 模式部分继续。  :::
+  :::tip
+  如果您不使用 GPLPV 驱动程序，可以跳过接下来的几个步骤，并从进入 %%KVM|kvm%% 模式部分继续。
+  :::

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::提示
	如果您不使用 GPLPV 驱动程序，可以跳过接下来的几个步骤，并从进入 %%KVM|kvm%% 模式部分继续。 :::
	:::tip
	如果您不使用 GPLPV 驱动程序，可以跳过接下来的几个步骤，并从进入 %%KVM|kvm%% 模式部分继续。
	:::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx`
around lines 362 - 363, Replace the invalid admonition block that currently
starts with ":::提示" and closes with "::: " on the same line as content: change
the opening token to a supported English keyword (e.g., ":::tip" or ":::note")
and move the closing "::: " onto its own line so the admonition is properly
delimited; locate the block by searching for the literal ":::提示" and the inline
":::", then update the opening token and ensure the closing delimiter is on a
separate line after the content.

[coderabbitai]

Actionable comments posted: 17

Note

Due to the large number of review comments, Critical severity comments were prioritized as inline comments.

🧹 Nitpick comments (10)

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md (1)

29-29: 建议将 API 链接指向 4.29.2 的具体变更条目。

当前链接跳到通用 releases 列表，后续会变得不够精确；建议改成具体 tag/release URL，便于长期可追溯。

✏️ 可选改法

-- dynamix.unraid.net 4.29.2 - [查看更改](https://github.com/unraid/api/releases)
+- dynamix.unraid.net 4.29.2 - [查看更改](https://github.com/unraid/api/releases/tag/v4.29.2)

🤖 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/release-notes/7.2.4.md`
at line 29, 在这行 "dynamix.unraid.net 4.29.2 -
[查看更改](https://github.com/unraid/api/releases)" 中把当前指向通用 releases 列表的链接改为该版本的具体
release/tag 页面（例如 将链接改为
https://github.com/unraid/api/releases/tag/4.29.2），以便长期可追溯；具体操作是替换 markdown 中的链接
URL 部分，保留显示文本 “[查看更改]” 和版本描述 "dynamix.unraid.net 4.29.2" 不变。

i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)

143-152: Style reformat is safe; consider deduplicating repeated container styles.
Rendering should remain unchanged. For maintainability, extract this repeated style into a shared class/component used here and in the other image blocks.

🤖 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 143 - 152, The inline styling on the div wrapping the image (the
container using margin: "auto", maxWidth: "600px", display: "flex",
flexDirection: "column", alignItems: "center") should be extracted into a shared
style to avoid duplication; create a reusable CSS class (e.g., .centeredImage)
or a small React component (e.g., CenteredImage) that applies those styles,
replace this inline-styled div around the "Deep Linking" image with that
class/component, and update the other image blocks to use the same
class/component so all instances reuse the single definition for
maintainability.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md (1)

9-9: LanguageTool flag is a false positive; minor singular/plural nitpick.

The abbreviated imperative form "Für Schritt-für-Schritt-Anleitungen siehe …" is standard German documentation style and grammatically correct — the QB_NEW_DE hint can be ignored.

One small nitpick: the previous phrasing used the singular "Anleitung", which more precisely matches the single linked page. The new plural "Anleitungen" is not wrong, but if consistency with other release-note files (which may still use the singular) matters, it's worth aligning.

✏️ Optional: restore singular for precision

-Für Schritt-für-Schritt-Anleitungen siehe [Unraid aktualisieren](../../unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx).
+Für eine Schritt-für-Schritt-Anleitung siehe [Unraid aktualisieren](../../unraid-os/system-administration/maintain-and-update/upgrading-unraid.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/release-notes/7.2.2.md`
at line 9, The LanguageTool flag QB_NEW_DE is a false positive—keep the existing
imperative phrase "Für Schritt-für-Schritt-Anleitungen siehe [Unraid
aktualisieren](../../unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx)."
If you prefer precision/consistency with other release notes, change the linked
sentence to use the singular "Anleitung" (i.e., "Für
Schritt-für-Schritt-Anleitung siehe [Unraid aktualisieren]…") by editing that
exact sentence in the file so the phrasing matches other release-note files.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx (1)

31-32: Stray line break in image alt text.

The alt text wraps across two lines, which renders as an extra space mid-phrase: 检查按钮可让您执行校验和读取 检查. Consider keeping it on one line to avoid the redundant trailing fragment.

✏️ Suggested fix

-![检查按钮可让您执行校验和读取
-检查](/img/Check_button.PNG)
+![检查按钮可让您执行校验和读取检查](/img/Check_button.PNG)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx`
around lines 31 - 32, Merge the broken alt text into a single line by replacing
the multiline alt text "检查按钮可让您执行校验和读取\n检查" with a single continuous string
(e.g., "检查按钮可让您执行校验和读取检查" or a corrected phrase without the duplicated fragment)
in the image markdown line that begins with ![检查按钮可让您执行校验和读取; ensure the alt
text does not contain a newline so it renders as one coherent phrase.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx (1)

81-81: Rename this repeated heading to avoid duplicate navigation labels.

Line 63 already uses ## 备份您的闪存设备; repeating the same title on Line 81 creates confusing TOC entries/slug suffixes.

Suggested rename

-### 备份您的闪存设备
+### 备份方法

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx`
at line 81, The third-level heading "### 备份您的闪存设备" duplicates the earlier
second-level heading "## 备份您的闪存设备" and causes duplicate TOC labels; change the
repeated heading text to a unique label (e.g., "### 备份闪存设备 — 详细步骤" or "###
恢复与备份闪存设备") so the two headings are distinct, update only the heading line in
the file where "### 备份您的闪存设备" appears, and ensure the new text remains concise
and consistent with surrounding content.

i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md (1)

43-43: Consider keeping a stable bug-fixes anchor for backward compatibility.

Line 43 drops the explicit anchor. If any internal/external links still use #bug-fixes-and-improvements, they may no longer resolve as expected.

Suggested fix

-### Corrections de bugs et améliorations
+### Corrections de bugs et améliorations {`#bug-fixes-and-improvements`}

🤖 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/6.12.6.md`
at line 43, Add a stable anchor so old links to `#bug-fixes-and-improvements`
continue to work: update the section that currently reads "### Corrections de
bugs et améliorations" to include an explicit anchor named
bug-fixes-and-improvements (e.g., an HTML anchor tag or a Markdown/MDX heading
ID) immediately before or on that heading so both existing links and the visible
heading remain unchanged.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md (1)

43-43: Keep an explicit bug-fixes anchor to prevent link drift.

Line 43 removes (or omits) an explicit fragment for this section. Keeping #bug-fixes-and-improvements helps preserve existing references across versions/locales.

Suggested fix

-### 漏洞修复和改进
+### 漏洞修复和改进 {`#bug-fixes-and-improvements`}

🤖 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/release-notes/6.12.6.md`
at line 43, Restore an explicit anchor for the bug-fixes section so existing
cross-version/locale links don't break: update the "### 漏洞修复和改进" heading to
include the fragment identifier "bug-fixes-and-improvements" (e.g. add an HTML
anchor or a Markdown header ID) so the section becomes addressable via
"#bug-fixes-and-improvements"; target the heading text "### 漏洞修复和改进" and add the
anchor immediately above or inline with that header.

i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (1)

85-90: Clarify the exact USB Flash Creator restore path.

Consider explicitly adding “Use custom” in the restore step so users choose the correct recovery flow for the downloaded ZIP.

Based on learnings: Unraid flash backup ZIP files are compatible with the USB Flash Creator’s “Use custom” option for restore-to-new-device workflows.

🤖 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-connect/automated-flash-backup.mdx`
around lines 85 - 90, Update step 6 (the line that begins "Usa el [Creador de
Flash USB de Unraid](https://unraid.net/download)") to explicitly instruct users
to pick the USB Flash Creator's "Usar personalizado" (Use custom) option when
restoring the downloaded ZIP to a new flash device; keep the link to the Unraid
USB Flash Creator and clarify that the flash backup ZIP is compatible with the
"Usar personalizado"/"Use custom" restore flow so users choose the correct
recovery path.

i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx (1)

156-194: Consolidate duplicated “Partages utilisateurs pour la virtualisation” subsections.

The same subsection title appears twice with overlapping scope. Merge them or rename one to avoid duplicated navigation entries and split guidance.

🤖 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/overview-and-system-prep.mdx`
around lines 156 - 194, The document contains a duplicated subsection header
"### Partages utilisateurs pour la virtualisation" with overlapping content;
merge the two blocks by keeping a single "### Partages utilisateurs pour la
virtualisation" section that contains the descriptive sentence, the two bullet
entries for `isos` and `domains`, and the backup recommendation note (currently
repeated), then remove the redundant header and paragraph block; locate the
duplicates by searching for the exact header string and the bullet list entries
`isos` and `domains` and consolidate them into one cohesive subsection.

i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (1)

41-57: Deduplicate repeated “Entendiendo los Modos de Autorización” content.

The heading and bullets are repeated back-to-back with the same meaning. Keep a single canonical version to reduce noise.

🤖 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/oidc-provider-setup.mdx`
around lines 41 - 57, Remove the duplicated section titled "Entendiendo los
Modos de Autorización": keep a single canonical heading and one copy of the
bullet list and "Cuándo usar el Modo Simple" content, deleting the repeated
block that appears immediately after the first heading so the document contains
only one heading "Entendiendo los Modos de Autorización" followed by the
consolidated bullets and examples.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 932f1fd and 1a827b2.

📒 Files selected for processing (294)

• i18n/de/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-zfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-array-to-pool.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-command-line.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-device-limit.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/cli.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx
• i18n/es/docusaurus-plugin-content-docs/current/contribute/style-guide.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Untranslated English paragraph and escaped bracket in admonition syntax.

Line 33 is a full English paragraph inserted into a German document. Additionally, line 35 uses :::info\[Example] — the backslash escapes the [, so this renders as literal text rather than a titled admonition. It should be :::info[Example]. The body of the admonition at line 37 is also in English.

🛠️ Proposed fix

-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.
+Unraid unterstützt %%ZFS|zfs%% für jeden Speicherpool. Sie können einen neuen %%ZFS|zfs%%-Pool erstellen, einen von einem anderen System importieren oder Unraids einzigartiges Hybrid-%%ZFS|zfs%%-Setup verwenden: Fügen Sie eine %%ZFS|zfs%%-formatierte Festplatte direkt zum Unraid %%array|array%% (nicht einem Pool) hinzu und kombinieren Sie %%ZFS|zfs%%-Funktionen mit Unraids %%parity|parity%%-Schutz.

-:::info\[Example]
+:::info[Beispiel]

-You can use %%ZFS|zfs%% %%snapshots|snapshot%% and replication on a single disk as a backup target, or replicate a fast SSD %%ZFS|zfs%% pool to a %%ZFS|zfs%% disk in the %%array|array%% protected by Unraid %%parity|parity%% - getting the best of both worlds.
+Sie können %%ZFS|zfs%% %%Snapshots|snapshot%% und Replikation auf einer einzelnen Festplatte als Backup-Ziel verwenden oder einen schnellen SSD-%%ZFS|zfs%%-Pool auf eine %%ZFS|zfs%%-Festplatte im durch Unraid %%parity|parity%% geschützten %%array|array%% replizieren.

🧰 Tools

🪛 LanguageTool

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...n Echtzeit Unraid supports %%ZFS|zfs%% for any storage pool. You can create a new ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...htzeit Unraid supports %%ZFS|zfs%% for any storage pool. You can create a new %%ZF...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...it Unraid supports %%ZFS|zfs%% for any storage pool. You can create a new %%ZFS|zfs%% pool,...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Wähle ein passenderes Wort
Context: ...e pool. You can create a new %%ZFS|zfs%% pool, import one from another system, or use...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_NOUN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...n create a new %%ZFS|zfs%% pool, import one from another system, or use Unraid’s un...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...eate a new %%ZFS|zfs%% pool, import one from another system, or use Unraid’s unique ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...a new %%ZFS|zfs%% pool, import one from another system, or use Unraid’s unique hybrid %...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...ZFS|zfs%% pool, import one from another system, or use Unraid’s unique hybrid %%ZFS|zfs...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...% pool, import one from another system, or use Unraid’s unique hybrid %%ZFS|zfs%% ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...ool, import one from another system, or use Unraid’s unique hybrid %%ZFS|zfs%% setu...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ... import one from another system, or use Unraid’s unique hybrid %%ZFS|zfs%% setup: add a ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...ne from another system, or use Unraid’s unique hybrid %%ZFS|zfs%% setup: add a %%ZFS|z...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ... another system, or use Unraid’s unique hybrid %%ZFS|zfs%% setup: add a %%ZFS|zfs%%-fo...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Hier könnte ein Fehler sein.
Context: ...r system, or use Unraid’s unique hybrid %%ZFS|zfs%% setup: add a %%ZFS|zfs%%-formatted disk...

(QB_NEW_DE)

---

[grammar] ~33-~33: Hier könnte ein Fehler sein.
Context: ... use Unraid’s unique hybrid %%ZFS|zfs%% setup: add a %%ZFS|zfs%%-formatted disk direct...

(QB_NEW_DE)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...raid’s unique hybrid %%ZFS|zfs%% setup: add a %%ZFS|zfs%%-formatted disk directly t...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...’s unique hybrid %%ZFS|zfs%% setup: add a %%ZFS|zfs%%-formatted disk directly to ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...id %%ZFS|zfs%% setup: add a %%ZFS|zfs%%-formatted disk directly to the Unraid %%array|arr...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...fs%% setup: add a %%ZFS|zfs%%-formatted disk directly to the Unraid %%array|array%% ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...setup: add a %%ZFS|zfs%%-formatted disk directly to the Unraid %%array|array%% (not a po...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...d a %%ZFS|zfs%%-formatted disk directly to the Unraid %%array|array%% (not a pool) and...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...directly to the Unraid %%array|array%% (not a pool) and combine %%ZFS|zfs%% feature...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...ctly to the Unraid %%array|array%% (not a pool) and combine %%ZFS|zfs%% features ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Korrigiere die Fehler
Context: ...ly to the Unraid %%array|array%% (not a pool) and combine %%ZFS|zfs%% features with ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~33-~33: Passe das Symbol an
Context: ...the Unraid %%array|array%% (not a pool) and combine %%ZFS|zfs%% features with Unrai...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~33-~33: Passe das Symbol an
Context: ...Unraid %%array|array%% (not a pool) and combine %%ZFS|zfs%% features with Unraid’s %%pa...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~33-~33: Hier könnte ein Fehler sein.
Context: ...%array|array%% (not a pool) and combine %%ZFS|zfs%% features with Unraid’s %%parity|parity%...

(QB_NEW_DE)

---

[grammar] ~33-~33: Passe das Symbol an
Context: ...%% (not a pool) and combine %%ZFS|zfs%% features with Unraid’s %%parity|parity%% protect...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~33-~33: Passe das Symbol an
Context: ... pool) and combine %%ZFS|zfs%% features with Unraid’s %%parity|parity%% protection. ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~33-~33: Passe das Symbol an
Context: ...) and combine %%ZFS|zfs%% features with Unraid’s %%parity|parity%% protection. :::info...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~33-~33: Hier könnte ein Fehler sein.
Context: ...bine %%ZFS|zfs%% features with Unraid’s %%parity|parity%% protection. :::info[Example] You can...

(QB_NEW_DE)

---

[grammar] ~33-~33: Wähle ein passenderes Wort
Context: ...eatures with Unraid’s %%parity|parity%% protection. :::info[Example] You can use %%ZFS|...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_NOUN)

---

[grammar] ~35-~35: Ergänze ein Leerzeichen
Context: ...s %%parity|parity%% protection. :::info[Example] You can use %%ZFS|zfs%% %%sna...

(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_ORTHOGRAPHY_SPACE)

---

[grammar] ~37-~37: Passe das Symbol an
Context: ...tion on a single disk as a backup target, or replicate a fast SSD %%ZFS|zfs%% poo...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~37-~37: Passe das Symbol an
Context: ...on on a single disk as a backup target, or replicate a fast SSD %%ZFS|zfs%% pool t...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~37-~37: Ersetze das Satzzeichen
Context: ...% protected by Unraid %%parity|parity%% - getting the best of both worlds. ::: ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_DASH_–)

🤖 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 - 39, Replace the English paragraph about ZFS (the full sentence
starting "Unraid supports %%ZFS|zfs%% ...") with a German translation and also
translate the admonition body (the paragraph starting "You can use %%ZFS|zfs%%
%%snapshots|snapshot%% ...") into German; additionally correct the admonition
opening from :::info\[Example] to :::info[Example] so the title renders (look
for the exact string :::info\[Example] and the English ZFS paragraphs in the
same block).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Untranslated English content in "ZFS-Disk ins Array integrieren" section.

Line 191 is an English paragraph and line 193 has :::info[What das ermöglicht] with a mixed-language title. Line 199 and line 203 (To add a...) also contain English text in the middle of a German document.

🧰 Tools

🪛 LanguageTool

[grammar] ~191-~191: Passe das Symbol an
Context: ...u can add a standalone %%ZFS|zfs%% disk to your Unraid %%array|array%% (not a %%ZF...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~191-~191: Ersetze das Satzzeichen
Context: ...raid %%array|array%% (not a %%ZFS|zfs%% pool) to combine %%ZFS|zfs%% features with Un...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_CLOSE_PARENTHESIS_CLOSE_PARENTHESISCOMMA)

---

[grammar] ~191-~191: Entferne ein Satzzeichen
Context: ...l) to combine %%ZFS|zfs%% features with Unraid's %%parity|parity%% protection. :::info[...

(QB_NEW_DE_OTHER_ERROR_IDS_UNNECESSARY_PUNCTUATION_UNRAIDAPOSTROPHES)

---

[grammar] ~193-~193: Korrigiere das Wort
Context: ... %%parity|parity%% protection. :::info[What das ermöglicht] - Parity-Schutz: D...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPELLING)

---

[grammar] ~197-~197: Passe das Symbol an
Context: ...en gesichert sind. - Datenintegrität: %%ZFS|zfs%% bietet Integritätsprüfungen...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~197-~197: Korrigiere das Wort
Context: ...et Integritätsprüfungen auf Blockebene (Prüfsummen). Während eine einzelne Festplatte nich...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_SPELLING)

---

[grammar] ~199-~199: Hier könnte ein Fehler sein.
Context: ...em Backup wiederherstellen können. - %%ZFS|zfs%% features: You can utilize %%ZFS|zfs%% %%snapsh...

(QB_NEW_DE)

---

[grammar] ~199-~199: Passe das Symbol an
Context: ...len können. - %%ZFS|zfs%% features: You can utilize %%ZFS|zfs%% %%snapshots|...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~199-~199: Hier könnte ein Fehler sein.
Context: ...al for backup targets, specific datasets, or scenarios where you want %%ZFS|zfs%%...

(QB_NEW_DE)

---

[grammar] ~199-~199: Korrigiere die Fehler
Context: ... for backup targets, specific datasets, or scenarios where you want %%ZFS|zfs%% fe...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~199-~199: Korrigiere die Fehler
Context: ...r backup targets, specific datasets, or scenarios where you want %%ZFS|zfs%% features alo...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~199-~199: Korrigiere die Fehler
Context: ...argets, specific datasets, or scenarios where you want %%ZFS|zfs%% features alongside...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~199-~199: Korrigiere die Fehler
Context: ..., specific datasets, or scenarios where you want %%ZFS|zfs%% features alongside tra...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~199-~199: Korrigiere die Fehler
Context: ...ecific datasets, or scenarios where you want %%ZFS|zfs%% features alongside traditio...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~199-~199: Hier könnte ein Fehler sein.
Context: ...c datasets, or scenarios where you want %%ZFS|zfs%% features alongside traditional Unraid s...

(QB_NEW_DE)

---

[grammar] ~199-~199: Korrigiere die Fehler
Context: ...or scenarios where you want %%ZFS|zfs%% features alongside traditional Unraid storage. ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~199-~199: Korrigiere die Fehler
Context: ...ios where you want %%ZFS|zfs%% features alongside traditional Unraid storage. ::: To add a %%ZFS|zf...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~199-~199: Korrigiere die Fehler
Context: ...FS|zfs%% features alongside traditional Unraid storage. ::: To add a %%ZFS|zfs%% dis...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

---

[grammar] ~199-~199: Korrigiere die Fehler
Context: ...% features alongside traditional Unraid storage. ::: To add a %%ZFS|zfs%% disk to the...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_MULTITOKEN)

🤖 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 191 - 203, Replace the stray English sentences in the "ZFS-Disk ins
Array integrieren" section by translating them into German and fix the
mixed-language info title: change the info block header from ":::info[What das
ermöglicht]" to ":::info[Was das ermöglicht]" and translate the English
paragraph that starts with "You can add a standalone %%ZFS|zfs%% disk..." and
the line "To add a %%ZFS|zfs%% disk to the %%array|array%%:" into German (e.g.,
"Sie können eine eigenständige %%ZFS|zfs%%-Festplatte zu Ihrem
Unraid-%%array|array%% hinzufügen..." and "Um eine %%ZFS|zfs%%-Festplatte zum
%%array|array%% hinzuzufügen:"). Keep all token markers like %%ZFS|zfs%%,
%%array|array%%, %%parity|parity%%, and %%parity drives|parity-drives%%
unchanged and preserve the rest of the content and formatting.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Remove placeholder text accidentally left in the document.

Line 157 contains a German draft note (- vielleicht hatten wir keinen Platz mehr — "maybe we ran out of space") embedded as a real bullet point in the Docker manager share list. This must be removed before publishing.

🐛 Proposed fix

 - 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

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- 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
	- 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.

🧰 Tools

🪛 LanguageTool

[grammar] ~155-~155: Passe die Groß- und Kleinschreibung an
Context: ...ese vorhandenen Freigaben verwendet: - system - wird verwendet, um Docker-Image-Schicht...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_LOWERCASE)

---

[grammar] ~156-~156: Ersetze das Satzzeichen
Context: ...das in system/docker gespeichert ist. - appdata - wird von Docker-Anwendungen verwendet, ...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_DASH_–)

---

[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`
around lines 155 - 158, Remove the accidental draft bullet "- vielleicht hatten
wir keinen Platz mehr" from the Docker manager share list in the release notes
so the list only contains the legitimate items ("system" and "appdata"); edit
the file
i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
and delete that placeholder line, keeping surrounding list formatting and
spacing intact.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

## powerdown section body describes Midnight Commander file transfer, not system shutdown.

Line 444 has heading ## powerdown but line 446 begins content about transferring files from network shares using Midnight Commander. The file transfer section content was placed under the wrong heading during the restructure.

🧰 Tools

🪛 LanguageTool

[grammar] ~446-~446: Ergänze ein Satzzeichen
Context: ...rkspeicherfreigaben (Windows- oder Linux SMB/CIFS-Freigaben) auf Ihren Unraid-Ser...

(QB_NEW_DE_OTHER_ERROR_IDS_MISSING_PUNCTUATION_LINUXDASHSMB)

🤖 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/advanced-tools/command-line-interface.mdx`
around lines 444 - 446, The paragraph under the incorrect heading "## powerdown"
describes Midnight Commander file transfers; locate the "## powerdown" heading
and the following paragraph starting with "Diese Methoden helfen Ihnen..." and
either rename the heading to something appropriate (e.g., "## Midnight
Commander" or "## File transfers from network shares") or move that paragraph
into the correct file-transfer section, and leave "## powerdown" to contain
content about system shutdown/poweroff (or add the correct shutdown content) so
headings and body text match; update any nearby anchors/toc entries if
necessary.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Orphaned ::: will break MDX rendering.

The :::note block is already closed by the indented ::: on line 8. The additional ::: introduced on line 10 is an unclosed/orphaned admonition directive — Docusaurus will fail to render this partial correctly.

🐛 Proposed fix

   :::

-:::

🤖 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/partials/data-recovery/repair-btrfs.mdx`
around lines 9 - 10, Remove the orphaned admonition delimiter by deleting the
extra standalone ":::” that follows the already-closed ":::note" block so the
MDX partial contains only the opening ":::note" and its single matching closing
":::” (ensure the ":::note" block and its intended content remain intact and
properly indented).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Four-colon ::::tip prefix is invalid Docusaurus admonition syntax.

Line 48 uses ::::tip[...] (4 colons). Docusaurus requires exactly three colons (:::) for admonition fences. The extra colon means the block will not be parsed as an admonition and will render as raw text.

🐛 Proposed fix

-::::tip[Rules norma general para el reemplazo]
+:::tip[Rules norma general para el reemplazo]

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	::::tip[Rules norma general para el reemplazo]
	:::tip[Rules norma general para el reemplazo]

🧰 Tools

🪛 LanguageTool

[grammar] ~48-~48: Cambia la palabra o signo.
Context: ...y a las limitaciones físicas | ::::tip[Rules norma general para el reemplazo] - Com...

(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx`
at line 48, Replace the invalid four-colon admonition fence "::::tip[...]" with
the correct three-colon Docusaurus admonition syntax ":::tip[...]" (and ensure
the matching closing fence uses three colons too if present); specifically
locate the token "::::tip[Rules norma general para el reemplazo]" and change it
to ":::tip[Rules norma general para el reemplazo]" so the block is parsed as an
admonition.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Same translated-CSS bug in all three image wrappers — all layouts will break.

Identical to the issue in capture-diagnostics-and-logs.mdx: margen, maxAnchura, "columna", and "centro" are not valid CSS property names or keyword values. All three <div> wrappers for the step images (lines 7–17, 23–33, 39–49) are affected.

🐛 Proposed fix (apply to all three <div> blocks)

 <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/maintain-and-update/partials/replacement-using-creator.mdx`
around lines 7 - 49, The three image wrapper <div> blocks use invalid Spanish
CSS identifiers (margen, maxAnchura, "columna", "centro") which breaks layout;
update each wrapper (the three blocks that surround Selectversion.png,
Invalidkey.png, and Replacekey.png) to use valid React inline style keys/values:
margin, maxWidth, display, flexDirection set to "column", and alignItems set to
"center" (keep the existing "600px" value for maxWidth and "flex" for display).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

CSS property names and values must not be translated — layout will break.

Crowdin has translated the JS style-object keys and CSS keyword values into Spanish. React passes these directly to the browser's style engine, which does not understand margen, maxAnchura, "columna", or "centro". All four declarations are silently dropped, leaving the image unstyled (full-width, uncentered, non-flex).

🐛 Proposed fix

 <div
 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.

Suggested change

	<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 contains translated CSS property
names/values causing the browser to ignore them; update the style keys/values in
the JSX element (the style passed to the div) to use proper React/CSS
identifiers: change margen -> margin, maxAnchura -> maxWidth, flexDirection:
"columna" -> flexDirection: "column", and alignItems: "centro" -> alignItems:
"center" so the div's styling (centering, max width, flex column layout) is
applied correctly.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicate admonition opener will break MDX rendering.

:::attention Avant de remplacer on Line 65 is never closed before :::caution Avant de remplacer opens on Line 67. Additionally, attention is not a standard Docusaurus admonition type. This looks like an incomplete replacement — the old directive was left in when the new :::caution was added. Only the single closing ::: on Line 76 exists, so one of these openers is dangling and will produce broken or unexpected output.

Proposed fix — remove the stale :::attention line

-:::attention Avant de remplacer
-
 :::caution Avant de remplacer

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::attention Avant de remplacer
	Avant de remplacer votre clé flash actuelle, envisagez de vérifier s'il y a des erreurs :
	:::caution Avant de remplacer
	:::caution Avant de remplacer

🧰 Tools

🪛 LanguageTool

[typographical] ~65-~65: Une espace est requise.
Context: ...cement de votre dispositif flash USB :::attention Avant de remplacer :::caution...

(DEUX_POINTS_ESPACE)

---

[typographical] ~67-~67: Une espace est requise.
Context: ...USB :::attention Avant de remplacer :::caution Avant de remplacer 1. Éteignez ...

(DEUX_POINTS_ESPACE)

🤖 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/changing-the-flash-device.mdx`
around lines 65 - 67, Remove the stale duplicate admonition opener `:::attention
Avant de remplacer` so only the valid `:::caution Avant de remplacer` remains;
ensure the single closing `:::` after line 76 matches that `:::caution` block
(search for the `:::attention` and `:::caution` tokens in the file and delete
the `:::attention` line).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Find and examine the file in question
FILE=$(fd "configure-your-array.mdx" "i18n/zh" | head -1)
if [ -n "$FILE" ]; then
  echo "=== Chinese version (lines 90-105) ==="
  sed -n '90,105p' "$FILE" | cat -n
  echo
  echo "=== Full context around lines 97-99 ==="
  sed -n '95,102p' "$FILE" | cat -n
fi

# Check if other language versions of this file also have the stray :::
for lang in de es fr; do
  FILE=$(fd "configure-your-array.mdx" "i18n/$lang" | head -1)
  if [ -n "$FILE" ]; then
    echo "=== $lang: lines 95-102 ==="
    sed -n '95,102p' "$FILE" | cat -n
    echo
  fi
done

# Also check the English source
EN_FILE=$(fd "configure-your-array.mdx" "docs" | head -1)
if [ -n "$EN_FILE" ]; then
  echo "=== English source: lines 95-102 ==="
  sed -n '95,102p' "$EN_FILE" | cat -n
fi

Repository: unraid/docs

Length of output: 1485

---

Remove the stray ::: marker on line 99.

The :::info block is properly closed on line 97, but an orphaned ::: on line 99 will cause Docusaurus to attempt parsing it as an admonition opening, resulting in a parse error or broken rendering.

Proposed fix

 :::

-:::

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::
	:::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx`
around lines 98 - 99, Remove the stray standalone ":::“ marker that follows the
closed ":::info" block — locate the orphaned line containing only ":::” and
delete it so the admonition block (started with ":::info" and closed properly)
no longer has an extra opening/closing marker that breaks MDX parsing.

[coderabbitai]

Actionable comments posted: 12

Note

Due to the large number of review comments, Critical severity comments were prioritized as inline comments.

🧹 Nitpick comments (11)

i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx (1)

225-230: Consider deduplicating repeated inline header styles.

Both blocks use the same inline style object. A shared class (or small MDX component) would reduce drift across localized updates.

♻️ Optional cleanup

-<div
-style={{
-fontSize: "1.1em",
-fontWeight: 600,
-marginBottom: "0.5rem",
-marginTop: "1.5rem",
-}}
->
+<div className="faq-subsection-title">

/* in site docs styles */
.faq-subsection-title {
  font-size: 1.1em;
  font-weight: 600;
  margin-bottom: 0.5rem;
  margin-top: 1.5rem;
}

Also applies to: 244-249

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx`
around lines 225 - 230, The inline style object used for subsection headers in
the MDX file (the style prop with fontSize: "1.1em", fontWeight: 600,
marginBottom: "0.5rem", marginTop: "1.5rem") is duplicated; replace both
occurrences by extracting a shared CSS class (e.g., .faq-subsection-title) or a
small MDX/React component (e.g., FaqSubsectionTitle) and update the header
blocks to use that class/component instead of the inline style to prevent drift
across localized updates.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md (1)

350-418: Large repeated webGUI/Dashboard/Docker subsections should be deduplicated.

From this range, several headings/content blocks are duplicated (### Dashboard, ### Docker, repeated NFS paragraph, repeated diagnostics bullets). This makes the release notes internally inconsistent and hard to trust.

🤖 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 350 - 418, The release notes contain duplicated sections (multiple
"### Dashboard" and "### Docker" headings and repeated NFS paragraph "Wir haben
einige neue Einstellungen hinzugefügt, um Probleme mit NFS-Freigaben zu
lösen...")—deduplicate by consolidating repeated content: keep a single "###
Dashboard" and a single "### Docker" block, merge duplicated bulleted lists
(e.g., SMART/SSD, gpujson, anonymization, phplog, Legacy Unraid.net certificate
items) into one coherent list under each heading, and remove the extra copy of
the NFS paragraph so it appears only once.

i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx (1)

186-186: Use a distinct title for the second “Partages utilisateurs…” section.

Line 186 duplicates the heading at Line 156, which makes generated anchors less predictable and navigation less clear.

Proposed fix

-### Partages utilisateurs pour la virtualisation
+### Configurer les partages utilisateurs pour la virtualisation

🤖 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/overview-and-system-prep.mdx`
at line 186, The second identical heading "Partages utilisateurs pour la
virtualisation" is duplicated; locate the second occurrence of that heading and
rename it to a distinct title (for example "Partages utilisateurs pour la
virtualisation — configuration" or "Partages utilisateurs pour la virtualisation
(suite)") so generated anchors are unique and navigation is clear; update only
the heading text in the MDX file where the duplicate appears.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)

91-91: Create-pool procedure duplicates the compression step.

Compression is already covered at Line 91, then repeated again as Step 9 at Line 120. Keep one canonical step to avoid workflow ambiguity.

Also applies to: 120-121

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx`
at line 91, The create-pool procedure currently mentions enabling compression
twice: once in Step 5 ("如果需要，可以启用压缩（推荐用于大多数工作负载）。") and again in Step 9; remove
the duplicate by keeping the canonical compression instruction (preferably the
more detailed instance) and delete or merge the repeated line in the other step,
then renumber or adjust surrounding steps so the workflow remains sequential and
unambiguous.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx (1)

451-452: Duplicate guidance appears twice with near-identical German text.

The same import guidance is repeated in paragraph form (Line 451-452) and again inside the tip (Line 461-462). Consider keeping one canonical version.

Also applies to: 461-462

🤖 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 451 - 452, Remove the duplicated German guidance that appears both
as a standalone paragraph and again inside the tip; keep one canonical instance
(either the paragraph or the tip) to avoid repetition, ensuring the retained
copy preserves the exact wording about exporting all physical drives and
optional support vdevs for new Unraid pools, and delete the other occurrence so
only a single copy of that guidance remains.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx (1)

189-219: Deduplicate repeated guidance blocks.

These changed lines repeat content already present nearby (warnings, ddrescue setup steps, and intro sentences). Consolidating them will improve readability and reduce translation maintenance overhead.

♻️ Suggested cleanup

-Formatieren Sie niemals eine unmontierbare Festplatte über das %%WebGUI|web-gui%%! Das Formatieren löscht alle Daten und aktualisiert %%parity|parity%%, was eine Wiederherstellung unmöglich macht.
@@
-Wenn eine Festplatte, die vorher einwandfrei funktionierte, plötzlich nicht mehr gemountet werden kann, ist es verständlich, sich um Ihre Daten Sorgen zu machen. Diese Art von Problem wird oft durch Dateisystemkorruption verursacht, die nach unsauberen Abschaltungen, Stromunterbrechungen oder fehlerhaften Schreibvorgängen auftreten kann. Das Wichtigste, das Sie sich merken sollten, ist: **Formatieren Sie das Laufwerk nicht**, wenn Sie vom %%WebGUI|web-gui%% dazu aufgefordert werden. Durch Formatieren werden alle vorhandenen Daten gelöscht und die Wiederherstellung erschwert, wenn nicht gar unmöglich gemacht.
@@
-Wenn Standard-Unraid-Wiederherstellungsmethoden, wie das [Ersetzen der Laufwerke](../../using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx) Verfahren, aufgrund mehrerer Plattenausfälle oder ungültiger %%parity|parity%% nicht durchführbar sind, können spezialisierte Tools wie **ddrescue** Ihnen helfen, so viele Daten wie möglich von einer fehlerhaften Festplatte zu retten.
@@
-- Installieren Sie [Nerd Tools](https://unraid-production-481d40bf.preview.craft.cloud/community/apps?q=nerd+tools#r:~:text=of%201%20App-,Nerd%20Tools,-unRaid.es) aus dem **Apps**-Tab in der Unraid %%WebGUI|web-gui%%.
-- Öffnen Sie ***Einstellungen → Nerd Tools*** und aktivieren Sie **ddrescue**.
@@
-Hier ein Beispiel dafür, was Sie während des ersten Durchgangs sehen könnten:

Also applies to: 252-268, 313-313

🤖 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/data-recovery.mdx`
around lines 189 - 219, Remove the duplicated guidance blocks (the repeated
warning/don't-format note in the :::danger::: block, the xfs_repair/btrfs check
instructions, and the ddrescue/Nerd Tools installation note) and consolidate
them into a single, clear section: keep one concise warning (the :::danger:::
block referencing the `#repair-file-systems` anchor), one set of filesystem repair
commands (xfs_repair -v /dev/mdXp1 and btrfs check[/--repair] with the risk
note), and one ddrescue installation line referencing Nerd Tools; update nearby
mentions that currently repeat the same sentences so they point to or reference
the consolidated section instead.

i18n/zh/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx (1)

14-14: Use a fully localized tip title for consistency.

Quick 开始 mixes English and Chinese in the same label. Consider using a single-language label to match surrounding zh-CN UI copy.

✏️ Suggested copy tweak

-:::tip[Quick 开始]
+:::tip[快速开始]

🤖 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/API/how-to-use-the-api.mdx` at
line 14, Replace the mixed-language tip title "Quick 开始" in the MDX tip block
with a fully localized Chinese label to match zh-CN UI copy; update the tip
declaration :::tip[Quick 开始] to :::tip[快速开始] (or another consistent Chinese
phrase) so the title is entirely in Chinese in the document.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx (1)

141-141: Use an ASCII identifier for the value prop.

value="设备" is inconsistent with the sibling tabs (value="windows", value="linux"). The value prop can be persisted to URL search parameters, and a Chinese-character value would appear percent-encoded (e.g., ?tab=%E8%AE%BE%E5%A4%87), which is hard to read and not idiomatic.

♻️ Proposed fix

-  <TabItem value="设备" label="设备虚拟机">
+  <TabItem value="appliance" label="设备虚拟机">

🤖 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/troubleshooting/common-issues/unclean-shutdowns.mdx`
at line 141, Change the TabItem's non-ASCII value to an ASCII identifier so URL
params remain readable: update the TabItem component (TabItem value="设备"
label="设备虚拟机") to use an ASCII value such as value="device" (keep label="设备虚拟机"
for display), ensure the new value is unique among sibling TabItem values (e.g.,
"windows", "linux", "device"), and update any code or documentation that
references the old value in URLs or tests to the new ASCII value.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md (1)

7-13: Anchor IDs for known-issues and rolling-back look correct.

For consistency with the anchor pattern applied to other release note files in this PR (e.g., 6.12.14.md line 3), consider also adding {#upgrade-notes} to the ## Upgrade heading at line 7.

💡 Proposed addition

-## Upgrade
+## Upgrade {`#upgrade-notes`}

🤖 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.1.2.md`
around lines 7 - 13, Add the missing anchor to the top-level Upgrade heading:
modify the "## Upgrade" heading to include the anchor `{`#upgrade-notes`}` so it
reads like "## Upgrade {`#upgrade-notes`}"; keep the existing anchors for "###
Bekannte Probleme {`#known-issues`}" and "### Rückschritte {`#rolling-back`}"
unchanged for pattern consistency with other release note files.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx (1)

153-153: Use the localized UI label instead of “Main”.

In zh docs, this should use “主页面” for consistency with the actual Chinese UI naming.

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/using-unraid-to/manage-storage/file-systems.mdx`
at line 153, The text uses the English UI label "Main" inside the sentence "Run
%%Mover|mover%% from the **Main** tab"; update that phrase to use the localized
Chinese UI label "主页面" so it reads "Run %%Mover|mover%% from the **主页面** tab"
(keeping the %%Mover|mover%% and %%cache|cache%% tokens intact) to match the
Unraid simplified Chinese UI terminology.

i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx (1)

6-7: Unused Tabs and TabItem imports.

These components are imported at lines 6–7 but never referenced in the file. The imports should be removed to keep the document clean.

♻️ Proposed fix

-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 # Automatisiertes Flash-Backup

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx`
around lines 6 - 7, Remove the unused imports Tabs and TabItem from the top of
the document — locate the import statement that declares "Tabs" and "TabItem"
and delete those identifiers (or remove the entire import line if nothing else
is imported from '@theme/...'), ensuring there are no remaining references to
Tabs or TabItem in the file such as in automated-flash-backup.mdx so the linter
no longer flags them as unused.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 932f1fd and 1a827b2.

📒 Files selected for processing (294)

• i18n/de/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-zfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-array-to-pool.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-command-line.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-device-limit.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/cli.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx
• i18n/es/docusaurus-plugin-content-docs/current/contribute/style-guide.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check what files exist in German API docs directory
echo "=== Files in German API docs directory ==="
find i18n/de/docusaurus-plugin-content-docs/current/API/ -type f -name "*.md*" | sort

echo ""
echo "=== OIDC-related files (case-insensitive) ==="
find i18n/de/docusaurus-plugin-content-docs/current/API/ -type f -iname "*oidc*" | sort

echo ""
echo "=== Files with 'Anbieter' in name ==="
find i18n/de/docusaurus-plugin-content-docs/current/API/ -type f -name "*Anbieter*" | sort

Repository: unraid/docs

Length of output: 1113

---

🏁 Script executed:

#!/bin/bash
# Check the frontmatter of the oidc-provider-setup.mdx file
head -30 i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx

Repository: unraid/docs

Length of output: 1116

---

Fix broken link: change href to match actual file slug.

The href ./oIDC-Anbieter-Einrichtung does not match the actual file. The file oidc-provider-setup.mdx generates the slug oidc-provider-setup. Change the href to ./oidc-provider-setup.

🤖 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/index.mdx` around lines 65
- 69, The Card with title "OIDC-Einrichtung" has a broken href; update the Card
component's href prop from "./oIDC-Anbieter-Einrichtung" to the actual slug
"./oidc-provider-setup" (the Card element in i18n/de/.../API/index.mdx).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicate ## Was, wenn ich mehrere Server habe? heading creates a broken document structure.

The heading appears at both Line 19 and Line 24. The content between them (Lines 21–22 — a bullet list) and the three-option list (Lines 26–30) are all rendered under the same duplicate heading, making the document ambiguous and likely breaking anchor navigation. The AI summary notes the original "Was entferne ich …?" section was renamed; it appears one instance of the heading was not cleaned up.

🐛 Proposed fix

-## Was, wenn ich mehrere Server habe?
-
-- Gehen Sie zu Ihrem Unraid-Server.
-- Öffnen Sie das Dropdown-Menü oben rechts und klicken Sie auf „Unraid.net-Konto verwalten", oder alle sichtbaren lizenzschlüsselbezogenen Aktionstasten.
-
-## Was, wenn ich mehrere Server habe?
+## Was, wenn ich mehrere Server habe?
 
 Es gibt drei Optionen:

🧰 Tools

🪛 LanguageTool

[grammar] ~22-~22: Ersetze das Satzzeichen
Context: ...ken Sie auf „Unraid.net-Konto verwalten“, oder alle sichtbaren lizenzschlüsselbez...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_L_DOUBLE_QUOTCOMMA_L_DOUBLE_QUOT)

---

[grammar] ~22-~22: Hier könnte ein Fehler sein.
Context: ...n Sie auf „Unraid.net-Konto verwalten“, oder alle sichtbaren lizenzschlüsselbezogene...

(QB_NEW_DE)

---

[uncategorized] ~22-~22: Uneinheitliche Verwendung von Bindestrichen. Der Text enthält sowohl ‚lizenzschlüsselbezogenen‘ als auch ‚Lizenzschlüssel-bezogenen‘.
Context: ...-Konto verwalten“, oder alle sichtbaren lizenzschlüsselbezogenen Aktionstasten. ## Was, wenn ich mehrer...

(DE_COMPOUND_COHERENCY)

🤖 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-account/server-management.mdx`
around lines 19 - 24, Remove the duplicate "## Was, wenn ich mehrere Server
habe?" heading so the document has a single section header; locate both
occurrences of the heading and delete the extra one (ensure the bullet list and
the subsequent three-option list remain under the single remaining "Was, wenn
ich mehrere Server habe?" header), then verify anchor consistency and that the
renamed "Was entferne ich …?" section wasn’t accidentally left behind.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# 1) List image references in the target file
echo "=== Image references in zfs-storage.mdx ==="
rg -n '!\[]\((\.\/assets\/|\/img\/)[^)]+\)' \
  i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx

echo ""
echo "=== Checking asset file existence ==="
# 2) Verify that referenced asset files exist under i18n assets and global /img sources
fd -t f 'zfs(1|2|3|5|6|8|9|10|11|12|13|14|15|16)\.png'

Repository: unraid/docs

Length of output: 7692

---

🏁 Script executed:

#!/bin/bash
# Check the full directory structure to understand the project layout
echo "=== Project structure for assets and images ==="
find . -type d -name assets -o -type d -name img 2>/dev/null | head -20

echo ""
echo "=== Check for i18n locale-specific asset directories ==="
ls -la i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/ 2>/dev/null || echo "Directory not found"

echo ""
echo "=== Check for global img directory ==="
ls -la img/ 2>/dev/null || echo "img/ directory not found"

echo ""
echo "=== Full count of ZFS image files ==="
find . -name 'zfs*.png' 2>/dev/null | sort

Repository: unraid/docs

Length of output: 9716

---

🏁 Script executed:

#!/bin/bash
# Read the actual file content to see what image paths are used
cat -n i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx | head -100

echo ""
echo "=== Checking all image reference lines ==="
cat -n i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx | grep -E '!\['

Repository: unraid/docs

Length of output: 4930

---

Fix broken image references on lines 363, 409, and 428 — images at /img/ paths do not exist.

The file mixes image path strategies inconsistently. Lines 50–338 correctly use ./assets/zfsN.png, but lines 363, 409, and 428 incorrectly reference /img/zfs14.png, /img/zfs15.png, and /img/zfs16.png. These /img/ paths do not exist in the repository; the images are only available in the local ./assets/ directory. Update those three lines to use ./assets/zfs14.png, ./assets/zfs15.png, and ./assets/zfs16.png respectively to match the pattern used throughout the rest of the file.

🤖 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 50, Update the three broken image references that use absolute /img/
paths to the local assets directory: replace "/img/zfs14.png", "/img/zfs15.png",
and "/img/zfs16.png" with "./assets/zfs14.png", "./assets/zfs15.png", and
"./assets/zfs16.png" respectively so they match the existing pattern (e.g.,
other images like "./assets/zfs1.png") used throughout the document.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicate OEM intro paragraph — identical sentence appears twice consecutively.

Line 57 and Line 59 contain the exact same sentence. One must be removed.

🐛 Proposed fix

 Sie können eine Lizenz über die %%WebGUI|web-gui%% oder durch den Erwerb eines Aktivierungscodes auf der [Unraid-Website](https://unraid.net/pricing) erwerben.
 
-Sie können eine Lizenz über die %%WebGUI|web-gui%% oder durch den Erwerb eines Aktivierungscodes auf der [Unraid-Website](https://unraid.net/pricing) erwerben.
-
 Für OEM-/Wiederverkäuferpreise (10 Lizenzen oder mehr) [kontaktieren Sie Unraid](https://unraid.net/contact) für Sonderpreise.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx`
around lines 57 - 59, The OEM intro sentence "Sie können eine Lizenz über die
%%WebGUI|web-gui%% oder durch den Erwerb eines Aktivierungscodes auf der
[Unraid-Website](https://unraid.net/pricing) erwerben." appears twice
consecutively; remove the redundant duplicate so the paragraph contains the
sentence only once, preserving surrounding formatting and spacing in the
licensing-faq.mdx content.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicate introductory paragraph for the "unlimited storage" section.

Lines 146 and 148 are the same sentence rendered twice — one with straight ASCII quotes and one with proper German curly quotes. Keep only the German-quotes variant.

🐛 Proposed fix

-"Unbegrenzt" bezieht sich auf die maximale Anzahl von Speichergeräten, die Sie basierend auf Ihrer Lizenzstufe an Ihren Unraid-Server anschließen können.
-
-„Unbegrenzt" bezieht sich auf die maximale Anzahl von Speichergeräten, die Sie basierend auf Ihrer Lizenzstufe an Ihren Unraid-Server anschließen können.
+„Unbegrenzt" bezieht sich auf die maximale Anzahl von Speichergeräten, die Sie basierend auf Ihrer Lizenzstufe an Ihren Unraid-Server anschließen können.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	### Was bedeutet "unlimited" für angeschlossene Speichergeräte? {#unlimited-storage}
	„Unbegrenzt“ bezieht sich auf die maximale Anzahl von Speichergeräten, die Sie basierend auf Ihrer Lizenzstufe an Ihren Unraid-Server anschließen können.
	"Unbegrenzt" bezieht sich auf die maximale Anzahl von Speichergeräten, die Sie basierend auf Ihrer Lizenzstufe an Ihren Unraid-Server anschließen können.
	Hier sind die aktuellen Grenzen:
	„Unbegrenzt“ bezieht sich auf die maximale Anzahl von Speichergeräten, die Sie basierend auf Ihrer Lizenzstufe an Ihren Unraid-Server anschließen können.
	### Was bedeutet "unlimited" für angeschlossene Speichergeräte? {`#unlimited-storage`}
	„Unbegrenzt" bezieht sich auf die maximale Anzahl von Speichergeräten, die Sie basierend auf Ihrer Lizenzstufe an Ihren Unraid-Server anschließen können.

🧰 Tools

🪛 LanguageTool

[grammar] ~144-~144: Ersetze das Satzzeichen
Context: ...enz für neue Updates. ### Was bedeutet "unlimited" für angeschlossene Speichergeräte? {#un...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)

---

[grammar] ~145-~145: Ersetze das Satzzeichen
Context: ...e Speichergeräte? {#unlimited-storage} "Unbegrenzt" bezieht sich auf die maximale Anzahl vo...

(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_PUNCTUATION_QUOTE_„)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx`
around lines 144 - 148, The "unlimited storage" section (header "### Was
bedeutet \"unlimited\" für angeschlossene Speichergeräte? {`#unlimited-storage`}")
contains a duplicated introductory sentence; remove the duplicate line that uses
straight ASCII quotes and keep only the line with the proper German curly quotes
(„Unbegrenzt“ ...). Ensure there is a single paragraph immediately after the
header using the curly-quote variant and delete the redundant ASCII-quoted
sentence.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

In-page link target no longer matches the section ID.

The link uses #checking-a-file-system, but this heading does not define that explicit ID anymore.

Also applies to: 451-451

🤖 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`
at line 433, The in-page link target "#checking-a-file-system" no longer matches
the heading "### Überprüfen eines Dateisystems", so either restore the explicit
anchor on that heading or update the links; locate the heading "### Überprüfen
eines Dateisystems" and add an explicit ID attribute (e.g.
{`#checking-a-file-system`}) or change the link targets that currently point to
"#checking-a-file-system" (also mentioned around the other occurrence) to the
heading's actual generated slug so the in-page links resolve.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Removing explicit heading IDs broke existing in-page English-fragment links.

This file still links to #https-with-self-signed-certificate and #https-with-myunraidnet-certificate-and-with-no-fallback-url, but the corresponding headings no longer define those IDs.

Also applies to: 94-94, 133-133

🤖 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/securing-your-connection.mdx`
at line 71, The Spanish translation removed explicit heading IDs, breaking
existing in-page English-fragment links; restore those IDs by adding
MDX/Markdown heading anchors to the relevant headings (for example add
{`#https-with-self-signed-certificate`} to the "HTTPS con certificado autofirmado"
heading and add {`#https-with-myunraidnet-certificate-and-with-no-fallback-url`}
to the corresponding Spanish heading at the other locations), or insert explicit
HTML id attributes (e.g., <h4 id="https-with-self-signed-certificate">...) so
the links to `#https-with-self-signed-certificate` and
`#https-with-myunraidnet-certificate-and-with-no-fallback-url` resolve correctly.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Missing explicit anchor {#changing-a-file-system-type} breaks the internal link at line 229.

Line 229 links to #changing-a-file-system-type. Without the explicit anchor attribute, Docusaurus generates a Spanish slug (#cambiar-un-tipo-de-sistema-de-archivos) and the link will 404.

🐛 Proposed fix

-## Cambiar un tipo de sistema de archivos
+## Cambiar un tipo de sistema de archivos {`#changing-a-file-system-type`}

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	## Cambiar un tipo de sistema de archivos
	## Cambiar un tipo de sistema de archivos {`#changing-a-file-system-type`}

🤖 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/file-systems.mdx`
at line 162, Add an explicit anchor to the Spanish header so the internal link
to `#changing-a-file-system-type` resolves: update the heading "## Cambiar un tipo
de sistema de archivos" to include the anchor attribute
`{`#changing-a-file-system-type`}` so the link at line 229 points to that exact
id; ensure the heading text remains unchanged and only the anchor attribute is
added.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Section ID mismatch breaks the conversion step link.

The conversion steps link to #changing-a-file-system-type, but this heading no longer defines that ID. Re-add the explicit anchor (or update all references).

💡 Suggested fix

-## Changer un type de système de fichiers
+## Changer un type de système de fichiers {`#changing-a-file-system-type`}

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	## Changer un type de système de fichiers
	## Changer un type de système de fichiers {`#changing-a-file-system-type`}

🤖 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/manage-storage/file-systems.mdx`
around lines 162 - 163, The French heading "## Changer un type de système de
fichiers" no longer defines the anchor used by conversion step links
(`#changing-a-file-system-type`); restore the anchor by adding an explicit HTML
anchor with id="changing-a-file-system-type" immediately before that heading (or
alternatively update all references to point to the new French ID), ensuring the
conversion steps' links resolve correctly; target the heading text "Changer un
type de système de fichiers" when making this change.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Search for references to scheduler anchor and page links
echo "=== Searching for scheduler anchor references ==="
rg "scheduler\|customize-unraid-settings" --type=md --type=mdx -n | head -50

echo ""
echo "=== Specifically looking for links to `#scheduler` ==="
rg "#scheduler" --type=md --type=mdx -n

echo ""
echo "=== Searching for links to the target page ==="
rg "customize-unraid-settings" --type=md --type=mdx -n

Repository: unraid/docs

Length of output: 307

---

🏁 Script executed:

#!/bin/bash
# Search for scheduler anchor references using file globbing
echo "=== Searching for `#scheduler` in md and mdx files ==="
rg "#scheduler" -g "*.md" -g "*.mdx" -n

echo ""
echo "=== Searching for customize-unraid-settings links ==="
rg "customize-unraid-settings" -g "*.md" -g "*.mdx" -n

echo ""
echo "=== Broader search for 'scheduler' in markdown files ==="
rg "scheduler" -g "*.md" -g "*.mdx" -n | head -50

Repository: unraid/docs

Length of output: 44066

---

Restore the {#scheduler} anchor or update all cross-references.

Removing the anchor {#scheduler} from this heading breaks links in at least 10 documents across multiple language versions:

• docs/unraid-os/getting-started/explore-the-user-interface/key-features.mdx:19
• docs/unraid-os/using-unraid-to/manage-storage/shares.mdx:235
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/key-features.mdx:19
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx:235
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/key-features.mdx:19
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx:235
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/key-features.mdx:19
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx:235
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/key-features.mdx:19
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx:235

All these files link to customize-unraid-settings.mdx#scheduler. Either restore the explicit anchor or update all links to use the new heading ID.

🤖 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/customize-unraid-settings.mdx`
at line 450, Restore the missing explicit anchor {`#scheduler`} on the "### 调度程序"
heading in customize-unraid-settings.mdx so existing cross-references to
customize-unraid-settings.mdx#scheduler continue to work; locate the heading
line that currently reads "### 调度程序" and re-add the anchor token {`#scheduler`}
immediately following the heading text, or if you prefer to remove the anchor
instead update every incoming link (those pointing to
customize-unraid-settings.mdx#scheduler) to the new auto-generated heading id
consistently across all language variants.

[coderabbitai]

Actionable comments posted: 7

Note

Due to the large number of review comments, Critical severity comments were prioritized as inline comments.

🧹 Nitpick comments (5)

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md (1)

5-5: Consider adding {#upgrade-notes} to the ## Upgrade heading for consistency.

The sibling release-note files in this PR consistently add {#upgrade-notes} to their ## Upgrade/## Upgrade-Hinweise headings. Line 5 here is the only top-level section heading without an explicit anchor, which could make deep-linking to it fragile if the heading text is ever adjusted.

♻️ Suggested addition

-## Upgrade
+## Upgrade {`#upgrade-notes`}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md`
at line 5, Update the top-level "## Upgrade" heading to include the explicit
anchor {`#upgrade-notes`} so it matches the sibling release-note files and ensures
stable deep-linking; locate the "## Upgrade" heading in this document and append
the anchor token exactly as used in the other files.

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (1)

295-295: 避免与“用户实用工具”章节重复同一段插件说明。

Line 295 与 Line 456 文案几乎一致，后续维护时容易漂移。建议在通知章节保留简短引导，详细说明只保留在“用户实用工具”。

💡 Suggested direction

-此处显示第三方插件，增强了 Unraid 的功能，并为您提供更多服务器控制。例如，[社区应用程序插件](../../using-unraid-to/run-docker-containers/community-applications.mdx) 已包含其中。其他插件提供了系统监控、维护、存储管理和 `appdata` 备份等功能。
+有关第三方插件及其扩展能力，请参见下方的[用户实用工具](`#用户实用工具`)部分（例如社区应用程序插件）。

🤖 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/customize-unraid-settings.mdx`
at line 295, The paragraph at the notification section that repeats the plugin
description (the third-party plugins/社区应用程序插件 sentence) should be shortened to a
brief pointer and the full explanation kept only in the “用户实用工具” section;
replace the duplicated full sentence in the notification section with a concise
line like “有关第三方插件及其功能的详细说明，请参见 用户实用工具 一节（社区应用程序插件）” and remove the redundant
detailed text there, leaving the comprehensive description only under the
“用户实用工具” heading so future edits don’t diverge.

i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx (1)

143-151: Nit: single-space indent inside style objects

All three converted style blocks indent properties with one space. Conventional JSX/JS uses two (or four) spaces for object contents, which would align with the surrounding MDX indentation style.

🖌️ Suggested fix (representative block — apply to all three)

 <div
 style={{
-  margin: "auto",
-  maxWidth: "600px",
-  display: "flex",
-  flexDirection: "column",
-  alignItems: "center",
+   margin: "auto",
+   maxWidth: "600px",
+   display: "flex",
+   flexDirection: "column",
+   alignItems: "center",
 }}
 >

Also applies to: 186-194, 211-219

🤖 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 143 - 151, The inline style object in the JSX div (the <div
style={{ ... }}> block containing properties margin, maxWidth, display,
flexDirection, alignItems) and the two other converted style blocks should use a
two-space indent for each property inside the style object instead of the
current single-space indent; update the spacing inside those style objects so
each property line is indented by two spaces (matching surrounding MDX/JSX
conventions) across all three occurrences.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx (1)

126-126: Optional: Consider German typographic quotation marks.

LanguageTool flags the straight ASCII quotes ("...") used here. German typographic convention uses „..." (low-9 opening, right double closing). If the broader German docs adopt a consistent style, it may be worth aligning here.

🤖 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/explore-the-user-interface/tour-the-web-gui.mdx`
at line 126, Replace the straight ASCII quotes around the WireGuard mention so
they use German typographic quotation marks; update the quoted text that
surrounds the token "%%WireGuard|wireguard%%" to use opening low double quote
(„) and closing double quote (”) so the line becomes „%%WireGuard|wireguard%%“
to match German typographic convention and the rest of the German docs.

i18n/es/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx (1)

177-179: “Pre-release Soporte” block duplicates the legacy warning text.

Line 179 repeats the same content already stated in the Legacy Soporte warning above, and doesn’t describe pre-release-specific guidance. Consider removing this block or replacing it with actual pre-release support details.

🤖 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/upcoming-features.mdx`
around lines 177 - 179, The ":::tip[Pre-release Soporte]" block duplicates the
earlier "Legacy Soporte" warning; either remove this duplicate tip or replace
its content with pre-release-specific guidance. Locate the block marked
":::tip[Pre-release Soporte]" in the upcoming-features.mdx and either delete it
or rewrite it to describe pre-release support details (e.g., differences for
Unraid beta versions, installation steps, known limitations, or compatibility
notes) so it does not repeat the "Legacy Soporte" warning.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 932f1fd and 1a827b2.

📒 Files selected for processing (294)

• i18n/de/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-zfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-array-to-pool.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-command-line.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-device-limit.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/cli.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx
• i18n/es/docusaurus-plugin-content-docs/current/contribute/style-guide.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Stray ::: creates an unbalanced admonition fence.

Line 138 introduces a standalone ::: with no corresponding opening admonition directive. This results in an odd number of fence markers (11 total), which will cause an MDX parse error or corrupt the surrounding content.

✏️ 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.

Suggested change

:::

🤖 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, There is a stray admonition fence marker ":::" that
creates an unbalanced admonition block; fix it by either removing that
standalone ":::” or by adding the corresponding opening admonition directive
(e.g., ":::note" or ":::warning" plus its closing ":::") so the admonition fence
is balanced; search for the orphan ":::” marker in the content around the
upcoming-features section and make the change in the same MDX block to restore a
matching pair.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Orphaned ::: closing token — no matching opening admonition.

:::note (line 12) is already closed by ::: at line 16. The newly added ::: at line 18 is a stray token with no corresponding opener and will cause MDX parsing issues or unexpected rendered output.

🐛 Proposed fix

-
-:::

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::

🤖 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/local.mdx`
around lines 17 - 18, Remove the stray closing admonition token by deleting the
unmatched ":::” at the end of the file (the extra token after the existing " 
:::" that closes ":::note"); ensure the only admonition delimiters present are
the matching ":::note" opener and its corresponding closing "  :::".

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicated section heading and bullet list — breaks TOC and repeats content.

Three distinct duplications were introduced:

1. Line 45: ### Entendiendo los Modos de Autorización duplicates the H2 at line 41, creating a conflicting anchor.
2. Line 47: La interfaz ofrece dos modos de autorización: is a verbatim copy of line 43.
3. Lines 55–57: the three bullet points are exact copies of lines 49–51.

Remove the entire duplicated block (lines 45–57).

🐛 Proposed fix

-### Entendiendo los Modos de Autorización
-
-La interfaz ofrece dos modos de autorización:
-
 <details>
   <summary><strong>Modo Avanzado</strong></summary>
 
 ...
 
-**Cuándo usar el Modo Simple:**
-
-- Permitir dominios de correo específicos (por ejemplo, `@empresa.com`)
-- Permitir direcciones de correo específicas
-- Configurar quién puede acceder a tu servidor Unraid con una configuración mínima
-
 <details>

🧰 Tools

🪛 LanguageTool

[grammar] ~45-~45: Corrige la mayúscula.
Context: ...s de autorización: ### Entendiendo los Modos de Autorización La interfaz ofrece dos...

(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)

---

[grammar] ~45-~45: Corrige la mayúscula.
Context: ...rización: ### Entendiendo los Modos de Autorización La interfaz ofrece dos modos de autoriza...

(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)

---

[grammar] ~49-~49: Cambia la palabra o signo.
Context: ... específicos (por ejemplo, @empresa.com) - Permitir direcciones de correo específic...

(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~50-~50: Cambia la palabra o signo.
Context: ...rmitir direcciones de correo específicas - Configurar quién puede acceder a tu serv...

(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~51-~51: Aquí puede haber un error.
Context: ...idor Unraid con una configuración mínima Cuándo usar el Modo Simple: - Permiti...

(QB_NEW_ES)

---

[grammar] ~55-~55: Cambia la palabra o signo.
Context: ... específicos (por ejemplo, @empresa.com) - Permitir direcciones de correo específic...

(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~56-~56: Cambia la palabra o signo.
Context: ...rmitir direcciones de correo específicas - Configurar quién puede acceder a tu serv...

(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~57-~57: Aquí puede haber un error.
Context: ...idor Unraid con una configuración mínima

Modo Avanzado

El modo avanzado ofrece un control granu...

(QB_NEW_ES)

🤖 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/oidc-provider-setup.mdx`
around lines 45 - 57, Remove the duplicated block that reintroduces the section
"### Entendiendo los Modos de Autorización", the repeated sentence "La interfaz
ofrece dos modos de autorización:" and the repeated three bullets (the same list
of allowed domains, specific addresses and minimal Unraid access configuration);
specifically delete the duplicate heading and the repeated paragraph and bullet
list so only the original "Entendiendo los Modos de Autorización" section and
its single set of bullets remain (look for the duplicate heading text and the
identical bullet lines to locate the block).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicate image and caption introduced at lines 228–229.

The image ![Página de inicio de sesión con Botones SSO](/img/api/sso-with-options.png) and its caption are already present at lines 222–223. This duplication renders the same screenshot twice in succession, which is confusing for readers.

🐛 Proposed fix

-![Página de inicio de sesión con Botones SSO](/img/api/sso-with-options.png)
-*Página de inicio de sesión de Unraid mostrando tanto la autenticación de usuario/contraseña tradicional como opciones SSO con botones personalizados de proveedores*
-
 **Ejemplos de URLs base correctas:**

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	
	*Página de inicio de sesión de Unraid mostrando tanto la autenticación de usuario/contraseña tradicional como opciones SSO con botones personalizados de proveedores*
	**Ejemplos de URLs base correctas:**

🧰 Tools

🪛 LanguageTool

[grammar] ~229-~229: Aquí puede haber un error.
Context: ...on botones personalizados de proveedores* Ejemplos de URLs base correctas: - Go...

(QB_NEW_ES)

🤖 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/oidc-provider-setup.mdx`
around lines 228 - 229, Remove the duplicate image block that repeats the
screenshot and caption (the second occurrence of "![Página de inicio de sesión
con Botones SSO](/img/api/sso-with-options.png" and the caption "*Página de
inicio de sesión de Unraid mostrando tanto la autenticación de
usuario/contraseña tradicional como opciones SSO con botones personalizados de
proveedores*"); keep the original instance (the first occurrence) and delete the
redundant lines so the image and caption only appear once in
oidc-provider-setup.mdx.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# First, let's run the provided verification script
rg -n --type=mdx '\(`#scheduler`\)|#scheduler\b'

Repository: unraid/docs

Length of output: 82

---

🏁 Script executed:

#!/bin/bash
# Also check the file itself to understand the context
if [ -f "i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx" ]; then
  echo "=== File exists. Checking lines around 450 ==="
  sed -n '440,460p' "i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx" | cat -n
else
  echo "File not found at expected path"
fi

Repository: unraid/docs

Length of output: 1610

---

🏁 Script executed:

#!/bin/bash
# Check for any links in the codebase (both English and other language versions) 
# that might reference the scheduler anchor
rg -n '\[.*\]\(.*#scheduler' --type=mdx

Repository: unraid/docs

Length of output: 82

---

🏁 Script executed:

#!/bin/bash
# Search for `#scheduler` references without type filter
rg -n '#scheduler\b' .

Repository: unraid/docs

Length of output: 4005

---

🏁 Script executed:

#!/bin/bash
# Search for any links pointing to `#scheduler`
rg -n '\[.*\]\(.*#scheduler' .

Repository: unraid/docs

Length of output: 4005

---

🏁 Script executed:

#!/bin/bash
# Check if there's an English version that might have links to `#scheduler`
find . -name "*customize*unraid*settings*" -type f | head -20

Repository: unraid/docs

Length of output: 607

---

🏁 Script executed:

#!/bin/bash
# Check the English version to compare
sed -n '440,460p' "docs/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx" | cat -n

Repository: unraid/docs

Length of output: 1402

---

Critical: 10+ inbound links across multiple languages reference #scheduler and will break with this heading change.

Files with broken anchor references:

• docs/unraid-os/getting-started/explore-the-user-interface/key-features.mdx
• docs/unraid-os/using-unraid-to/manage-storage/shares.mdx
• Spanish, French, German, and Chinese equivalents of the above

All these files contain active links to customize-unraid-settings.mdx#scheduler. Since ### Programador generates the anchor #programador, these links will fail.

Fix: Either add an explicit anchor ### Programador {#scheduler} to maintain backward compatibility, or update all 10+ inbound references to use #programador.

🤖 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/customize-unraid-settings.mdx`
at line 450, The new Spanish heading "### Programador" changed the generated
anchor and breaks existing links to "#scheduler"; to fix, restore backward
compatibility by adding an explicit anchor to that heading (e.g., change the
heading to include {`#scheduler`} so it reads "### Programador {`#scheduler`}"), or
alternatively update all inbound links that point to
customize-unraid-settings.mdx#scheduler to use `#programador` across the listed
files (e.g.,
docs/unraid-os/getting-started/explore-the-user-interface/key-features.mdx and
docs/unraid-os/using-unraid-to/manage-storage/shares.mdx and their
Spanish/French/German/Chinese equivalents).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Broken internal link — #btrfs-pools anchor no longer exists after removing it from ### Pools ZFS.

Line 184 references [BTRFS pools](#btrfs-pools), but the AI summary confirms the {#btrfs-pools} anchor was removed from the ### Pools ZFS heading (Line 129). Docusaurus will now auto-generate #pools-zfs for that heading, leaving the link on Line 184 dead.

🐛 Proposed fix — restore the explicit anchor on the heading

-### Pools ZFS
+### Pools ZFS {`#btrfs-pools`}

Also applies to: 184-184

🤖 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/manage-storage/cache-pools.mdx`
at line 129, Restore the missing explicit anchor by adding the `{`#btrfs-pools`}`
ID to the "### Pools ZFS" heading so the existing link `[BTRFS
pools](`#btrfs-pools`)` resolves; specifically modify the "### Pools ZFS" heading
to include `{`#btrfs-pools`}`, then verify the link to that anchor (the `[BTRFS
pools](`#btrfs-pools`)` reference) is now working and update any other references
if necessary.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Find direct references to scheduler fragment or explicit anchor id
echo "=== Searching for {`#scheduler`} or `#scheduler` references ==="
rg -n --hidden -g '!**/.git/**' '\{`#scheduler`\}|#scheduler' || echo "No matches found"

echo ""
echo "=== Searching for links to customize-unraid-settings with fragments ==="
rg -n --hidden -g '!**/.git/**' 'customize-unraid-settings(\.mdx)?#' || echo "No matches found"

Repository: unraid/docs

Length of output: 19514

---

Do not remove the explicit anchor {#scheduler} without updating all deep links.

Removing {#scheduler} will break at least 10 active deep links across the repository in multiple language versions:

• docs/unraid-os/getting-started/explore-the-user-interface/key-features.mdx:19
• docs/unraid-os/using-unraid-to/manage-storage/shares.mdx:235
• Chinese, French, Spanish, and German equivalents at the same locations

All of these files link to customize-unraid-settings.mdx#scheduler. If you're switching to auto-generated anchors, you must update these references first or keep the explicit anchor.

🤖 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/customize-unraid-settings.mdx`
at line 450, The explicit anchor `{`#scheduler`}` was removed from
customize-unraid-settings.mdx which will break many deep links; restore the
explicit anchor `{`#scheduler`}` at the "### 调度程序" heading in
i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx,
or if you prefer auto-generated anchors, update every referencing file (e.g.,
docs/unraid-os/getting-started/explore-the-user-interface/key-features.mdx,
docs/unraid-os/using-unraid-to/manage-storage/shares.mdx and their Chinese,
French, Spanish, German equivalents) to point to the new anchor text, ensuring
all occurrences of customize-unraid-settings.mdx#scheduler are replaced with the
correct new anchor.

[coderabbitai]

Actionable comments posted: 6

Note

Due to the large number of review comments, Critical severity comments were prioritized as inline comments.

🧹 Nitpick comments (7)

i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx (2)

450-450: Consider preserving the legacy scheduler anchor for deep-link stability.

If any existing bookmarks/docs use #scheduler, removing the explicit id can break them. Keeping the old anchor is a low-cost compatibility guard.

Suggested fix

-### 调度程序
+### 调度程序 {`#scheduler`}

🤖 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/customize-unraid-settings.mdx`
at line 450, The heading "### 调度程序" should retain the legacy anchor id
"scheduler" so existing deep-links/bookmarks don't break; update the heading
node for "### 调度程序" to include an explicit id attribute (i.e., add the anchor/id
"scheduler") or insert an HTML anchor element immediately before the heading to
preserve the old "#scheduler" URL target.

---

295-295: Refine this paragraph to be notification-specific (or remove duplicate copy).

Line 295 repeats the same plugin text used again in 用户实用工具 (Line 456), which makes this section feel redundant/off-topic.

Suggested edit

-此处显示第三方插件，增强了 Unraid 的功能，并为您提供更多服务器控制。例如，[社区应用程序插件](../../using-unraid-to/run-docker-containers/community-applications.mdx) 已包含其中。其他插件提供了系统监控、维护、存储管理和 `appdata` 备份等功能。
+此处可配置通知相关功能，包括浏览器通知、电子邮件（SMTP）以及第三方通知代理（如 Discord、Telegram 等），用于接收系统事件、更新和警报。

🤖 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/customize-unraid-settings.mdx`
at line 295, The paragraph repeating the third-party plugin description (the
sentence starting "此处显示第三方插件，增强了 Unraid 的功能...") duplicates content already used
in the "用户实用工具" section; either remove this duplicate sentence or rewrite it to
be notification-specific (e.g., explain how notifications interact with plugins,
which plugins trigger notifications, or where notification settings for plugins
live). Locate the duplicate text in the current "设置 Unraid" page (the paragraph
around the notifications subsection) and update it so it no longer repeats the
general plugin description but instead focuses on notification behavior for
plugins or is removed entirely.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx (1)

38-38: Remove extra leading space inside <details> content blocks.

LanguageTool flags unnecessary leading whitespace before the sentence at both lines 38 and 74.

✏️ Proposed fix

-   Die Konfiguration der Unraid %%VM|vm%% erfordert einige spezifische Einstellungen...
+  Die Konfiguration der Unraid %%VM|vm%% erfordert einige spezifische Einstellungen...

(Apply the same single-space trim at line 74.)

Also applies to: 74-74

🤖 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 38, Trim the extra leading space inside the affected <details> content
blocks by removing the single blank character before the sentence "Die
Konfiguration der Unraid %%VM|vm%% erfordert einige spezifische Einstellungen,
um einen ordnungsgemäßen Betrieb sicherzustellen." and do the same for the other
occurrence around the content referenced at the second <details> block; ensure
the text inside each <details> starts immediately (no leading spaces) so both
instances are left-trimmed.

i18n/zh/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx (1)

14-14: Prefer a fully localized tip title.

Quick 开始 mixes English and Chinese; consider 快速开始 for consistency with the rest of the zh doc.

Suggested edit

-:::tip[Quick 开始]
+:::tip[快速开始]

🤖 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/API/how-to-use-the-api.mdx` at
line 14, Replace the mixed-language tip title in the docs tip block—change the
token :::tip[Quick 开始] to a fully localized Chinese label :::tip[快速开始] so the
tip title matches the rest of the zh translations (look for the :::tip[...]
occurrence in how-to-use-the-api.mdx).

i18n/de/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdx (1)

17-30: Use consistent quotation/wording style across the updated lines.

The changed lines mix quote styles and phrasing; normalizing this will improve translation consistency.

✍️ Suggested polish

-2. Öffnen Sie das Dropdown-Menü oben rechts und klicken Sie auf "Unraid.net-Konto verwalten" oder alle sichtbaren Lizenzschlüssel-bezogenen Aktionstasten.
+2. Öffnen Sie das Dropdown-Menü oben rechts und klicken Sie auf „Unraid.net-Konto verwalten“ oder auf eine der sichtbaren lizenzschlüsselbezogenen Aktionstasten.
...
-3. Klicken Sie auf "Server entfernen" auf der Serververwaltungs-Karte.
+3. Klicken Sie auf „Server entfernen“ auf der Serververwaltungs-Karte.

🤖 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-account/server-management.mdx`
around lines 17 - 30, Normalize quotation marks and wording for consistency:
replace any German-style quotes („…“ and „“ “) with standard straight double
quotes ("…") for the strings "Unraid.net-Konto verwalten" and "Server
entfernen", and ensure the phrase for action buttons is identical in both places
(use one consistent wording such as "alle sichtbaren lizenzschlüsselbezogenen
Aktionstasten" with consistent capitalization). Update all occurrences so both
sections use the exact same quoted labels and phrasing.

i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md (1)

7-9: ## Upgrade heading lacks an explicit anchor ID unlike the sibling sections.

Lines 11 and 15 use {#known-issues} and {#rolling-back} respectively to support stable deep-links. For consistency, and to avoid breaking any future cross-references, consider adding {#upgrade-notes} to the upgrade heading, matching the pattern used in other language variants (e.g., the ES 6.12.15.md in this PR).

♻️ Proposed addition

-## Upgrade
+## Upgrade {`#upgrade-notes`}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md`
around lines 7 - 9, The "## Upgrade" heading is missing an explicit anchor ID;
update the heading "## Upgrade" to include the anchor "{`#upgrade-notes`}" (e.g.,
change the heading to "## Upgrade {`#upgrade-notes`}") so it matches the pattern
used by sibling sections like "{`#known-issues`}" and "{`#rolling-back`}" and
maintains consistent deep-linking across translations.

i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx (1)

222-227: Pre-existing: security note and section headings are duplicated in this file.

The **⚠️ 安全注意** block appears identically at Lines 222–225 and 227 (consecutive). Additionally, ## 🏢 提供者特定设置 appears twice (Lines 299 and 306), and the **配置：** subsections are repeated for Microsoft/Azure (Lines 378–380), Keycloak (Lines 392–394), and Authentik (Lines 405–408). These are pre-existing issues not introduced by this PR, but should be cleaned up.

🤖 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/API/oidc-provider-setup.mdx`
around lines 222 - 227, Remove duplicated content blocks in the OIDC provider
docs: delete the repeated security warning block that starts with "**⚠️
安全注意**：始终尽量使用基本URL格式..." so it appears only once, remove the duplicated section
heading "## 🏢 提供者特定设置" so there is a single provider-specific section, and
eliminate the repeated " **配置：**" subsections for Microsoft/Azure, Keycloak, and
Authentik so each provider (Microsoft/Azure, Keycloak, Authentik) has only one
configuration subsection; search for the exact strings "**⚠️ 安全注意**：...", "## 🏢
提供者特定设置", and "**配置：**" to locate and remove the duplicates within the file.

---

ℹ️ Review info

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 932f1fd and 1a827b2.

📒 Files selected for processing (294)

• i18n/de/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-account/server-management.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/create-your-bootable-media.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.9.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.0.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.1.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.2.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/monitor-performance/smart-reports-and-disk-health.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/user-management.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/data-recovery.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/partials/data-recovery/repair-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-check-cli-zfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-btrfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/fs-repair-cli-xfs.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-array-to-pool.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/move-pool-to-array.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-command-line.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-device-limit.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/troubleshoot-license-issues.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/partials/managing-and-customizing-containers/environment-variables.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/cli.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/programmatic-api-key-management.mdx
• i18n/es/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx
• i18n/es/docusaurus-plugin-content-docs/current/contribute/style-guide.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-manual-method.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/partials/replacement-using-creator.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-mobile.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/partials/wireguard-configure-other-devices.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-flash-drive.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/partials/syslog-server/remote.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/multi-language-support.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/apple-time-machine.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/how-to-use-the-api.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/index.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/API/oidc-provider-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-account/redeem-activation-code.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/automated-flash-backup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/overview-and-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-connect/remote-access.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/getting-started/what-is-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.10.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.11.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.12.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.13.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.14.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.15.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.5.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.6.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.8.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/6.12.9.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.0.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.1.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.2.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.1.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.3.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/release-notes/7.2.4.md
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-connection.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/securing-your-data.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/tailscale.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/system-administration/secure-your-server/wireguard.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/boot-and-startup-failures.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/system-crashes-and-stability.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/diagnostics/udma-crc-errors.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/licensing-faq.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/overview-and-system-prep.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/unraid-as-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-conversion-and-migration.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/vm-setup.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/create-virtual-machines/windows-on-a-vm.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/customize-your-experience/plugins.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/_category_.json
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/array/removing-disks-from-array.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/file-systems.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/array-check-parity.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-data-disk-parity-preserve.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/shares.mdx
• i18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/overview.mdx

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify suspicious standalone admonition delimiters in this file.

FILE="i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx"

# Check if file exists
if [ ! -f "$FILE" ]; then
  echo "File not found: $FILE"
  exit 1
fi

echo "=== Lines 128-146 with line numbers ==="
nl -ba "$FILE" | sed -n '128,146p'

echo ""
echo "=== All delimiter (:::) lines in this file ==="
nl -ba "$FILE" | grep ':::' | head -20

Repository: unraid/docs

Length of output: 243

---

🏁 Script executed:

#!/bin/bash
# Find the file first
echo "=== Searching for upcoming-features.mdx ==="
find . -name "upcoming-features.mdx" -type f 2>/dev/null

echo ""
echo "=== Alternative search ==="
fd "upcoming-features.mdx" 2>/dev/null || echo "fd not found, trying find..."

Repository: unraid/docs

Length of output: 782

---

🏁 Script executed:

#!/bin/bash
FILE="i18n/de/docusaurus-plugin-content-docs/current/API/upcoming-features.mdx"

# Get total lines first
TOTAL_LINES=$(wc -l < "$FILE")
echo "File has $TOTAL_LINES total lines"
echo ""

# Read lines 128-146 with cat -n
echo "=== Lines 128-146 with line numbers ==="
cat -n "$FILE" | sed -n '128,146p'

echo ""
echo "=== All lines with ::: delimiter ==="
cat -n "$FILE" | grep ':::' | head -30

Repository: unraid/docs

Length of output: 1244

---

Remove unmatched admonition delimiter on line 138.

The standalone ::: on line 138 is unmatched (no corresponding opening delimiter) and will break MDX rendering for the section that follows.

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.

Suggested change

	:::
	### Unraid v7.2-beta.1 Highlights
	### 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 - 140, Remove the unmatched standalone admonition delimiter
':::' that appears immediately before the "### Unraid v7.2-beta.1 Highlights"
heading; open the file section around the heading (look for the literal ':::'
and the heading text) and delete that stray delimiter so the MDX renders
correctly.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Escaped bracket in admonition title will break rendering.

:::note\[Timing] has a backslash before [ which will either render the title incorrectly as \[Timing] or cause an MDX parse error. Docusaurus expects :::note[Timing].

🐛 Proposed fix

-:::note\[Timing]
+:::note[Timing]

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::note\[Timing]
	:::note[Timing]

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/manage-storage/partials/remove-disk-gui.mdx`
at line 17, The admonition start token currently uses an escaped bracket
":::note\[Timing]" which breaks MDX parsing; update the admonition tag (the line
containing ":::note\[Timing]") to remove the backslash so it reads
":::note[Timing]" (i.e., replace "\[" with "[") to ensure the admonition title
renders correctly by Docusaurus.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicate ### 🚀 Inicio Rápido heading immediately after </details>.

Line 17 already has ## 🚀 Inicio Rápido as a section heading. The repeated H3 at line 28 creates a duplicate anchor and a redundant heading rendering in the middle of the section.

🐛 Proposed fix

 </details>

-### 🚀 Inicio Rápido
-
 ![Página de inicio de sesión con opciones SSO](/img/api/sso-with-options.png)

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

### 🚀 Inicio Rápido

🧰 Tools

🪛 LanguageTool

[grammar] ~28-~28: Aquí puede haber un error.
Context: ...vo proveedor

### 🚀 Inicio Rápido *Página de inicio de sesión mostrando el...

(QB_NEW_ES)

🤖 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/oidc-provider-setup.mdx`
around lines 28 - 29, Remove the duplicate "### 🚀 Inicio Rápido" heading that
appears immediately after the </details> block; keep the original "## 🚀 Inicio
Rápido" section header (the one at the top of the section) and either delete the
H3 or replace it with non-heading text. Locate the duplicate by searching for
the exact strings "### 🚀 Inicio Rápido" and "</details>" and remove or demote
the H3 so there is only a single "## 🚀 Inicio Rápido" anchor in the document.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Duplicate heading and bullet fragments in the troubleshooting section.

Line 249 introduces ## "URI de redirección inválido" as an H2 section, but line 253 immediately repeats it as an H4 (#### "URI de redirección inválido") inside a ### Solución de problemas H3, creating duplicate anchors. Lines 255–256 also duplicate the bullets at lines 260–261.

🐛 Proposed fix

-## "URI de redirección inválido"
-
 ### Solución de problemas

-#### "URI de redirección inválido"
-
-- Verifica que al menos una regla de autorización esté configurada
-- Verifica que el proveedor esté habilitado/guardado
-
 #### No se puede ver el botón de inicio de sesión

🧰 Tools

🪛 LanguageTool

[grammar] ~255-~255: Cambia la palabra o signo.
Context: ...a regla de autorización esté configurada - Verifica que el proveedor esté habilitad...

(QB_NEW_ES_OTHER_ERROR_IDS_REPLACEMENT_OTHER)

---

[grammar] ~256-~256: Aquí puede haber un error.
Context: ...ue el proveedor esté habilitado/guardado #### No se puede ver el botón de inicio de se...

(QB_NEW_ES)

🤖 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/oidc-provider-setup.mdx`
around lines 249 - 256, Remove the duplicate heading and repeated bullets for
"URI de redirección inválido": keep a single canonical heading (either the
top-level H2 "URI de redirección inválido" or the nested H4 under "Solución de
problemas") and delete the redundant one so anchors aren’t duplicated;
consolidate the troubleshooting bullets ("Verifica que al menos una regla de
autorización esté configurada" and "Verifica que el proveedor esté
habilitado/guardado") so they appear only once under the chosen heading
(reference the headings "URI de redirección inválido" and the section "Solución
de problemas" to locate and remove the duplicate H4 and duplicate bullet list).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Removing explicit anchor IDs breaks internal cross-reference links.

Lines 157 and 171 contain internal links that reference the English-based anchor IDs which were set explicitly on the headings before this PR:

• Line 157: [HTTPS con un certificado autofirmado](#https-with-self-signed-certificate) — targets the anchor previously on the heading now at line 71.
• Line 171: [HTTPS con certificado Myunraid.net y sin URL de respaldo](#https-with-myunraidnet-certificate-and-with-no-fallback-url) — targets the anchor previously on the heading now at line 133.

After removal, Docusaurus auto-generates slugs from the Spanish heading text (e.g., #https-con-certificado-autofirmado), which will no longer match either reference. Both links will 404.

Either restore the explicit anchor IDs on the headings or update the inline links to use the new auto-generated Spanish slugs:

🐛 Option A — restore anchors (minimal change, keeps English cross-linking consistent)

-#### HTTPS con certificado autofirmado
+#### HTTPS con certificado autofirmado {`#https-with-self-signed-certificate`}

-#### HTTPS con certificado Myunraid.net y sin URL de respaldo
+#### HTTPS con certificado Myunraid.net y sin URL de respaldo {`#https-with-myunraidnet-certificate-and-with-no-fallback-url`}

🐛 Option B — update inline links to Spanish slugs

-  - Consulta [HTTPS con un certificado autofirmado](`#https-with-self-signed-certificate`) arriba para más detalles.
+  - Consulta [HTTPS con un certificado autofirmado](`#https-con-certificado-autofirmado`) arriba para más detalles.

-  Consulte la advertencia bajo [HTTPS con certificado Myunraid.net y sin URL de respaldo](`#https-with-myunraidnet-certificate-and-with-no-fallback-url`).
+  Consulte la advertencia bajo [HTTPS con certificado Myunraid.net y sin URL de respaldo](`#https-con-certificado-myunraidnet-y-sin-url-de-respaldo`).

Also applies to: 133-133, 157-157, 171-171

🤖 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/securing-your-connection.mdx`
at line 71, The PR removed explicit English anchor IDs causing internal links to
404; either restore the original HTML anchor IDs on the affected headings (e.g.,
add the explicit id attributes back to the "HTTPS con certificado autofirmado"
and the other heading that previously had ids like
"https-with-self-signed-certificate" and
"https-with-myunraidnet-certificate-and-with-no-fallback-url"), or update the
inline links that point to those anchors (the markdown links such as `[HTTPS con
un certificado autofirmado](`#https-with-self-signed-certificate`)` and `[HTTPS
con certificado Myunraid.net y sin URL de
respaldo](`#https-with-myunraidnet-certificate-and-with-no-fallback-url`)`) to the
new auto-generated Spanish slugs (e.g., `#https-con-certificado-autofirmado` and
the corresponding Spanish slug for the Myunraid.net heading) so internal
cross-references resolve.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Removing the explicit anchor breaks the #changing-a-file-system-type internal link.

Line 229 links to #changing-a-file-system-type. Without the explicit anchor, Docusaurus will generate a Spanish slug (#cambiar-un-tipo-de-sistema-de-archivos) and this cross-reference will 404.

🐛 Proposed fix

-## Cambiar un tipo de sistema de archivos
+## Cambiar un tipo de sistema de archivos {`#changing-a-file-system-type`}

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	## Cambiar un tipo de sistema de archivos
	## Cambiar un tipo de sistema de archivos {`#changing-a-file-system-type`}

🤖 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/file-systems.mdx`
at line 162, The Spanish heading "## Cambiar un tipo de sistema de archivos"
needs an explicit anchor so the existing cross-reference to
"#changing-a-file-system-type" resolves; edit that heading to include the
English slug as an explicit id (e.g., add `{`#changing-a-file-system-type`}` or an
equivalent HTML anchor) so the link at line 229 points to the correct anchor.