Open
Conversation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughAdds Onboarding wizard content (Unraid 7.3+), introduces TPM-based licensing guidance and boot-device terminology throughout docs, adds 7.3.0 release notes, and applies wide formatting and wording standardization across many MDX files and i18n variants. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Tip You can make CodeRabbit's review stricter and more nitpicky using the `assertive` profile, if that's what you prefer.Change the |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
unraid-docs | 77c06df | Commit Preview URL Branch Preview URL |
Mar 16 2026, 09:46 PM |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)
140-159: Use semantic lists for the BIOS checklist.These checklist items are plain lines with hard breaks, which is brittle in MDX and less friendly for accessibility/translation tooling. Converting them to actual list items will render more consistently and be easier to maintain.
Suggested shape
### Basic Settings -✅ Set the USB flash drive as the primary boot device.\ - ✅ Configure the storage controller to **%%AHCI|ahci%%** mode with SATA connections.\ - ✅ Set the controller to **%%HBA mode|hba-mode%%** (not **%%RAID|raid%%**).\ - ✅ Disable **Secure Boot** as it is not supported by Unraid OS. +- ✅ Set the USB flash drive as the primary boot device. +- ✅ Configure the storage controller to **%%AHCI|ahci%%** mode with SATA connections. +- ✅ Set the controller to **%%HBA mode|hba-mode%%** (not **%%RAID|raid%%**). +- ✅ Disable **Secure Boot** because it is not supported by Unraid OS.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 140 - 159, Convert the hard‑wrapped checklist lines under the "Basic Settings", "Advanced Settings", and "Troubleshooting Tips" headings into proper semantic Markdown/MDX lists (e.g., unordered lists or task list items like - [x]) so each checkbox becomes a real list item; update the lines containing the checklist tokens (e.g., "Set the USB flash drive as the primary boot device.", "Configure the storage controller to **%%AHCI|ahci%%** mode...", "Enable **%%hardware virtualization|hvm%%**...", and the troubleshooting entries) to be list items rather than plain text with trailing backslashes, preserving the inline tokens (%%...%%) and check states.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 107-123: The "Register your license key" section currently targets
Unraid 7.2 and earlier but doesn't cover the Unraid 7.3+ onboarding flow; either
add a new "For Unraid 7.3 and later" subsection under the same heading that
describes the new registration path (what UI entry point to use during
first-boot onboarding or the updated WebGUI flow, and screenshots to match) or
explicitly mark the existing content as "Legacy (7.2 and earlier)". Update or
add text and images referenced in the section (the "Get Started" and "Install
trial key" descriptions) to reflect the correct steps for 7.3+, and keep the
heading "Register your license key" so readers can find both legacy and
current-version guidance.
---
Nitpick comments:
In
`@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 140-159: Convert the hard‑wrapped checklist lines under the "Basic
Settings", "Advanced Settings", and "Troubleshooting Tips" headings into proper
semantic Markdown/MDX lists (e.g., unordered lists or task list items like -
[x]) so each checkbox becomes a real list item; update the lines containing the
checklist tokens (e.g., "Set the USB flash drive as the primary boot device.",
"Configure the storage controller to **%%AHCI|ahci%%** mode...", "Enable
**%%hardware virtualization|hvm%%**...", and the troubleshooting entries) to be
list items rather than plain text with trailing backslashes, preserving the
inline tokens (%%...%%) and check states.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: f03ebcf7-9904-487a-b644-397031a650d1
⛔ Files ignored due to path filters (7)
static/img/onboarding_step1.pngis excluded by!**/*.pngstatic/img/onboarding_step2.pngis excluded by!**/*.pngstatic/img/onboarding_step3a.pngis excluded by!**/*.pngstatic/img/onboarding_step3b.pngis excluded by!**/*.pngstatic/img/onboarding_step4.pngis excluded by!**/*.pngstatic/img/onboarding_step5.pngis excluded by!**/*.pngstatic/img/onboarding_step6.pngis excluded by!**/*.png
📒 Files selected for processing (1)
docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
Show resolved
Hide resolved
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)
107-127:⚠️ Potential issue | 🟠 MajorDocument the 7.3+ registration entry point or mark this as legacy.
After the new onboarding section, this block still drops readers into the older Get Started registration flow without saying whether it applies to 7.3+. That leaves current-version users without a clear handoff from onboarding to license registration. Please either add the 7.3+ path here or explicitly label this section as a legacy 7.2-and-earlier flow.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 107 - 127, The "Register your license key" section currently points users to the older "Get Started" flow (mentions %%WebGUI|web-gui%% and "Get Started") but doesn't state whether it applies to 7.3+; update the section to either (A) add the 7.3+ registration entry point after the onboarding flow (describe where to find license registration in 7.3+ and update screenshots/labels accordingly), or (B) explicitly mark this section as "Legacy (7.2 and earlier)" and link to the new 7.3+ onboarding documentation; update the heading or callout text (the "Register your license key" heading, the "Get Started" references, and the "Tools → Registration" note) so readers have a clear handoff for current-version users.
🧹 Nitpick comments (1)
docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)
61-105: Colocate the new screenshots with this doc instead of/img.These newly added images are still referenced from the global
/imgbucket, which makes the page harder to maintain and drifts from the contributor checklist for new doc assets. Please move them into an adjacentassets/folder and switch the references to relative paths/imports.Example pattern
-  + Apply the same pattern to the other new onboarding and registration screenshots.
Also applies to: 113-120
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 61 - 105, The new onboarding screenshots in deploy-and-configure-unraid-os.mdx are referenced from the global /img bucket; move those image files into a local assets/ directory adjacent to this MDX and update the references in this file (e.g., change "/img/onboarding_step1.png" etc.) to relative paths or imported asset variables (for example "./assets/onboarding_step1.png" or import onboardingStep1 from './assets/onboarding_step1.png' and use {onboardingStep1}) so the images are colocated with the document and follow the contributor checklist; apply the same change for all other new onboarding/registration screenshots referenced in the file (including the ones noted in the comment).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 53-57: The callout header text is inconsistent with the body;
update the note tag label from "Unraid 7.3 only" to match the body wording
(e.g., "Unraid 7.3 and later") by changing :::note[Unraid 7.3 only] to
:::note[Unraid 7.3 and later] so the callout and the sentence "The onboarding
wizard below applies to Unraid 7.3 and later." are consistent.
---
Duplicate comments:
In
`@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 107-127: The "Register your license key" section currently points
users to the older "Get Started" flow (mentions %%WebGUI|web-gui%% and "Get
Started") but doesn't state whether it applies to 7.3+; update the section to
either (A) add the 7.3+ registration entry point after the onboarding flow
(describe where to find license registration in 7.3+ and update
screenshots/labels accordingly), or (B) explicitly mark this section as "Legacy
(7.2 and earlier)" and link to the new 7.3+ onboarding documentation; update the
heading or callout text (the "Register your license key" heading, the "Get
Started" references, and the "Tools → Registration" note) so readers have a
clear handoff for current-version users.
---
Nitpick comments:
In
`@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 61-105: The new onboarding screenshots in
deploy-and-configure-unraid-os.mdx are referenced from the global /img bucket;
move those image files into a local assets/ directory adjacent to this MDX and
update the references in this file (e.g., change "/img/onboarding_step1.png"
etc.) to relative paths or imported asset variables (for example
"./assets/onboarding_step1.png" or import onboardingStep1 from
'./assets/onboarding_step1.png' and use {onboardingStep1}) so the images are
colocated with the document and follow the contributor checklist; apply the same
change for all other new onboarding/registration screenshots referenced in the
file (including the ones noted in the comment).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 1c7ce9be-d66d-4ed2-878e-ad29d434e3c6
📒 Files selected for processing (1)
docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
Outdated
Show resolved
Hide resolved
elibosley
force-pushed
the
feature/internal-boot
branch
from
36eb5cc to
88fdb43
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx (1)
53-57:⚠️ Potential issue | 🟡 MinorMake the version callout consistent.
Line 53 says "Unraid 7.3 only", but Line 55 says the wizard applies to "7.3 and later." These scopes conflict.
-:::note[Unraid 7.3 only] +:::note[Unraid 7.3 and later] The onboarding wizard below applies to Unraid 7.3 and later.,
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx` around lines 53 - 57, The callout label ":::note[Unraid 7.3 only]" conflicts with the following sentence "The onboarding wizard below applies to Unraid 7.3 and later." Update one of them so both state the same scope: either change the callout label to ":::note[Unraid 7.3 and later]" to match the sentence, or change the sentence to "The onboarding wizard below applies to Unraid 7.3 only." Make the edit in the deploy-and-configure-unraid-os.mdx file by updating the text inside the callout tag or the sentence accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 142-159: Normalize the leading spaces for all checklist lines so
indentation is consistent: remove the extra leading spaces before "Set the USB
flash drive as the primary boot device", "Configure the storage controller to
**%%AHCI|ahci%%** mode with SATA connections", "Set the controller to **%%HBA
mode|hba-mode%%** (not **%%RAID|raid%%**)", "Disable **Secure Boot** as it is
not supported by Unraid OS", the Advanced Settings items such as "Enable
**%%hardware virtualization|hvm%%** features" and "Enable **%%IOMMU|iommu%%**
support", and the Troubleshooting Tips lines like "Adjusting the boot order to:
**Forced-FDD**, **USB-HDD**, **USB-ZIP**", ensuring every checklist line uses
the same leading whitespace (either none or one space) so rendered indentation
is uniform.
---
Duplicate comments:
In
`@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`:
- Around line 53-57: The callout label ":::note[Unraid 7.3 only]" conflicts with
the following sentence "The onboarding wizard below applies to Unraid 7.3 and
later." Update one of them so both state the same scope: either change the
callout label to ":::note[Unraid 7.3 and later]" to match the sentence, or
change the sentence to "The onboarding wizard below applies to Unraid 7.3 only."
Make the edit in the deploy-and-configure-unraid-os.mdx file by updating the
text inside the callout tag or the sentence accordingly.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: a07a4d44-7f69-49e0-b398-83685b22132b
⛔ Files ignored due to path filters (7)
static/img/onboarding_step1.pngis excluded by!**/*.pngstatic/img/onboarding_step2.pngis excluded by!**/*.pngstatic/img/onboarding_step3a.pngis excluded by!**/*.pngstatic/img/onboarding_step3b.pngis excluded by!**/*.pngstatic/img/onboarding_step4.pngis excluded by!**/*.pngstatic/img/onboarding_step5.pngis excluded by!**/*.pngstatic/img/onboarding_step6.pngis excluded by!**/*.png
📒 Files selected for processing (1)
docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx
Comment on lines
+142
to
+159
| ✅ Set the USB flash drive as the primary boot device.\ | ||
| ✅ Configure the storage controller to **%%AHCI|ahci%%** mode with SATA connections.\ | ||
| ✅ Set the controller to **%%HBA mode|hba-mode%%** (not **%%RAID|raid%%**).\ | ||
| ✅ Disable **Secure Boot** as it is not supported by Unraid OS. | ||
|
|
||
| ### Advanced Settings | ||
| ### Advanced Settings | ||
|
|
||
| ✅ Enable **%%hardware virtualization|hvm%%** features (e.g., **%%Intel VT-x|intel-vt-x%%** or **%%AMD-V|amd-v%%**) for **%%virtual machines (VMs)|vm%%**.\ | ||
| ✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs. | ||
| ✅ Enable **%%hardware virtualization|hvm%%** features (e.g., **%%Intel VT-x|intel-vt-x%%** or **%%AMD-V|amd-v%%**) for **%%virtual machines (VMs)|vm%%**.\ | ||
| ✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs. | ||
|
|
||
| ### Troubleshooting Tips | ||
| ### Troubleshooting Tips | ||
|
|
||
| If Unraid OS does not boot, try: | ||
| If Unraid OS does not boot, try: | ||
|
|
||
| ✅ Adjusting the boot order to: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\ | ||
| ✅ Disabling USB 2.0/3.0 support.\ | ||
| ✅ Toggling any Fast Boot features.\ | ||
| ✅ Toggling USB keyboard support. | ||
| ✅ Adjusting the boot order to: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\ | ||
| ✅ Disabling USB 2.0/3.0 support.\ | ||
| ✅ Toggling any Fast Boot features.\ | ||
| ✅ Toggling USB keyboard support. |
Contributor
There was a problem hiding this comment.
Inconsistent leading spaces in checklist items.
Some checkmark items have a leading space (lines 143-145, 150, 157-159) while others don't (lines 142, 149, 154, 156). This creates inconsistent indentation in the rendered output.
✅ Set the USB flash drive as the primary boot device.\
- ✅ Configure the storage controller to **%%AHCI|ahci%%** mode with SATA connections.\
- ✅ Set the controller to **%%HBA mode|hba-mode%%** (not **%%RAID|raid%%**).\
- ✅ Disable **Secure Boot** as it is not supported by Unraid OS.
+✅ Configure the storage controller to **%%AHCI|ahci%%** mode with SATA connections.\
+✅ Set the controller to **%%HBA mode|hba-mode%%** (not **%%RAID|raid%%**).\
+✅ Disable **Secure Boot** as it is not supported by Unraid OS.
### Advanced Settings
✅ Enable **%%hardware virtualization|hvm%%** features (e.g., **%%Intel VT-x|intel-vt-x%%** or **%%AMD-V|amd-v%%**) for **%%virtual machines (VMs)|vm%%**.\
- ✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs.
+✅ Enable **%%IOMMU|iommu%%** support (Intel VT-d or AMD-Vi) for PCI device assignment to VMs.
### Troubleshooting Tips
If Unraid OS does not boot, try:
✅ Adjusting the boot order to: **Forced-FDD**, **USB-HDD**, **USB-ZIP**.\
- ✅ Disabling USB 2.0/3.0 support.\
- ✅ Toggling any Fast Boot features.\
- ✅ Toggling USB keyboard support.
+✅ Disabling USB 2.0/3.0 support.\
+✅ Toggling any Fast Boot features.\
+✅ Toggling USB keyboard support.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@docs/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os.mdx`
around lines 142 - 159, Normalize the leading spaces for all checklist lines so
indentation is consistent: remove the extra leading spaces before "Set the USB
flash drive as the primary boot device", "Configure the storage controller to
**%%AHCI|ahci%%** mode with SATA connections", "Set the controller to **%%HBA
mode|hba-mode%%** (not **%%RAID|raid%%**)", "Disable **Secure Boot** as it is
not supported by Unraid OS", the Advanced Settings items such as "Enable
**%%hardware virtualization|hvm%%** features" and "Enable **%%IOMMU|iommu%%**
support", and the Troubleshooting Tips lines like "Adjusting the boot order to:
**Forced-FDD**, **USB-HDD**, **USB-ZIP**", ensuring every checklist line uses
the same leading whitespace (either none or one space) so rendered indentation
is uniform.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 5
🧹 Nitpick comments (6)
docs/unraid-os/troubleshooting/common-issues/data-recovery.mdx (1)
225-225: Use an absolute path forsuper.datto reduce ambiguity.At Line 225, consider formatting the path as
/config/super.datinstead ofconfig/super.datso readers interpret it as a root-relative location on the boot device.✏️ Suggested wording tweak
-Losing your %%array|array%% configuration can be stressful, but it doesn't mean your data is gone. The %%array|array%% configuration file (located at `config/super.dat` on your boot device) tells Unraid how your drives are assigned and which ones serve as %%parity|parity%%. If you've lost your boot device or don’t have a recent backup, you can recover your %%array|array%% by carefully reassigning the drives. +Losing your %%array|array%% configuration can be stressful, but it doesn't mean your data is gone. The %%array|array%% configuration file (located at `/config/super.dat` on your boot device) tells Unraid how your drives are assigned and which ones serve as %%parity|parity%%. If you've lost your boot device or don’t have a recent backup, you can recover your %%array|array%% by carefully reassigning the drives.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/unraid-os/troubleshooting/common-issues/data-recovery.mdx` at line 225, Update the documentation text that refers to the Unraid configuration file so the path is absolute: change the referenced `config/super.dat` string to `/config/super.dat` wherever it appears in the paragraph about losing your %%array|array%% configuration (specifically in the sentence that mentions "located at `config/super.dat` on your boot device") to make clear it is a root-relative path on the boot device; keep the surrounding wording intact.docs/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx (2)
4-6: Update screenshot alt text to match the new terminology.The alt text still says Flash Backup, which now conflicts with the updated Boot Device Backup wording.
Proposed doc tweak
-  + 🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx` around lines 4 - 6, Update the image alt text to use the new terminology: replace the current alt text "Flash Backup" in the JSX img element (the node rendering ) with "Boot Device Backup" so the alt attribute and any visible description match the updated wording across the docs.
1-2: Consider clarifying what the downloaded ZIP is used for.A short clause here (e.g., that the ZIP contains the full Unraid install/config and can be used in USB Flash Creator via Use custom) would make this step more self-contained for replacement workflows.
Based on learnings: Unraid’s flash backup ZIP includes OS + config and is restorable via USB Flash Creator’s “Use custom” option.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx` around lines 1 - 2, Clarify what the downloaded ZIP from the "Boot Device Backup" step contains and how it is used: update the text near the "Boot Device" / "Boot Device Backup" steps to add a short clause stating the ZIP contains the full Unraid OS and configuration and can be used to recreate the USB by selecting "Use custom" in the USB Flash Creator (so readers know it's restorable for replacement workflows).i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx (1)
55-55: Align link label text with the new boot-device terminology.Line 55 updates the URL, but the sentence/link label still references “clé USB,” which is inconsistent with the destination page’s boot-device terminology.
Proposed wording update
-Avant d'installer, envisagez de sauvegarder votre clé USB pour protéger votre configuration. Consultez [Sécurisez votre clé USB](../../system-administration/secure-your-server/secure-your-boot-drive.mdx) pour obtenir des conseils de sauvegarde. +Avant d'installer, envisagez de sauvegarder votre périphérique de démarrage pour protéger votre configuration. Consultez [Sécurisez votre périphérique de démarrage](../../system-administration/secure-your-server/secure-your-boot-drive.mdx) pour obtenir des conseils de sauvegarde.🤖 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/run-docker-containers/community-applications.mdx` at line 55, Update the link label and surrounding sentence to use the boot-device terminology instead of "clé USB": replace the visible text "Sécurisez votre clé USB" (and the preceding "votre clé USB" in the sentence) with "Sécurisez votre périphérique de démarrage" so the anchor text and sentence match the destination page's terminology while keeping the existing URL.i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx (1)
55-55: Update the visible Spanish wording to match the new boot-device target.Line 55 updates the destination, but the sentence/link label still uses “flash,” which is inconsistent with the linked page.
Proposed wording update
-Antes de instalar, considera realizar una copia de seguridad de tu flash para proteger tu configuración. Consulta [Asegura tu unidad flash](../../system-administration/secure-your-server/secure-your-boot-drive.mdx) para obtener orientación sobre copias de seguridad. +Antes de instalar, considera realizar una copia de seguridad de tu dispositivo de arranque para proteger tu configuración. Consulta [Asegura tu dispositivo de arranque](../../system-administration/secure-your-server/secure-your-boot-drive.mdx) para obtener orientación sobre copias de seguridad.🤖 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/run-docker-containers/community-applications.mdx` at line 55, Update the visible Spanish wording that currently says "Asegura tu unidad flash" to match the new boot-device terminology used in the linked page (secure-your-boot-drive.mdx): change the sentence/link label in community-applications.mdx from "Asegura tu unidad flash" to "Asegura tu unidad de arranque" (or "Asegura tu dispositivo de arranque" if that matches the linked page wording) so the link text and surrounding sentence consistently reference the boot device.docs/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx (1)
34-34: Minor inconsistency: image alt text references "Flash backup".The alt text "Select the Flash backup button" still uses the old "Flash" terminology. While the image file path (
/img/flashbackup.png) may remain unchanged, consider updating the alt text for consistency.Suggested fix
-  + 🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx` at line 34, The image alt text "Select the Flash backup button" is using the old "Flash" terminology; update that alt text to use the current terminology used elsewhere in the docs (replace "Flash" with the preferred term) for the markdown image referencing /img/flashbackup.png so the alt string matches the rest of the content and accessibility labels.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx`:
- Line 21: Update the heading text in the target document so the link targets
match terminology used elsewhere: locate the heading currently written as "###
Backing up your flash device" and change it to "### Backing up your boot device"
(so links from upgrading-unraid.mdx that point to Backing up your boot device
resolve correctly); ensure the heading punctuation and spacing remain consistent
and no other heading IDs are altered.
In `@docs/unraid-os/troubleshooting/faq.mdx`:
- Around line 272-273: The second line currently uses a double-dash continuation
("-- Always [back up your boot device]...") instead of a Markdown list item;
replace the leading "--" with a single hyphen and a space to make it a proper
bullet point (i.e., change "-- Always ..." to "- Always ...") so the note
becomes a consistent Markdown list item in the FAQ section.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx`:
- Line 268: The list item "Ab Unraid OS 6.9 beginnt Partition 1..." contains a
literal "\n --" which breaks Markdown; edit that text to remove the escape
sequence and render the note correctly by placing the dash-started sentence on
its own line (e.g., end the previous sentence, add a real newline, then start
"-- Sichern Sie immer [Ihr Flash-Laufwerk]..." or convert it into a proper
sub-list or sentence), updating the string in the MDX so the note list renders
properly.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx`:
- Line 272: The line beginning with the literal "\-- Siempre [respalda tu unidad
flash]..." should be converted to a proper markdown list bullet; locate the
malformed string ("\-- Siempre [respalda tu unidad
flash](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups)
antes de comenzar este proceso de conversión.") and replace the leading "\--"
with "- " so it renders as a bullet ("- Siempre ...") in the FAQ.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx`:
- Line 272: The sentence "À partir d'Unraid OS 6.9..." contains a literal "\n"
and a double hyphen; remove the "\n", split the content into two real lines so
the warning appears on the following paragraph, and replace the double hyphen
("--") with a proper em-dash ("—") and correct spacing per French typographic
rules; locate and update the exact sentence in the FAQ content block in
unraid-os/troubleshooting/faq.mdx to apply these changes.
---
Nitpick comments:
In
`@docs/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdx`:
- Around line 4-6: Update the image alt text to use the new terminology: replace
the current alt text "Flash Backup" in the JSX img element (the node rendering
) with "Boot Device Backup" so the alt
attribute and any visible description match the updated wording across the docs.
- Around line 1-2: Clarify what the downloaded ZIP from the "Boot Device Backup"
step contains and how it is used: update the text near the "Boot Device" / "Boot
Device Backup" steps to add a short clause stating the ZIP contains the full
Unraid OS and configuration and can be used to recreate the USB by selecting
"Use custom" in the USB Flash Creator (so readers know it's restorable for
replacement workflows).
In
`@docs/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdx`:
- Line 34: The image alt text "Select the Flash backup button" is using the old
"Flash" terminology; update that alt text to use the current terminology used
elsewhere in the docs (replace "Flash" with the preferred term) for the markdown
image referencing /img/flashbackup.png so the alt string matches the rest of the
content and accessibility labels.
In `@docs/unraid-os/troubleshooting/common-issues/data-recovery.mdx`:
- Line 225: Update the documentation text that refers to the Unraid
configuration file so the path is absolute: change the referenced
`config/super.dat` string to `/config/super.dat` wherever it appears in the
paragraph about losing your %%array|array%% configuration (specifically in the
sentence that mentions "located at `config/super.dat` on your boot device") to
make clear it is a root-relative path on the boot device; keep the surrounding
wording intact.
In
`@i18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx`:
- Line 55: Update the visible Spanish wording that currently says "Asegura tu
unidad flash" to match the new boot-device terminology used in the linked page
(secure-your-boot-drive.mdx): change the sentence/link label in
community-applications.mdx from "Asegura tu unidad flash" to "Asegura tu unidad
de arranque" (or "Asegura tu dispositivo de arranque" if that matches the linked
page wording) so the link text and surrounding sentence consistently reference
the boot device.
In
`@i18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx`:
- Line 55: Update the link label and surrounding sentence to use the boot-device
terminology instead of "clé USB": replace the visible text "Sécurisez votre clé
USB" (and the preceding "votre clé USB" in the sentence) with "Sécurisez votre
périphérique de démarrage" so the anchor text and sentence match the destination
page's terminology while keeping the existing URL.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: f4b161a2-ed89-45fe-8135-62b676ec1dc4
📒 Files selected for processing (37)
docs/unraid-os/getting-started/explore-the-user-interface/tour-the-web-gui.mdxdocs/unraid-os/getting-started/set-up-unraid/complete-your-post-setup-essentials.mdxdocs/unraid-os/getting-started/set-up-unraid/configure-your-array.mdxdocs/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdxdocs/unraid-os/getting-started/what-is-unraid.mdxdocs/unraid-os/release-notes/7.3.0.mddocs/unraid-os/system-administration/advanced-tools/command-line-interface.mdxdocs/unraid-os/system-administration/advanced-tools/wake-on-lan.mdxdocs/unraid-os/system-administration/maintain-and-update/partials/backup-using-webgui.mdxdocs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdxdocs/unraid-os/system-administration/secure-your-server/secure-your-boot-drive.mdxdocs/unraid-os/system-administration/secure-your-server/security-fundamentals.mdxdocs/unraid-os/system-administration/secure-your-server/wireguard.mdxdocs/unraid-os/troubleshooting/common-issues/data-recovery.mdxdocs/unraid-os/troubleshooting/common-issues/docker-troubleshooting.mdxdocs/unraid-os/troubleshooting/common-issues/partials/unclean-shutdowns/flash-drive-failure.mdxdocs/unraid-os/troubleshooting/common-issues/unclean-shutdowns.mdxdocs/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs.mdxdocs/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdxdocs/unraid-os/troubleshooting/diagnostics/partials/syslog-server/mirror.mdxdocs/unraid-os/troubleshooting/faq.mdxdocs/unraid-os/troubleshooting/licensing-faq.mdxdocs/unraid-os/troubleshooting/partials/licensing-faq/manual-keyfile-offline.mdxdocs/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance.mdxdocs/unraid-os/using-unraid-to/manage-storage/shares.mdxdocs/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdxdocs/unraid-os/using-unraid-to/run-docker-containers/overview.mdxdocusaurus.config.tsglossary.yamli18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/es/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/fr/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdxi18n/zh/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
✅ Files skipped from review due to trivial changes (8)
- docs/unraid-os/troubleshooting/common-issues/docker-troubleshooting.mdx
- docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
- i18n/de/docusaurus-plugin-content-docs/current/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
- docs/unraid-os/using-unraid-to/run-docker-containers/community-applications.mdx
- docs/unraid-os/troubleshooting/diagnostics/partials/syslog-server/local.mdx
- docs/unraid-os/getting-started/set-up-unraid/configure-your-array.mdx
- docs/unraid-os/system-administration/secure-your-server/wireguard.mdx
- docs/unraid-os/system-administration/secure-your-server/security-fundamentals.mdx
| :::note[Prerequisites] | ||
|
|
||
| Before you start upgrading, make sure to create a complete backup of your USB flash device. For more details, refer to [Backing up your flash device](../maintain-and-update/changing-the-flash-device.mdx#backing-up-your-flash-device). | ||
| Before you start upgrading, make sure to create a complete backup of your boot device. For more details, refer to [Backing up your boot device](../maintain-and-update/changing-the-flash-device.mdx#backing-up-your-flash-device). |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check if the target anchor exists in the referenced file
echo "=== Checking anchor in target file ==="
rg -n "backing-up-your-flash-device|backing-up-your-boot-device" --glob "changing-the-flash-device.mdx"
echo ""
echo "=== Looking for heading that would generate the anchor ==="
rg -n -i "backing up your (flash|boot) device" --glob "changing-the-flash-device.mdx"Repository: unraid/docs
Length of output: 1077
🏁 Script executed:
#!/bin/bash
# Check the content around lines 21 and 144 in upgrading-unraid.mdx
echo "=== Content around line 21 ==="
sed -n '19,23p' docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
echo ""
echo "=== Content around line 144 ==="
sed -n '142,146p' docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx
echo ""
echo "=== Target heading in changing-the-flash-device.mdx ==="
sed -n '79p' docs/unraid-os/system-administration/maintain-and-update/changing-the-flash-device.mdxRepository: unraid/docs
Length of output: 826
Update the target heading to align with boot device terminology.
Lines 21 and 144 link to "Backing up your boot device" but the target heading in changing-the-flash-device.mdx line 79 still reads "### Backing up your flash device". Update the target heading to "### Backing up your boot device" for terminology consistency across the documentation.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx`
at line 21, Update the heading text in the target document so the link targets
match terminology used elsewhere: locate the heading currently written as "###
Backing up your flash device" and change it to "### Backing up your boot device"
(so links from upgrading-unraid.mdx that point to Backing up your boot device
resolve correctly); ensure the heading punctuation and spacing remain consistent
and no other heading IDs are altered.
Comment on lines
272
to
+273
| - Starting with Unraid OS 6.9, partition 1 starts at 32KiB for rotational devices and 1MiB for non-rotational devices, regardless of the partition style. | ||
| -- Always [back up your flash drive](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups) before starting this conversion process. | ||
| -- Always [back up your boot device](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) before starting this conversion process. |
Contributor
There was a problem hiding this comment.
Formatting issue: double dash should be a bullet point.
Line 273 starts with -- which appears to be a continuation note that should be a proper bullet point for consistent markdown formatting.
Proposed fix
- Starting with Unraid OS 6.9, partition 1 starts at 32KiB for rotational devices and 1MiB for non-rotational devices, regardless of the partition style.
- -- Always [back up your boot device](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) before starting this conversion process.
+- Always [back up your boot device](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) before starting this conversion process.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/unraid-os/troubleshooting/faq.mdx` around lines 272 - 273, The second
line currently uses a double-dash continuation ("-- Always [back up your boot
device]...") instead of a Markdown list item; replace the leading "--" with a
single hyphen and a space to make it a proper bullet point (i.e., change "--
Always ..." to "- Always ...") so the note becomes a consistent Markdown list
item in the FAQ section.
| - **Größer als 2TB**: Verwendet immer GPT-Partitionierung | ||
|
|
||
| - Ab Unraid OS 6.9 beginnt Partition 1 bei 32 KiB für rotierende Geräte und 1 MiB für nicht rotierende Geräte, unabhängig vom Partitionsstil.\n -- Sichern Sie immer [Ihr Flash-Laufwerk](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups), bevor Sie diesen Konvertierungsprozess starten. | ||
| - Ab Unraid OS 6.9 beginnt Partition 1 bei 32 KiB für rotierende Geräte und 1 MiB für nicht rotierende Geräte, unabhängig vom Partitionsstil.\n -- Sichern Sie immer [Ihr Flash-Laufwerk](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups), bevor Sie diesen Konvertierungsprozess starten. |
Contributor
There was a problem hiding this comment.
Fix malformed Markdown in the note list item.
Line 268 includes a literal \n --, which can render incorrectly and break list formatting.
Proposed markdown fix
-- Ab Unraid OS 6.9 beginnt Partition 1 bei 32 KiB für rotierende Geräte und 1 MiB für nicht rotierende Geräte, unabhängig vom Partitionsstil.\n -- Sichern Sie immer [Ihr Flash-Laufwerk](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups), bevor Sie diesen Konvertierungsprozess starten.
+- Ab Unraid OS 6.9 beginnt Partition 1 bei 32 KiB für rotierende Geräte und 1 MiB für nicht rotierende Geräte, unabhängig vom Partitionsstil.
+- Sichern Sie immer [Ihr Boot-Gerät](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups), bevor Sie diesen Konvertierungsprozess starten.📝 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
| - Ab Unraid OS 6.9 beginnt Partition 1 bei 32 KiB für rotierende Geräte und 1 MiB für nicht rotierende Geräte, unabhängig vom Partitionsstil.\n -- Sichern Sie immer [Ihr Flash-Laufwerk](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups), bevor Sie diesen Konvertierungsprozess starten. | |
| - Ab Unraid OS 6.9 beginnt Partition 1 bei 32 KiB für rotierende Geräte und 1 MiB für nicht rotierende Geräte, unabhängig vom Partitionsstil. | |
| - Sichern Sie immer [Ihr Boot-Gerät](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups), bevor Sie diesen Konvertierungsprozess starten. |
🧰 Tools
🪛 LanguageTool
[grammar] ~268-~268: Wähle ein passenderes Wort
Context: ...e Geräte, unabhängig vom Partitionsstil.\n -- Sichern Sie immer [Ihr Flash-Laufwerk](...
(QB_NEW_DE_OTHER_ERROR_IDS_REPLACEMENT_NOUN)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In
`@i18n/de/docusaurus-plugin-content-docs/current/unraid-os/troubleshooting/faq.mdx`
at line 268, The list item "Ab Unraid OS 6.9 beginnt Partition 1..." contains a
literal "\n --" which breaks Markdown; edit that text to remove the escape
sequence and render the note correctly by placing the dash-started sentence on
its own line (e.g., end the previous sentence, add a real newline, then start
"-- Sichern Sie immer [Ihr Flash-Laufwerk]..." or convert it into a proper
sub-list or sentence), updating the string in the MDX so the note list renders
properly.
|
|
||
| - A partir de Unraid OS 6.9, la partición 1 comienza a las 32KiB para dispositivos rotacionales y a las 1MiB para dispositivos no rotacionales, independientemente del estilo de partición. | ||
| \-- Siempre [respalda tu unidad flash](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups) antes de comenzar este proceso de conversión. | ||
| \-- Siempre [respalda tu unidad flash](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) antes de comenzar este proceso de conversión. |
Contributor
There was a problem hiding this comment.
Fix malformed bullet syntax in the backup reminder.
Line 272 starts with \--, which renders as literal text instead of a list bullet.
✏️ Proposed fix
- \-- Siempre [respalda tu unidad flash](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) antes de comenzar este proceso de conversión.
+ - Siempre [respalda tu unidad flash](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) antes de comenzar este proceso de conversión.📝 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
| \-- Siempre [respalda tu unidad flash](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) antes de comenzar este proceso de conversión. | |
| - Siempre [respalda tu unidad flash](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) antes de comenzar este proceso de conversión. |
🧰 Tools
🪛 LanguageTool
[grammar] ~272-~272: Aquí puede haber un error.
Context: ...endientemente del estilo de partición. -- Siempre [respalda tu unidad flash](.....
(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/unraid-os/troubleshooting/faq.mdx`
at line 272, The line beginning with the literal "\-- Siempre [respalda tu
unidad flash]..." should be converted to a proper markdown list bullet; locate
the malformed string ("\-- Siempre [respalda tu unidad
flash](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups)
antes de comenzar este proceso de conversión.") and replace the leading "\--"
with "- " so it renders as a bullet ("- Siempre ...") in the FAQ.
| - **Plus grand que 2 To** : Utilise toujours un partitionnement GPT | ||
|
|
||
| - À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB pour les dispositifs rotatifs et à 1MiB pour les dispositifs non rotatifs, quel que soit le style de partition.\n -- Toujours [sauvegarder votre clé USB](../system-administration/secure-your-server/secure-your-flash-drive.mdx#backups) avant de commencer ce processus de conversion. | ||
| - À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB pour les dispositifs rotatifs et à 1MiB pour les dispositifs non rotatifs, quel que soit le style de partition.\n -- Toujours [sauvegarder votre clé USB](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) avant de commencer ce processus de conversion. |
Contributor
There was a problem hiding this comment.
Formatting issue: malformed newline escape and typographical dash.
This line contains what appears to be a literal \n string and improper dash formatting. The content should be on separate lines, and the double hyphen (--) should be an em-dash (—) per French typographical conventions.
Proposed fix
-- À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB pour les dispositifs rotatifs et à 1MiB pour les dispositifs non rotatifs, quel que soit le style de partition.\n -- Toujours [sauvegarder votre clé USB](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) avant de commencer ce processus de conversion.
+- À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB pour les dispositifs rotatifs et à 1MiB pour les dispositifs non rotatifs, quel que soit le style de partition.
+- Toujours [sauvegarder votre clé USB](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) avant de commencer ce processus de conversion.📝 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
| - À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB pour les dispositifs rotatifs et à 1MiB pour les dispositifs non rotatifs, quel que soit le style de partition.\n -- Toujours [sauvegarder votre clé USB](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) avant de commencer ce processus de conversion. | |
| - À partir d'Unraid OS 6.9, la partition 1 commence à 32KiB pour les dispositifs rotatifs et à 1MiB pour les dispositifs non rotatifs, quel que soit le style de partition. | |
| - Toujours [sauvegarder votre clé USB](../system-administration/secure-your-server/secure-your-boot-drive.mdx#backups) avant de commencer ce processus de conversion. |
🧰 Tools
🪛 LanguageTool
[typographical] ~272-~272: Ces deux traits d’union peuvent être associés pour former un tiret.
Context: ...quel que soit le style de partition.\n -- Toujours [sauvegarder votre clé USB](.....
(TIRET)
🤖 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/faq.mdx`
at line 272, The sentence "À partir d'Unraid OS 6.9..." contains a literal "\n"
and a double hyphen; remove the "\n", split the content into two real lines so
the warning appears on the following paragraph, and replace the double hyphen
("--") with a proper em-dash ("—") and correct spacing per French typographic
rules; locate and update the exact sentence in the FAQ content block in
unraid-os/troubleshooting/faq.mdx to apply these changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before Submitting This PR, Please Ensure You Have Completed The Following:
Summary by CodeRabbit