@@ -31,7 +31,7 @@ The queue table shows the following columns by default: Status, Artist, Album Ti
 ### Queue statuses
 
 | Icon | Status | Description | Resolution |
-|---|---|---|---|
+| --- | --- | --- | --- |
 | Grey cloud | Queued | The item is waiting in the download client and hasn't started downloading yet. | Wait for the download client to start it. |
 | Grey clock | Release Pending | The download is waiting for a Delay Profile timer to expire before Lidarr sends it to the download client. | Wait for the delay to pass, or adjust your Delay Profile in Settings. |
 | Yellow arrow | Downloading | The item is actively downloading in the download client. | N/A. |
@@ -59,7 +59,7 @@ Each row has action icons on the right:
 Click **Options** in the queue toolbar to open Table Options:
 
 | Option | Default | Description |
-|---|---|---|
+| --- | --- | --- |
 | Page Size | 20 | Number of queue items shown per page. |
 | Show Unknown Artist Items | On | Shows items in Lidarr's download client category that Lidarr can't match to any artist in your library (for example, removed artists or items added to the category manually). |
 | Columns | (see below) | Choose which columns are visible and their display order. |
 
@@ -22,22 +22,22 @@ Both Lidarr and beets pull from MusicBrainz, but beets exposes more of that data
 ## Release and catalog identifiers
 
 | Field | What it stores |
-|---|---|
+| --- | --- |
 | `catalognum` | The release's catalog number |
 | `asin` | Amazon Standard Identification Number |
 | `barcode` | The release's barcode |
 
 ## Locale and script
 
 | Field | What it stores |
-|---|---|
+| --- | --- |
 | `script` | The writing system used for the release's titles |
 | `language` | Release language |
 
 ## Artist naming
 
 | Field | What it stores |
-|---|---|
+| --- | --- |
 | `artist_credit` | The artist name exactly as credited on this specific release |
 | `albumartist_credit` | The album artist name exactly as credited on this specific release |
 
@@ -62,7 +62,7 @@ Lidarr writes only the release-level disambiguation, into MusicBrainz Album Comm
 Core beets fields since beets 1.5.0, not a plugin:
 
 | Field | What it stores |
-|---|---|
+| --- | --- |
 | `work` | The MusicBrainz Work title (the composition, distinct from the recording) |
 | `mb_workid` | The Work's MBID |
 | `work_disambig` | Disambiguation string for the work |
