unraid · elibosley · Apr 24, 2026 · Apr 19, 2026 · Apr 19, 2026 · Apr 19, 2026
diff --git a/.remarkignore b/.remarkignore
@@ -3,3 +3,4 @@ docs/unraid-os/troubleshooting/licensing-faq.mdx
 docs/unraid-os/troubleshooting/tpm-licensing-faq.mdx
 docs/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
 i18n/
+.codex/
diff --git a/docs/API/cli.mdx b/docs/API/cli.mdx
@@ -4,7 +4,6 @@ description: Complete reference for all Unraid API CLI commands
 sidebar_position: 4
 ---
 
-<!-- markdownlint-disable MD025 -->
 
 # CLI commands
 

diff --git a/docs/API/how-to-use-the-api.mdx b/docs/API/how-to-use-the-api.mdx
@@ -4,7 +4,6 @@ description: Learn how to interact with your Unraid server through the GraphQL A
 sidebar_position: 2
 ---
 
-<!-- markdownlint-disable MD025 MD033 -->
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
@@ -206,4 +205,3 @@ For more information about specific commands and configuration options, refer to
 
 :::
 
-<!-- markdownlint-enable MD025 MD033 -->
diff --git a/docs/API/index.mdx b/docs/API/index.mdx
@@ -4,7 +4,6 @@ description: The official GraphQL API for Unraid server management and automatio
 sidebar_position: 1
 ---
 
-<!-- markdownlint-disable MD025 MD033 -->
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
@@ -52,4 +51,3 @@ The [Unraid Connect](../unraid-connect/overview-and-setup.mdx) plugin provides t
 
 For detailed usage instructions, see the [CLI Commands](./cli) reference.
 
-<!-- markdownlint-enable MD025 MD033 -->
diff --git a/docs/API/oidc-provider-setup.mdx b/docs/API/oidc-provider-setup.mdx
@@ -4,7 +4,6 @@ description: Configure OIDC (OpenID Connect) providers for SSO authentication in
 sidebar_position: 3
 ---
 
-<!-- markdownlint-disable MD025 MD007 MD023 -->
 
 # OIDC provider setup
 
@@ -99,7 +98,6 @@ In simple authorization:
 <details>
   <summary><strong>Advanced Mode Examples</strong></summary>
 
-  <!-- markdownlint-disable-next-line MD023 -->
   #### Authorization Rule Mode
 
   When using multiple rules, you can choose how they're evaluated:
@@ -124,7 +122,6 @@ In simple authorization:
 
   This ensures users must have both a company email AND a verified email address.
 
-  <!-- markdownlint-disable-next-line MD023 -->
   #### Group-Based Access (OR Mode)
 
   To allow access to multiple groups:
@@ -141,17 +138,12 @@ In simple authorization:
 
   Users in either `admins` OR `developers` group will be authorized.
 
-  <!-- markdownlint-disable-next-line MD023 -->
   #### Multiple Domains
 
-  <!-- markdownlint-disable-next-line MD007 -->
   - **Claim**: `email`
-  <!-- markdownlint-disable-next-line MD007 -->
   - **Operator**: `endsWith`
-  <!-- markdownlint-disable-next-line MD007 -->
   - **Values**: Add multiple domains (e.g., `company.com`, `subsidiary.com`)
 
-  <!-- markdownlint-disable-next-line MD023 -->
   #### Complex Authorization (AND Mode)
 
   For strict security requiring multiple conditions:
@@ -168,7 +160,6 @@ In simple authorization:
 <details>
   <summary><strong>Configuration Interface Details</strong></summary>
 
-  <!-- markdownlint-disable-next-line MD023 -->
   ### Provider Tabs
 
 - Each configured provider appears as a tab at the top.
@@ -180,36 +171,25 @@ In simple authorization:
 - **Simple**: Best for email-based authorization (recommended for most users).
 - **Advanced**: For complex claim-based rules using JWT claims.
 
-  <!-- markdownlint-disable-next-line MD023 -->
   ### Simple Authorization Fields
 
   When "simple" mode is selected, you'll see:
 
-  <!-- markdownlint-disable-next-line MD007 -->
   - **Allowed Email Domains**: Enter domains without @ (e.g., `company.com`).
     - Helper text: "Users with emails ending in these domains can login"
-  <!-- markdownlint-disable-next-line MD007 -->
   - **Specific Email Addresses**: Add individual email addresses.
     - Helper text: "Only these exact email addresses can login"
-  <!-- markdownlint-disable-next-line MD007 -->
   - **Add Item** buttons to add multiple entries.
 
-  <!-- markdownlint-disable-next-line MD023 -->
   ### Advanced Authorization Fields
 
   When "advanced" mode is selected, you'll see:
 
-  <!-- markdownlint-disable-next-line MD007 -->
   - **Authorization Rule Mode**: Choose `OR` (any rule passes) or `AND` (all rules must pass).
-  <!-- markdownlint-disable-next-line MD007 -->
   - **Authorization Rules**: Add multiple claim-based rules.
-  <!-- markdownlint-disable-next-line MD007 -->
   - **For each rule**:
-    <!-- markdownlint-disable-next-line MD007 -->
     - **Claim**: The JWT claim to check.
-    <!-- markdownlint-disable-next-line MD007 -->
     - **Operator**: How to compare (equals, contains, endsWith, startsWith).
-    <!-- markdownlint-disable-next-line MD007 -->
     - **Value**: What to match against.
 
   ### Additional Interface Elements

diff --git a/docs/API/partials/get-started-v72.mdx b/docs/API/partials/get-started-v72.mdx
@@ -1,4 +1,3 @@
-<!-- markdownlint-disable MD041 -->
 
 1. The API is already installed and running.
 2. Access settings at ***Settings → Management Access → API***.

diff --git a/docs/API/partials/manage-api-keys-gui.mdx b/docs/API/partials/manage-api-keys-gui.mdx
@@ -1,4 +1,3 @@
-<!-- markdownlint-disable MD041 -->
 
 Navigate to ***Settings → Management Access → API Keys*** in your Unraid %%WebGUI|web-gui%% to:
 

diff --git a/docs/API/programmatic-api-key-management.mdx b/docs/API/programmatic-api-key-management.mdx
@@ -4,7 +4,6 @@ description: Create, use, and delete API keys programmatically for automated wor
 sidebar_position: 4
 ---
 
-<!-- markdownlint-disable MD025 MD024 -->
 
 # Programmatic API key management
 

diff --git a/docs/API/upcoming-features.mdx b/docs/API/upcoming-features.mdx
@@ -4,7 +4,6 @@ description: Current status and upcoming features for the Unraid API
 sidebar_position: 10
 ---
 
-<!-- markdownlint-disable MD024 -->
 
 # Roadmap & Features
 

diff --git a/docs/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx b/docs/unraid-os/advanced-configurations/optimize-storage/zfs-storage.mdx
@@ -3,7 +3,6 @@ sidebar_position: 1
 sidebar_label: ZFS storage
 ---
 
-<!-- markdownlint-disable MD041 -->
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
@@ -77,9 +76,7 @@ To create a %%ZFS|zfs%% pool using the %%WebGUI|web-gui%%:
   ![](./assets/zfs3.png)
 </div>
 
-<!-- markdownlint-disable-next-line MD029 -->
 3. Choose a name for your pool (for example, `raptor`).
-<!-- markdownlint-disable-next-line MD029 -->
 4. Set the number of slots to match the number of disks you want in your primary data vdev(s).
 
 :::note
@@ -92,23 +89,19 @@ This initial slot count is for data vdevs only. Support vdevs (such as log or ca
   ![](./assets/zfs4.png)
 </div>
 
-<!-- markdownlint-disable-next-line MD029 -->
 5. Assign disks to the pool (disk order does not matter).
 
 <div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}>
   ![](./assets/zfs5.png)
 </div>
 
-<!-- markdownlint-disable-next-line MD029 -->
 6. Click the pool name (e.g., `raptor`) to open its configuration screen.
-<!-- markdownlint-disable-next-line MD029 -->
 7. Set the file system type to `zfs` or `zfs-encrypted` (for LUKS encryption).
 
 <div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}>
   ![](./assets/zfs6.png)
 </div>
 
-<!-- markdownlint-disable-next-line MD029 -->
 8. Choose your allocation profile - this determines your pool's redundancy and performance.
 
 :::tip
@@ -125,9 +118,7 @@ Before finalizing, review the sections on allocation profiles and topology to ma
   ![](./assets/zfs8.png)
 </div>
 
-<!-- markdownlint-disable-next-line MD029 -->
 9. Enable compression if desired (recommended for most workloads).
-<!-- markdownlint-disable-next-line MD029 -->
 10. Click **Done**, then start the %%array|array%%.
 
 ---
@@ -157,16 +148,13 @@ To add a %%ZFS|zfs%% disk to the %%array|array%%:
   ![](./assets/zfs9.png)
 </div>
 
-<!-- markdownlint-disable-next-line MD029 -->
 5. Under **File system**, choose `zfs` or `zfs-encrypted`.
 
 <div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}>
   ![](./assets/zfs10.png)
 </div>
 
