docs: clarify update process for different deployment types

- Add clear ProxmoxVE LXC update instructions (just type 'update')
- Fix incorrect FAQ about UI updates (no longer possible)
- Explain why Pulse cannot self-update for security reasons
- Make it clear that most users run in LXC containers

README.md

@@ -177,10 +177,18 @@ See [Security Documentation](docs/SECURITY.md) for details.
 
 ## Updating
 
-### Automatic Updates
-Pulse checks for updates based on your configured channel (stable or RC). Updates are notified in the UI but must be installed manually for security.
+### Update Notifications
+Pulse checks for updates and displays notifications in the UI when new versions are available. For security reasons, updates must be installed manually using the appropriate method for your deployment.
 
-### Manual Update via Script
+### ProxmoxVE LXC Container
+If you installed Pulse using the ProxmoxVE Helper Script:
+```bash
+# Simply type 'update' in the LXC console
+update
+```
+The ProxmoxVE script handles everything automatically.
+
+### Manual Installation (systemd)
 ```bash
 # Update to latest stable
 curl -fsSL https://raw.githubusercontent.com/rcourtman/Pulse/main/install.sh | sudo bash

docs/FAQ.md

@@ -93,8 +93,12 @@ Yes, ensure WebSocket support is enabled
 ## Updates
 
 ### How to update?
-- **Docker**: Pull latest image, recreate container
-- **Manual**: Settings → System → Check for Updates
+- **ProxmoxVE LXC**: Type `update` in the LXC console
+- **Docker**: Pull latest image, recreate container  
+- **Manual/systemd**: Run the install script again: `curl -fsSL https://raw.githubusercontent.com/rcourtman/Pulse/main/install.sh | sudo bash`
+
+### Why can't I update from the UI?
+For security reasons, Pulse cannot self-update. The UI will notify you when updates are available and show the appropriate update command for your deployment type.
 
 ### Will updates break config?
 No, configuration is preserved