From cbfe1ecd4ce877887ef095b7f697ab6e7bb6c4f1 Mon Sep 17 00:00:00 2001 From: Pulse Monitor Date: Thu, 4 Sep 2025 10:34:16 +0000 Subject: [PATCH] docs: remove time references from password recovery sections --- docs/SECURITY.md | 2 +- docs/TROUBLESHOOTING.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/SECURITY.md b/docs/SECURITY.md index a8ca8b76e..b0f9f7854 100644 --- a/docs/SECURITY.md +++ b/docs/SECURITY.md @@ -354,4 +354,4 @@ curl -X POST http://localhost:7655/api/security/reset-lockout \ **Can't login?** Check PULSE_AUTH_USER and PULSE_AUTH_PASS environment variables **API access denied?** Verify API_TOKEN is correct (use original token, not hash) **CORS errors?** Configure ALLOWED_ORIGINS for your domain -**Forgot password?** Start fresh - delete your Pulse data and restart (takes 2 minutes) \ No newline at end of file +**Forgot password?** Start fresh - delete your Pulse data and restart \ No newline at end of file diff --git a/docs/TROUBLESHOOTING.md b/docs/TROUBLESHOOTING.md index 12f83d395..58bed415e 100644 --- a/docs/TROUBLESHOOTING.md +++ b/docs/TROUBLESHOOTING.md @@ -8,7 +8,7 @@ **Solution: Start Fresh** -If you've forgotten your password, the recommended approach is to simply start fresh. Pulse is designed for quick setup - it takes just 2-3 minutes to be fully operational again. +If you've forgotten your password, the recommended approach is to simply start fresh. Pulse is designed for quick setup. **Why no password recovery?** - Adding recovery mechanisms creates security vulnerabilities @@ -173,7 +173,7 @@ systemctl status pulse 2>/dev/null || systemctl status pulse-backend #### Lost authentication See [Forgot Password / Lost Access](#forgot-password--lost-access) section above. -**Recommended approach**: Start fresh. Delete your Pulse data and restart - takes 2 minutes to set up again. +**Recommended approach**: Start fresh. Delete your Pulse data and restart. #### Corrupt configuration Restore from backup or delete config files to start fresh: