docs: update notification references to mention persistent retry

Author: m4r1k

README.md

@@ -38,7 +38,7 @@ Most UPS shutdown solutions are **single-system focused**. Eneru is designed for
 | Different systems need different commands | ✅ Per-server custom shutdown commands |
 | Hypervisors need graceful VM shutdown | ✅ Pre-shutdown actions (Proxmox, ESXi, XCP-ng, libvirt) |
 | Battery estimates are unreliable | ✅ Multi-vector shutdown triggers |
-| Network down during outage | ✅ Non-blocking notification architecture |
+| Network down during outage | ✅ Non-blocking notifications with persistent retry |
 
 ---
 
@@ -105,7 +105,7 @@ See the [full documentation](https://eneru.readthedocs.io/) for complete configu
 - **Multi-vector shutdown triggers** - Battery %, runtime, depletion rate, time on battery, FSD flag
 - **Orchestrated shutdown** - VMs, containers, remote servers, filesystems, local system
 - **100+ notification services** - Discord, Slack, Telegram, ntfy, Email via [Apprise](https://github.com/caronc/apprise/wiki)
-- **Non-blocking notifications** - Never delays critical shutdown operations
+- **Non-blocking notifications** - Persistent retry without delaying shutdown
 - **Power quality monitoring** - Voltage, AVR, bypass, and overload detection
 - **Dry-run mode** - Test your configuration safely
 

docs/index.md

@@ -23,7 +23,7 @@ Most UPS shutdown solutions are **single-system focused**. Eneru is designed for
 | Different systems need different commands | ✅ Per-server custom shutdown commands |
 | Hypervisors need graceful VM shutdown | ✅ Pre-shutdown actions (Proxmox, ESXi, XCP-ng, libvirt) |
 | Battery estimates are unreliable | ✅ Multi-vector shutdown triggers |
-| Network down during outage might block/slow down shutdown | ✅ Non-blocking notification architecture |
+| Network down during outage might block/slow down shutdown | ✅ Non-blocking notifications with persistent retry |
 
 ---
 
@@ -74,7 +74,7 @@ All components are optional and independently configurable:
 ### Real-Time Notifications (via Apprise)
 
 - **100+ Notification Services:** Discord, Slack, Telegram, ntfy, Pushover, Email, and [many more](https://github.com/caronc/apprise/wiki)
-- **Non-Blocking Architecture:** Notifications never delay critical shutdown operations
+- **Non-Blocking with Persistent Retry:** Notifications never delay shutdown, retried until delivered
 - **Power Event Alerts:** Color-coded notifications for all power events
 - **Service Lifecycle:** Notifications when service starts/stops