-<!-- markdownlint-disable-next-line MD029 -->
 6. Click **Apply**.
-<!-- markdownlint-disable-next-line MD029 -->
 7. Start the %%array|array%% and let the disk be formatted if needed.
 
 ---
@@ -295,9 +283,7 @@ Unraid can import %%ZFS|zfs%% pools created on other platforms with minimal hass
 
   After importing, running a %%scrub|scrub%% is highly recommended to verify data integrity.
 
-<!-- markdownlint-disable-next-line MD007 -->
   - Click the pool name (e.g., `raptor`) to open its configuration.
-<!-- markdownlint-disable-next-line MD007 -->
   - Under **Pool Status**, check the status and click **Scrub**.
 
   <div style={{ margin: 'auto', maxWidth: '600px', display: 'flex', flexDirection: 'column', alignItems: 'center' }}>

diff --git a/docs/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx b/docs/unraid-os/getting-started/set-up-unraid/customize-unraid-settings.mdx
@@ -255,7 +255,7 @@ You can also configure your server as a %%Subnet Router|subnet-routing%% for loc
 
 ### VPN manager
 
-You can establish a %%VPN|vpn-tunnel%% connection to your Unraid server using [%%Wireguard|wireguard%%](https://www.wireguard.com/) for secure internet connections.
+You can establish a %%VPN|vpn-tunnel%% connection to your Unraid server using [WireGuard](https://www.wireguard.com/) for secure internet connections.
 
 <div style={{ margin: 'auto', maxWidth: '400px'}}>
   ![VPN Manager](/img/settings-vpnmanager.png)

diff --git a/docs/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx b/docs/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
@@ -35,6 +35,7 @@ This page contains frequently asked questions about internal boot in Unraid OS.
   </div>
 </details>
 
+### I switched from flash boot to internal boot, but the system still boots from flash. What should I do? {/* #internal-boot-bios-order */}
 ### Why would I use internal boot instead of a USB flash drive? {/* #internal-boot-benefits */}
 
 Internal boot is optional. If your USB flash boot setup is reliable and fits your server, you do not need to switch just because internal boot exists.
@@ -48,35 +49,35 @@ Internal boot solves a few practical problems:
 
 Internal boot does not make the array faster during normal operation, and it is not required for servers that are already booting reliably from USB.
 
-### I switched from flash boot to internal boot, but the system still boots from flash. What should I do? {#internal-boot-bios-order}
+### I switched from flash boot to internal boot, but the system still boots from flash. What should I do? {/* #internal-boot-bios-order */}
 
 Unraid attempts to update the UEFI boot order automatically. If that does not take effect, manually move your internal boot device(s) to the top of your BIOS/UEFI boot order, save changes, and reboot.
 
-### What should I do if I see "prohibited by secure boot policy" after enabling internal boot? {#internal-boot-secure-boot}
+### What should I do if I see "prohibited by secure boot policy" after enabling internal boot? {/* #internal-boot-secure-boot */}
 
 Disable **Secure Boot** in your BIOS/UEFI settings, then reboot.
 
-### Does an internal boot SSD or NVMe device count toward my attached storage device limit? {#internal-boot-drive-count}
+### Does an internal boot SSD or NVMe device count toward my attached storage device limit? {/* #internal-boot-drive-count */}
 
 Yes. Internal boot SSD/NVMe devices count toward your attached device limit.
 
 Unraid does not currently exclude internal boot drives from the attached device count. If you use mirrored internal boot, both boot devices count.
 
 Specifically, attached storage devices include all devices present before %%array|array%% start, except one eMMC device and one USB device. See [Licensing FAQ](/unraid-os/troubleshooting/licensing-faq/).
 
-### Can I configure internal boot with two SSDs in a mirrored setup for redundancy? {#internal-boot-mirror}
+### Can I configure internal boot with two SSDs in a mirrored setup for redundancy? {/* #internal-boot-mirror */}
 
 Yes. Mirrored internal boot is supported by default.
 
 Internal boot uses %%ZFS|zfs%%, and a mirrored setup uses a %%ZFS mirror|zfs%% for redundancy. If one boot drive fails, Unraid continues running in a degraded state. Replace the failed device through the normal Unraid drive assignment flow to restore the mirror.
 
-### Can I enable internal boot and still license from flash? {#internal-boot-flash-license}
+### Can I enable internal boot and still license from flash? {/* #internal-boot-flash-license */}
 
 Yes. The licensing method is independent of the boot method.
 
 For TPM-based licensing details, see the [TPM Licensing FAQ (7.3+)](/unraid-os/troubleshooting/tpm-licensing-faq/).
 
-### How does flash backup work if I use internal boot? {#internal-boot-flash-backup}
+### How does flash backup work if I use internal boot? {/* #internal-boot-flash-backup */}
 
 Restore the backup to a USB flash drive first using the [Unraid USB Flash Creator](https://unraid.net/download), then boot from that restored USB device.
 

diff --git a/docs/unraid-os/partials/flash-drive-selection-guidance.mdx b/docs/unraid-os/partials/flash-drive-selection-guidance.mdx
@@ -1,4 +1,3 @@
-<!-- markdownlint-disable MD041 -->
 
 Unraid requires boot media with a unique hardware %%GUID|guid%%. For USB boot, this is typically a USB flash drive. Drives that lack a unique %%GUID|guid%% or reuse a %%GUID|guid%% already registered to another user cannot be used with Unraid and may be blacklisted if they cause registration problems.
 

diff --git a/docs/unraid-os/partials/webgui-boot-device-labels.mdx b/docs/unraid-os/partials/webgui-boot-device-labels.mdx
@@ -1,4 +1,3 @@
-<!-- markdownlint-disable MD041 -->
 
 :::note[WebGUI: Boot device vs Flash]
 

diff --git a/docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx b/docs/unraid-os/system-administration/advanced-tools/command-line-interface.mdx
@@ -3,7 +3,6 @@ sidebar_position: 1
 sidebar_label: Command line interface
 ---
 
-<!-- markdownlint-disable MD041 -->
 
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";

diff --git a/docs/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx b/docs/unraid-os/system-administration/advanced-tools/wake-on-lan.mdx
@@ -57,7 +57,7 @@ The plugin manages most sleep configuration options.
 
   To configure sleep manually:
 
-  1. Connect to your server using the %%WebGUI|web-gui%% terminal or [%%SSH|ssh%%](../../system-administration/advanced-tools/command-line-interface.mdx#accessing-the-terminal).
+  1. Connect to your server using the %%WebGUI|web-gui%% terminal or [SSH](../../system-administration/advanced-tools/command-line-interface.mdx#accessing-the-terminal).
 
   2. Identify your primary network interface (usually `eth0`) by running the following command:
 

diff --git a/...raid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx b/...raid-os/system-administration/maintain-and-update/changing-the-flash-device.mdx
@@ -167,7 +167,7 @@ To safely reconfigure your %%array|array%%:
 4. Assign the correct drives as %%parity|parity%% and the rest as data drives in the **Main** tab.
 5. If you have a single %%parity|parity%% drive, the order of data drives is not critical. Check **Parity is Valid** only if you are certain you assigned the same physical parity disk and no writes occurred since the original configuration. For dual %%parity|parity%%, both the order of the data drives and the assignment of parity1 and parity2 are important—parity1 and parity2 are not interchangeable, and %%parity|parity%% must be rebuilt if either is changed.
 6. Start the %%array|array%% to commit assignments. Data drives should mount, and their contents should remain intact.
-7. If you checked **Parity is Valid**, run a correcting [%%parity|parity%% check](../../using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx#parity-checks) to confirm that your configuration is correct.
+7. If you checked **Parity is Valid**, run a correcting [parity check](../../using-unraid-to/manage-storage/array/array-health-and-maintenance.mdx#parity-checks) to confirm that your configuration is correct.
 
 :::note
 

diff --git a/...raid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx b/...raid-os/system-administration/secure-your-server/secure-your-outgoing-comms.mdx
@@ -10,8 +10,8 @@ The outgoing proxy manager and %%Tailscale|tailscale%% exit nodes provide a way
 There are three main methods to secure your outgoing communications:
 
 1. [**Outgoing Proxy Manager**](#setting-up-a-proxy-server) - This tool routes HTTP traffic through a proxy server, allowing you to manage and direct your web requests securely.
-2. [**%%Tailscale|tailscale%% exit nodes**](#tailscale-exit-nodes) - With %%Tailscale|tailscale%% exit nodes, all your traffic can be routed through %%Tailscale|tailscale%%'s mesh network, ensuring a secure connection across your devices.
-3. [**%%WireGuard|wireguard%% %%VPN|vpn-tunnel%%**](#outgoing-vpn-connections) - You can also use %%WireGuard|wireguard%% %%VPN|vpn-tunnel%% to route your traffic through commercial %%VPN|vpn-tunnel%% providers, adding an extra layer of privacy and security.
+2. [**Tailscale exit nodes**](#tailscale-exit-nodes) - With %%Tailscale|tailscale%% exit nodes, all your traffic can be routed through %%Tailscale|tailscale%%'s mesh network, ensuring a secure connection across your devices.
+3. [**WireGuard VPN**](#outgoing-vpn-connections) - You can also use %%WireGuard|wireguard%% %%VPN|vpn-tunnel%% to route your traffic through commercial %%VPN|vpn-tunnel%% providers, adding an extra layer of privacy and security.
 
 ### Outgoing Proxy Manager vs. Tailscale/WireGuard/VPN
 
@@ -23,7 +23,7 @@ There are three main methods to secure your outgoing communications:
 | Isolate Docker or VM traffic                     | %%VPN\|vpn-tunnel%% or container proxy       | Configure %%VPN\|vpn-tunnel%% at the container/VM level for granular control.                                                       |
 | Access home network from anywhere                | %%Tailscale\|tailscale%% exit nodes          | Route traffic through your home network for consistent IP and geo-location.                                                         |
 
-For most users, solutions like [%%Tailscale|tailscale%%](./tailscale.mdx) or [%%WireGuard|wireguard%%](./wireguard.mdx) are preferred for full-system security and privacy. Use Outgoing Proxy Manager when you only need to proxy Unraid's own HTTP requests.
+For most users, solutions like [Tailscale](./tailscale.mdx) or [WireGuard](./wireguard.mdx) are preferred for full-system security and privacy. Use Outgoing Proxy Manager when you only need to proxy Unraid's own HTTP requests.
 
 ### Setting up a proxy server
 
@@ -46,7 +46,7 @@ The %%WebGUI|web-gui%% will automatically use the selected proxy for outgoing sy
 - **If your organization provides a proxy:** Use the address and credentials supplied by your network administrator.
 - **If you need to set up your own:**
   - The [Proxy Server Docker container by @ich777](https://forums.unraid.net/profile/72388-ich777/) is tested and works well with Unraid.
-  - You can configure this container to route traffic through a commercial %%VPN|vpn-tunnel%% using Unraid's [%%WireGuard|wireguard%% %%VPN|vpn-tunnel%%](wireguard.mdx) or connect it to another Docker-based %%VPN|vpn-tunnel%% service.
+  - You can configure this container to route traffic through a commercial %%VPN|vpn-tunnel%% using Unraid's [WireGuard VPN](wireguard.mdx) or connect it to another Docker-based %%VPN|vpn-tunnel%% service.
   - For reliability, host the proxy server on a separate system from Unraid to ensure network availability during boot.
 
 To monitor proxy traffic, go to the **Docker** tab on the proxy host system, select the **Proxy Server** container, and view **Logs**.
@@ -97,7 +97,7 @@ Tailscale has teamed up with Mullvad VPN to provide commercial exit nodes. You c
 
 You can also set up a Docker container to function as a %%Tailscale|tailscale%% exit node on your Unraid server.
 
-1. **Deploy a %%Tailscale|tailscale%% container** using the [official %%Tailscale|tailscale%% Docker image](https://hub.docker.com/r/tailscale/tailscale).
+1. **Deploy a %%Tailscale|tailscale%% container** using the [official Tailscale Docker image](https://hub.docker.com/r/tailscale/tailscale).
 2. **Configure the container** by adding the `--advertise-exit-node` flag.
 3. **Approve the exit node** in your %%Tailscale|tailscale%% admin console.
 4. **Select the container** as an exit node for your other devices on the %%Tailnet|tailnet%%.
-Original file line number
+Diff line change
@@ Expand Up / @@ -3,3 +3,4 @@ docs/unraid-os/troubleshooting/licensing-faq.mdx @@
     docs/unraid-os/troubleshooting/tpm-licensing-faq.mdx
     docs/unraid-os/getting-started/set-up-unraid/internal-boot-faq.mdx
     i18n/
+    .codex/
Original file line number	Diff line number	Diff line change
		@@ -1,4 +1,3 @@
		<!-- markdownlint-disable MD041 -->

		Navigate to *Settings → Management Access → API Keys* in your Unraid %%WebGUI\|web-gui%% to:

Expand Down
Original file line number	Diff line number	Diff line change
		@@ -1,4 +1,3 @@
		<!-- markdownlint-disable MD041 -->

		Unraid requires boot media with a unique hardware %%GUID\|guid%%. For USB boot, this is typically a USB flash drive. Drives that lack a unique %%GUID\|guid%% or reuse a %%GUID\|guid%% already registered to another user cannot be used with Unraid and may be blacklisted if they cause registration problems.

Expand Down
Original file line number	Diff line number	Diff line change
		@@ -1,4 +1,3 @@
		<!-- markdownlint-disable MD041 -->

		:::note[WebGUI: Boot device vs Flash]

Expand Down