@@ -197,7 +197,7 @@ foreach ($dir in $albumDirs) {
 ## Trade-offs
 
 | | |
-|---|---|
+| --- | --- |
 | **Benefit** | beets runs once at import time with any plugins you want, writing a full tag set that Lidarr wouldn't produce on its own. |
 | **Benefit** | No persistent beets database to maintain or back up. |
 | **Drawback** | Tags written at import time are never updated. If MusicBrainz data improves, or a plugin source updates its data (for example, updated ReplayGain values), the library files won't reflect it until you re-import or run beets manually. |
@@ -252,7 +252,7 @@ Two scenarios where the tools can conflict:
 ## Trade-offs
 
 | | |
-|---|---|
+| --- | --- |
 | **Benefit** | beets maintains tags on an ongoing basis; as plugin data sources update, you can re-run beets to pull in new values. |
 | **Benefit** | beets' persistent library enables more sophisticated queries, playlist generation, and plugin behaviour. |
 | **Drawback** | Requires careful beets configuration to prevent file moves. One misconfiguration can disorganise a large library. |
@@ -313,7 +313,7 @@ $dir = Split-Path -Parent $env:lidarr_trackfile_path
 ## Trade-offs
 
 | | |
-|---|---|
+| --- | --- |
 | **Benefit** | No separate scheduler to maintain. Reuses Lidarr's own artist-refresh cadence as the trigger, and only runs beets against files that actually changed. |
 | **Benefit** | One hook covers import, manual retag, and periodic MusicBrainz sync. Pattern 1 only covers import. |
 | **Drawback** | Lidarr's write always happens first. If you want beets' choices (for example, its release-specific artist credit) to reliably win over Lidarr's canonical values, this ordering delivers that, but only after Lidarr has written its own value there first, every time. |
 
@@ -17,7 +17,7 @@ The Calendar page shows album releases from artists in your library, laid out we
 Each release tile is color-coded to show its current status:
 
 | Color | Meaning |
-|---|---|
+| --- | --- |
 | Green | All tracks downloaded; Lidarr has a complete copy of this release. |
 | Blue | Monitored and upcoming; the release date is in the future. |
 | Purple | Currently downloading; the release is in the queue or was recently grabbed. |
@@ -38,7 +38,7 @@ Lidarr can expose your calendar as an iCal feed that any calendar client support
 Click the **iCal Feed** button on the Calendar page to open the feed configuration dialog. The options available are:
 
 | Field | Default | Description |
-|---|---|---|
+| --- | --- | --- |
 | Include Unmonitored | Off | When enabled, unmonitored album releases are included in the feed as well as monitored ones. |
 | Past Days | 7 | How many days into the past the feed includes. |
 | Future Days | 28 | How many days into the future the feed includes. |
@@ -56,14 +56,14 @@ The **Options** button opens the Calendar Options dialog, split into two section
 **Local** (apply to this browser only):
 
 | Option | Default | Description |
-|---|---|---|
+| --- | --- | --- |
 | Collapse Multiple Albums | Off | When more than one album from the same artist releases on the same day, collapse them into a single tile instead of showing each one. |
 | Icon for Cutoff Unmet | Off | Show a visual indicator on release tiles where files exist but the quality cutoff hasn't been met. |
 
 **Global** (apply across all browsers and users):
 
 | Option | Description |
-|---|---|
+| --- | --- |
 | First Day of Week | Sets whether weeks start on Sunday or Monday. |
 | Week Column Header | Controls the date format shown above each day column (for example, `Tue 3/25`). |
 | Time Format | Sets the time format used across the calendar (12-hour or 24-hour). |
 
@@ -19,7 +19,7 @@ A custom script can be any executable accessible by the user Lidarr is running a
 Lidarr writes script output to the log files:
 
 | Output | Log level | Log file |
-|---|---|---|
+| --- | --- | --- |
 | `stdout` | `Debug` | `config/logs/Lidarr.debug.txt` |
 | `stderr` | `Error` | `config/logs/Lidarr.txt` |
 | Script trigger | `Trace` | `config/logs/Lidarr.trace.txt` |
@@ -48,7 +48,7 @@ Lidarr passes data to your script through environment variables. The variables a
 These three variables are present in every event.
 
 | Environment Variable | Details |
-|---|---|
+| --- | --- |
 | `lidarr_eventtype` | The event name: `Grab`, `AlbumDownload`, `Rename`, `TrackRetag`, `ArtistAdd`, `ArtistDeleted`, `AlbumDeleted`, `HealthIssue`, `HealthRestored`, `ApplicationUpdate`, `Test` |
 | `lidarr_instancename` | The Lidarr instance name (set in Settings → General) |
 | `lidarr_applicationurl` | The configured application URL (set in Settings → General) |
@@ -58,7 +58,7 @@ These three variables are present in every event.
 Fired when Lidarr sends a release to a download client.
 
 | Environment Variable | Details |
-|---|---|
+| --- | --- |
 | `lidarr_eventtype` | `Grab` |
 | `lidarr_artist_id` | Internal Lidarr ID for the artist |
 | `lidarr_artist_name` | Artist name |
@@ -89,7 +89,7 @@ Fired when Lidarr sends a release to a download client.
 Fired after Lidarr has successfully imported a downloaded album into the library. `lidarr_eventtype` is `AlbumDownload` for both initial imports and upgrades.
 
 | Environment Variable | Details |
-|---|---|
+| --- | --- |
 | `lidarr_eventtype` | `AlbumDownload` |
 | `lidarr_artist_id` | Internal Lidarr ID for the artist |
 | `lidarr_artist_name` | Artist name |
@@ -119,7 +119,7 @@ Fired after Lidarr has successfully imported a downloaded album into the library
 Fired after Lidarr renames one or more track files for an artist.
 
 | Environment Variable | Details |
-|---|---|
+| --- | --- |
 | `lidarr_eventtype` | `Rename` |
 | `lidarr_artist_id` | Internal Lidarr ID for the artist |
 | `lidarr_artist_name` | Artist name |
@@ -137,7 +137,7 @@ Fired after Lidarr renames one or more track files for an artist.
 Fired after Lidarr rewrites tags on one or more track files.
 
 | Environment Variable | Details |
-|---|---|
+| --- | --- |
 | `lidarr_eventtype` | `TrackRetag` |
 | `lidarr_artist_id` | Internal Lidarr ID for the artist |
 | `lidarr_artist_name` | Artist name |
@@ -170,7 +170,7 @@ Fired after Lidarr rewrites tags on one or more track files.
 Fired when you add an artist to Lidarr.
 
 | Environment Variable | Details |
-|---|---|
+| --- | --- |
 | `lidarr_eventtype` | `ArtistAdd` |
 | `lidarr_artist_id` | Internal Lidarr ID for the artist |
 | `lidarr_artist_title` | Artist name |
@@ -185,7 +185,7 @@ Fired when you add an artist to Lidarr.
 Fired when you remove an artist from Lidarr.
 
 | Environment Variable | Details |
-|---|---|
+| --- | --- |
 | `lidarr_eventtype` | `ArtistDeleted` |
 | `lidarr_artist_id` | Internal Lidarr ID for the artist |
 | `lidarr_artist_title` | Artist name |
@@ -201,7 +201,7 @@ Fired when you remove an artist from Lidarr.
 Fired when you remove an album from Lidarr.
 
 | Environment Variable | Details |
-|---|---|
+| --- | --- |
 | `lidarr_eventtype` | `AlbumDeleted` |
 | `lidarr_artist_id` | Internal Lidarr ID for the artist |
 | `lidarr_artist_name` | Artist name |
@@ -222,7 +222,7 @@ Fired when you remove an album from Lidarr.
 Fired when Lidarr detects a health check failure.
 
 | Environment Variable | Details |
-|---|---|
+| --- | --- |
 | `lidarr_eventtype` | `HealthIssue` |
 | `lidarr_health_issue_level` | Severity level: `Ok`, `Notice`, `Warning`, or `Error` |
 | `lidarr_health_issue_message` | Human-readable description of the issue |
@@ -234,7 +234,7 @@ Fired when Lidarr detects a health check failure.
 Fired when a failing health check returns to a healthy state.
 
 | Environment Variable | Details |
-|---|---|
+| --- | --- |
 | `lidarr_eventtype` | `HealthRestored` |
 | `lidarr_health_restored_level` | Previous severity level |
 | `lidarr_health_restored_message` | Description of the check that recovered |
@@ -246,7 +246,7 @@ Fired when a failing health check returns to a healthy state.
 Fired after Lidarr updates itself to a new version.
 
 | Environment Variable | Details |
-|---|---|
+| --- | --- |
 | `lidarr_eventtype` | `ApplicationUpdate` |
 | `lidarr_update_message` | Update changelog message |
 | `lidarr_update_newversion` | Version that was just installed |
 
@@ -145,7 +145,7 @@ Branch=master
 ### Available Keys
 
 | Key | Description | Example |
-|-----|-------------|---------|
+| ----- | ------------- | --------- |
 | `PackageVersion` | Custom package version identifier | `1.0.0-custom` |
 | `PackageAuthor` | Package maintainer name | `Community Package` |
 | `PackageGlobalMessage` | Message displayed in UI | `Custom build for Debian 11` |
@@ -157,7 +157,7 @@ Branch=master
 ### UpdateMethod Values
 
 | Value | Numeric | Description | Use Case |
-|-------|---------|-------------|----------|
+| ------- | --------- | ------------- | ---------- |
 | `BuiltIn` | 0 | Default built-in updater | Standard installations |
 | `Script` | 1 | Updates via custom script | Advanced custom setups |
 | `External` | 10 | Updates managed externally | Package managers, Docker |
 
@@ -74,7 +74,7 @@ A few common causes:
 Lidarr supports three prefixes for direct MBID lookup. All three work the same way and are case-insensitive:
 
 | Prefix | Example |
-|---|---|
+| --- | --- |
 | `lidarr:` | `lidarr:9255f594-b912-4bdf-87a2-ada04502a459` |
 | `lidarrid:` | `lidarrid:9255f594-b912-4bdf-87a2-ada04502a459` |
 | `mbid:` | `mbid:9255f594-b912-4bdf-87a2-ada04502a459` |
 
@@ -50,7 +50,7 @@ Standalone track imports outside the album context use a **60% similarity** thre
 The distance score is a weighted combination of how well each field matches. Lidarr adapts the weights from [beets' default configuration](https://beets.readthedocs.io/), with MusicBrainz IDs as the strongest signals:
 
 | Signal | Weight | Notes |
-|---|---|---|
+| --- | --- | --- |
 | `recording_id` | 10.0 | MusicBrainz Recording MBID. If present and correct, imports almost always succeed. |
 | `album_id` | 5.0 | MusicBrainz Release MBID. |
 | `artist` | 3.0 | Artist name (Levenshtein distance after normalisation). |
 
@@ -72,7 +72,7 @@ When adding an artist you will set:
 **Monitor** is a one-time action, applied to whatever albums Lidarr already has on file at the moment it runs, whether that's when you first add the artist, or later via the **Update Monitoring** bulk action. It does not reach forward to catch albums added to MusicBrainz afterward; that's what [Monitor New Items](#monitor-new-items) is for.
 
 | Option | Sets monitored to true for |
-|---|---|
+| --- | --- |
 | **All Albums** | Every album. |
 | **Future Albums** | Albums with no file that have a release date in the future. Already-released albums, with or without a file, are unmonitored. |
 | **Missing Albums** | Albums with no file, whether already released or upcoming. |
@@ -91,7 +91,7 @@ When adding an artist you will set:
 **Monitor New Items** is an ongoing, artist-level setting. Unlike **Monitor** above, it doesn't run once — it fires every time a metadata refresh finds an album for this artist that isn't already in Lidarr's database.
 
 | Option | Behavior |
-|---|---|
+| --- | --- |
 | **All Albums** | Monitor every newly discovered album. |
 | **New Albums** | Monitor a newly discovered album only if its release date is on or after the most recent release date Lidarr already has on file for that artist. |
 | **None** | Leave newly discovered albums unmonitored. |
 
@@ -30,7 +30,7 @@ Before writing, Lidarr reads the file's current tags and compares them against w
 ## Track and album fields
 
 | Field | Source | Notes |
-|---|---|---|
+| --- | --- | --- |
 | Title | Track title | |
 | Artist | Track's credited artist name | |
 | Album Artist | Album's artist name | |
@@ -46,7 +46,7 @@ Before writing, Lidarr reads the file's current tags and compares them against w
 ## Dates
 
 | Field | Source | Notes |
-|---|---|---|
+| --- | --- | --- |
 | Date | Release date of the specific release matched to this file | |
 | Year | Album release year | |
 | Original Release Date | Album's original release date | Distinguishes a reissue's release date from the date the album was first released. |
@@ -55,7 +55,7 @@ Before writing, Lidarr reads the file's current tags and compares them against w
 ## MusicBrainz identifiers
 
 | Field | Source |
-|---|---|
+| --- | --- |
 | MusicBrainz Artist Id | Track's credited artist |
 | MusicBrainz Release Artist Id | Album artist |
 | MusicBrainz Release Id | The matched release |
@@ -76,7 +76,7 @@ If **Embed Cover Art in Audio Files** is enabled, Lidarr embeds the album's cove
 Most fields above map to the standard tag for the format in use, for example Title becomes `TIT2` in ID3v2 and `TITLE` in Vorbis comments. A handful of fields don't have a standard home in every format and get format-specific treatment:
 
 | Field | ID3v2 (MP3) | Vorbis comments (FLAC, Ogg) |
-|---|---|---|
+| --- | --- | --- |
 | Media Format | `TMED` | `MEDIA` |
 | Date | `TDRC` (ID3v2.4) or `TYER`/`TDAT` (ID3v2.3) | `DATE` |
 | Original Release Date | `TDOR` (ID3v2.4) or `TORY` (ID3v2.3, year only) | `ORIGINALDATE` and `ORIGINALYEAR` |
 
@@ -212,7 +212,7 @@ To add a Spotify relationship on MusicBrainz, open the release and go to **Edit*
 ## Retry or wait
 
 | Situation | Action |
-|---|---|
+| --- | --- |
 | You just submitted an edit at MusicBrainz | Wait ~3 hours, then **Refresh Artist** in Lidarr |
 | You just uploaded cover art to the Cover Art Archive | Allow days, not hours — covers propagate slower than metadata |
 | A release status was `unknown` and you changed it | Wait ~3 hours after the edit's visible on MusicBrainz, then **Refresh Artist** |