docs(web): fix remaining Settings and Introduction drift from docs audit

web/app/[locale]/docs/settings/beta-program/page.tsx

@@ -144,7 +144,7 @@ export default async function BetaProgramPage({
 
       <h2 className="text-2xl font-semibold mt-10 mb-4 text-gray-900">{t("manual.heading")}</h2>
       <p className="mb-4 text-gray-800 leading-relaxed">{t("manual.intro")}</p>
-      <pre className="rounded-md bg-gray-100 p-4 overflow-x-auto text-xs font-mono text-gray-800 leading-relaxed border border-gray-200">{`# Check current channel (returns "beta" or "stable")
+      <pre className="rounded-md bg-gray-100 p-4 overflow-x-auto text-xs font-mono text-gray-800 leading-relaxed border border-gray-200">{`# Check current channel (returns "active" for beta, or "stable")
 jq -r '.beta_program.status // "stable"' /usr/local/share/proxmenux/config.json
 
 # Switch to Stable

web/messages/en/docs/installation.json

@@ -53,11 +53,11 @@
     "calloutBody": "Want to try the latest features before the official release and help shape the final version? The ProxMenux Beta Program gives early access to new functionality — including the newest builds of ProxMenux Monitor — directly from the <code>develop</code> branch. Beta builds may contain bugs or incomplete features. Your feedback helps fix them before the stable release.",
     "intro": "Install the beta version instead of the stable one with:",
     "code": "bash -c \"$(wget -qLO - https://raw.githubusercontent.com/MacRimi/ProxMenux/develop/install_proxmenux_beta.sh)\"",
-    "outro": "Beta is opt-in — you have to explicitly run the beta installer. When a stable release is published, ProxMenux notifies you on the next <code>menu</code> launch and offers to switch automatically. To opt out earlier, use the <betalink>Deactivate Beta Program</betalink> option in Settings."
+    "outro": "Beta is opt-in — you have to explicitly run the beta installer. When a stable release is published, the next <code>menu</code> launch offers it with the regular update prompt. To leave the beta channel, use <betalink>Change Release Channel</betalink> in Settings and pick Stable."
   },
   "updating": {
     "heading": "Updating",
-    "body": "ProxMenux self-updates. When a new version is available, the next <code>menu</code> launch offers the update; accepting replaces utility files and configurations in place. No manual download needed. Stable users get stable releases; beta users get beta releases (and the auto-switch prompt above when a stable cuts over). The prompt shape depends on where <code>menu</code> runs: over SSH or the Proxmox console it is a classic yes / no dialog, and accepting applies the update immediately. Inside the WebSocket terminal of ProxMenux Monitor it is replaced by an informational msgbox — that terminal cannot survive a self-update mid-flight, so the msgbox shows the canonical one-line installer (<code>bash -c \"$(wget -qLO - https://raw.githubusercontent.com/MacRimi/ProxMenux/main/install_proxmenux.sh)\"</code> for stable, or the equivalent <code>install_proxmenux_beta.sh</code> URL for beta) to run from SSH or console."
+    "body": "ProxMenux self-updates. When a new version is available, the next <code>menu</code> launch offers the update; accepting replaces utility files and configurations in place. No manual download needed. Stable users get stable releases; beta users get beta builds and are also offered new stable releases. The prompt shape depends on where <code>menu</code> runs: over SSH or the Proxmox console it is a classic yes / no dialog, and accepting applies the update immediately. Inside the WebSocket terminal of ProxMenux Monitor it is replaced by an informational msgbox — that terminal cannot survive a self-update mid-flight, so the msgbox shows the canonical one-line installer (<code>bash -c \"$(wget -qLO - https://raw.githubusercontent.com/MacRimi/ProxMenux/main/install_proxmenux.sh)\"</code> for stable, or the equivalent <code>install_proxmenux_beta.sh</code> URL for beta) to run from SSH or console."
   },
   "uninstall": {
     "heading": "Uninstalling",

web/messages/en/docs/introduction.json

@@ -21,7 +21,7 @@
     "intro": "ProxMenux has two components in the same source tree. The installer deploys both on the host: Scripts provides the terminal interface, and Monitor provides the web dashboard:",
     "scripts": {
       "title": "ProxMenux Scripts",
-      "body": "The original CLI/TUI you launch with <code>menu</code>. Nine functional areas covering post-install optimizations, VM and LXC creation, GPU and Coral TPU passthrough, disks, storage, network, security, utilities, plus a curated commands reference. Runs in any terminal — local, SSH or web."
+      "body": "The original CLI/TUI you launch with <code>menu</code>. Functional areas covering post-install optimizations, VM and LXC creation, GPU and Coral TPU passthrough, disks, storage, OCI apps, network, security, utilities, host backup and restore, Proxmox VE Helper Scripts, plus a curated commands reference. Runs in any terminal — local, SSH or web."
     },
     "monitor": {
       "title": "ProxMenux Monitor",
@@ -37,7 +37,7 @@
   },
   "scriptsSection": {
     "heading": "ProxMenux Scripts — what you get",
-    "intro": "Nine functional areas, each with its own menu inside <code>menu</code> and a detail page in the documentation. Click any card to jump straight to that section's overview.",
+    "intro": "The main functional areas, each with its own menu inside <code>menu</code> and a detail page in the documentation. Click any card to jump straight to that section's overview.",
     "items": [
       {
         "title": "Post-Install",

web/messages/en/docs/settings/beta-program.json

@@ -51,7 +51,7 @@
     "intro": "Both directions go through the same installer — they are <strong>not</strong> special-cased uninstall + reinstall flows. Each direction simply runs the channel's own installer, which is designed to be idempotent and safe to re-execute over an existing install. Practical consequences:",
     "items": [
       "Your existing config, ProxMenux Monitor login (<code>auth.json</code>), notification channels, post-install registry, custom thresholds — none of those are touched. The channel switch only swaps the script tree and the binary AppImage.",
-      "A Monitor that was active before the switch stays active after; one that was deactivated stays deactivated.",
+      "The installer restarts the Monitor service during the switch, so a Monitor you had deactivated runs again (it stays disabled at boot). Deactivate it again from Settings if needed.",
       "ProxMenux Monitor <code>auth.json</code>, API tokens and the JWT secret are preserved across channel changes. Sessions don't get logged out.",
       "You can flip channels as many times as you like — the dialog will accept it every time and rerun the installer. No restart of Proxmox is required.",
       "The channel switch installer replaces ProxMenux's own script tree, so it cannot run inside the Monitor's browser terminal (that PTY would be torn down mid-update and leave the dialog stranded). If you launch the option from there, the confirmation is replaced by an informational msgbox showing the canonical one-line installer for the target channel; run that command from an SSH session or the Proxmox host console."

web/messages/en/docs/settings/index.json

@@ -76,7 +76,7 @@
         "icon": "Trash2",
         "href": "/docs/settings/uninstall-proxmenux",
         "title": "Uninstall ProxMenux",
-        "description": "Remove ProxMenux and (optionally) its dependencies. Also restores /root/.bashrc and /etc/motd backups created at install time."
+        "description": "Remove ProxMenux and (optionally) its dependencies. Also restores /root/.bashrc and /etc/motd backups created by Post-Install."
       }
     ]
   },

web/messages/en/docs/settings/uninstall-proxmenux.json

@@ -12,7 +12,7 @@
   },
   "scopeWarn": {
     "title": "Affects the ProxMenux install only — not your VMs / CTs / storage",
-    "body": "Uninstalling ProxMenux removes the ProxMenux scripts, the menu launcher, the Monitor service and any backups ProxMenux took of system files when you installed it. <strong>It does not touch your VMs, containers, storage, network configuration, Fail2Ban, NVIDIA driver or anything else you installed via ProxMenux.</strong> Those stay as they are."
+    "body": "Uninstalling ProxMenux removes the ProxMenux scripts, the menu launcher, the Monitor service and restores the /root/.bashrc and /etc/motd backups that Post-Install took, if they exist. <strong>It does not touch your VMs, containers, storage, network configuration, Fail2Ban, NVIDIA driver or anything else you installed via ProxMenux.</strong> Those stay as they are."
   },
   "flow": {
     "heading": "The uninstall flow",