Document v4.4.1: fixed rows out of Known Limitations, watched folders on network shares, install tags
Links in tables: [Text](Page) instead of [[Text|Page]] GitHub reads the | of a wiki link inside a table cell as a column separator, so every link in a table rendered as raw [[Text text.
Wiki for 4.4: RSS, download order, queue and share limits, managed WireGuard, Prometheus metrics; Known Limitations re-checked against the code Every page re-verified against v4.4.0 (EN and FR). New pages: Managed-WireGuard, RSS-and-Automatic-Downloads, Queue-Share-and-Speed-Limits, Prometheus-Metrics. Known-Limitations: 79 rows fixed in 4.4 moved to a Fixed in 4.4 section.
Punctuate like a human: commas, not hyphens Replacing the em dashes with a spaced hyphen swapped one tic for another. Nobody writes that. Prose gets a comma, an aside that interrupts a sentence gets parentheses, and a heading that names a thing then explains it gets a colon.
Style pass: no warning emoji, fewer verbal tics Same house style as the UI. The six warning emoji are gone: the bold lead-in already says it is a warning, so the icon was decoration. Trims the words that read as filler once you notice them - deliberately, on purpose, by construction, simply, note that, under the hood. Where the intent genuinely is the point the sentence keeps saying so, and the rest just state the fact. The language-switch flags stay: they are the navigation, not decoration.
Drop the em dashes Same house style as the UI: no em dashes. 355 of them across the wiki, most added by this documentation pass. Replaced with a plain hyphen, which is what the surrounding prose and the commit log already use.
Add a Jobs & moving data page Jobs shipped in v3.100.0 and the wiki never mentioned them: the word 'job' appeared only as an ordinary English noun. So the Jobs tab, the data move behind a category change, the 200 MB/s throughput cap and the piece-by-piece transfer between nodes were all undocumented. Written around the guarantee rather than the feature list, because that is what an operator needs to trust it: across filesystems the source is never removed before the destination is verified, so an interruption leaves the payload where the torrent is still seeding from it. Same for the parts that surprise -- a cross-filesystem move breaks hardlinks and asks first, and the answer is stored so a resumed job does not re-answer it for you.