changes

docs/v2.0/bridge.md

@@ -11,6 +11,14 @@ The regular Linux bridge is recommended for most installations. The Linux Bridge
 
 Below are the instructions to configure Netplan, whether using the Linux Bridge or Bifrost XDP bridge:
 
+```{note}
+The Network Mode page in the LibreQoS web UI now inspects the current Netplan files, offers eligible non-management interfaces in dropdowns, stages managed `libreqos.yaml` changes for Linux bridge and single-interface modes, applies them with a timed LibreQoS rollback window, and lets you confirm or revert the pending change. You can also restore the previous managed backup from that page. XDP bridge mode remains a manual Netplan workflow.
+```
+
+```{note}
+If a timed Netplan change briefly interrupts your browser session, return to the Network Mode page after connectivity comes back. LibreQoS will resume the pending confirm or revert flow from that page automatically.
+```
+
 ## Option A: Netplan config for a regular Linux bridge (Recommended)
 
 Ubuntu Server uses NetPlan, which uses .yaml files in /etc/netplan to determine interface settings.
@@ -26,11 +34,11 @@ Assuming your shaping interfaces are ens19 and ens20, here is what your file wou
 network:
     ethernets:
         ens19:
-            dhcp4: no
-            dhcp6: no
+            dhcp4: false
+            dhcp6: false
         ens20:
-            dhcp4: no
-            dhcp6: no
+            dhcp4: false
+            dhcp6: false
     bridges:
         br0:
             interfaces:
@@ -42,7 +50,7 @@ network:
 Please be sure to replace ens19 and ens20 in the example above with the correct shaping interfaces. The order of the interfaces does not matter for this section.
 ```
 
-By setting `dhcp4: no` and `dhcp6: no`, the shaping interfaces will be brought up as part of the normal boot cycle, despite not having IP addresses assigned.
+By setting `dhcp4: false` and `dhcp6: false`, the shaping interfaces will be brought up as part of the normal boot cycle, despite not having IP addresses assigned.
 
 Then run
 
@@ -66,18 +74,18 @@ Assuming your shaping interfaces are ens19 and ens20, here is what your file wou
 network:
     ethernets:
         ens19:
-            dhcp4: no
-            dhcp6: no
+            dhcp4: false
+            dhcp6: false
         ens20:
-            dhcp4: no
-            dhcp6: no
+            dhcp4: false
+            dhcp6: false
     version: 2
 ```
 ```{note}
 Please be sure to replace ens19 and ens20 in the example above with the correct shaping interfaces. The order of the interfaces does not matter for this section.
 ```
 
-By setting `dhcp4: no` and `dhcp6: no`, the shaping interfaces will be brought up as part of the normal boot cycle, despite not having IP addresses assigned.
+By setting `dhcp4: false` and `dhcp6: false`, the shaping interfaces will be brought up as part of the normal boot cycle, despite not having IP addresses assigned.
 
 Then run
 

docs/v2.0/insight.md

@@ -119,13 +119,13 @@ Operational notes:
 
 ### Mapped circuit limits and license state
 
-`ShapedDevices.csv` can contain unlimited entries. In current v2.0 builds, admission into active shaping state depends on valid Insight license state.
+`ShapedDevices.csv` can contain unlimited entries. In current v2.0 builds, admission into active shaping state depends on valid entitled license/grant state.
 
-Without a valid Insight subscription/license, LibreQoS admits only the first 1000 valid mapped circuits into active shaping state. Additional valid mapped circuits remain outside active shaping until valid Insight licensing is restored.
+Without a valid Insight or Local license/grant state, LibreQoS admits only the first 1000 valid mapped circuits into active shaping state. Additional valid mapped circuits remain outside active shaping until valid entitled licensing is restored.
 
-A valid Insight subscription/license enables mapped-circuit counts above the default 1000 limit.
+A valid entitled license/grant state enables mapped-circuit counts above the default 1000 limit.
 
-The default 1000-limit behavior applies when Insight is:
+The default 1000-limit behavior applies when license/grant state is:
 - missing
 - expired
 - otherwise invalid
@@ -139,6 +139,6 @@ When the limit is reached, operators will typically see:
   - `Bakery mapped circuit cap enforced`
 
 When this occurs, check:
-1. Insight license status in the UI.
+1. License status in the `License & Services` page.
 2. `journalctl -u lqosd` for requested/allowed/dropped mapped counts.
-3. Whether your node is operating at the default 1000 mapped-circuit limit because the current Insight/license state is invalid.
+3. Whether your node is operating at the default 1000 mapped-circuit limit because the current license/grant state is invalid.

docs/v2.0/recipes-proxmox-vm.md

@@ -138,11 +138,11 @@ network:
       nameservers:
         addresses: [1.1.1.1, 8.8.8.8]
     ens19:
-      dhcp4: no
-      dhcp6: no
+      dhcp4: false
+      dhcp6: false
     ens20:
-      dhcp4: no
-      dhcp6: no
+      dhcp4: false
+      dhcp6: false
 ```
 
 Then configure bridge behavior per [Configure Shaping Bridge](bridge.md).

docs/v2.0/troubleshooting.md

@@ -276,9 +276,9 @@ If logs mention messages like:
 - `Mapped circuit limit reached`
 - `Bakery mapped circuit cap enforced`
 
-`ShapedDevices.csv` can contain unlimited entries, but without a valid Insight subscription/license LibreQoS admits only the first 1000 valid mapped circuits into active shaping state.
+`ShapedDevices.csv` can contain unlimited entries, but without a valid Insight or Local license/grant state LibreQoS admits only the first 1000 valid mapped circuits into active shaping state.
 
-The default 1000 mapped-circuit limit applies when Insight is:
+The default 1000 mapped-circuit limit applies when license/grant state is:
 - missing
 - expired
 - otherwise invalid
@@ -291,7 +291,7 @@ Typical operator-visible symptoms:
 - partial shaping, with circuits beyond the active limit left outside shaping state
 
 Recommended checks:
-1. Confirm Insight/license status in the UI.
+1. Confirm license status in the `License & Services` page.
 2. Review `lqosd` logs for requested/allowed/dropped counts.
 3. Reduce mapped circuit count (short term) or update licensing/limits (long term).
 

docs/v2.0/update.md

@@ -7,7 +7,7 @@ If you use the XDP bridge, traffic will briefly stop passing through the bridge
 ## If you installed the .deb
 
 ```{important}
-Starting in v2.0, mapped-circuit ingest depends on valid Insight license state. Without a valid Insight subscription/license, LibreQoS reads only the first 1000 valid mapped circuits into active shaping state. This includes expired or otherwise invalid local grant/license state. See [Insight Licensing Behavior](insight.md#mapped-circuit-limits-and-license-state) and [Troubleshooting](troubleshooting.md).
+Starting in v2.0, mapped-circuit ingest depends on valid entitled license/grant state. Without a valid Insight or Local license/grant state, LibreQoS reads only the first 1000 valid mapped circuits into active shaping state. This includes expired or otherwise invalid local grant/license state. See [Insight Licensing Behavior](insight.md#mapped-circuit-limits-and-license-state) and [Troubleshooting](troubleshooting.md).
 ```
 
 Run: