feat: some more docs

Author: SoulKyu

docs/notificator-collaboration.md

@@ -13,80 +13,33 @@ No more "are you looking at this?" messages in Slack!
 ### User Authentication
 Everyone gets their own login. No more anonymous alert handling!
 
-![User Login](screenshots/user-login.png)
+![User Registration](../screenshots/user-registration.png)
+*Screenshot: Registration dialog with username/password fields*
+
+![User Login](../screenshots/user-login.png)
 *Screenshot: Login dialog with username/password fields*
 
 ### Alert Acknowledgments
 Click "Ack" on any alert to let your team know you're handling it. The alert gets marked with your name and timestamp.
 
-![Alert Acknowledgment](screenshots/alert-ack.png)
+![Alert Acknowledgment](../screenshots/alert-ack.png)
 *Screenshot: Alert with acknowledge button and "Acked by Bastien at 14:32" status*
 
 ### Comments on Alerts
 Add context to alerts! Leave notes about what you're investigating, what you found, or what actions you took.
 
-![Alert Comments](screenshots/alert-comments.png)
+![Alert Comments](../screenshots/alert-comments.png)
 *Screenshot: Alert with comment section showing conversation between team members*
 
-### Real-time Updates
-When someone acks an alert or adds a comment, everyone sees it instantly. No refresh needed!
-
-![Real-time Updates](screenshots/real-time-updates.png)
-*Screenshot: Alert status changing in real-time as someone else acknowledges it*
-
 ### Team Filters
 Filter alerts by acknowledgment status to quickly see what needs attention:
 - Show only unacknowledged alerts
 - Show only my acknowledged alerts
 - Show alerts with comments
 
-![Team Filters](screenshots/team-filters.png)
-*Screenshot: Filter dropdown with acknowledgment and comment options*
-
 ### Alert History
 See the full timeline of what happened with each alert - when it fired, who acknowledged it, what comments were added.
 
-![Alert History](screenshots/alert-history.png)
-*Screenshot: Alert detail view showing chronological history of actions*
-
-### 3. Create user accounts
-
-The first time someone connects, they can register a new account. After that, they just login with their username/password.
-
-![User Registration](screenshots/user-registration.png)
-*Screenshot: Registration form for new users*
-
-## How it works in practice
-
-### During an incident
-1. **Alert fires** - Everyone sees it immediately
-2. **Someone acknowledges** - "I'm on it!" (everyone else can relax)
-3. **Investigation starts** - Add comments as you dig in
-4. **Share findings** - "Found the issue, deploying fix"
-5. **Resolution** - "Fixed! Was a database connection leak"
-
-### Daily operations
-- **Morning standup**: Check acknowledged alerts from night shift
-- **Handoffs**: See what the previous shift was working on
-- **Knowledge sharing**: Comments become a searchable history
-
-## Best practices
-
-### Acknowledgment etiquette
-- **Ack quickly** when you start looking at an alert
-- **Add a comment** saying what you're investigating
-- **Update status** as you progress ("still investigating", "fix deployed", etc.)
-
-### Writing good comments
-- **Be specific**: "CPU spike on web-01" not just "investigating"
-- **Include actions**: "Restarted service, monitoring for 10 minutes"
-- **Share findings**: "Caused by memory leak in feature X"
-
-### Team workflow
-- **Ack before investigating** - prevents duplicate work
-- **Comment your findings** - helps others learn
-- **Don't unack others** - unless they ask you to take over
-
 ## Troubleshooting
 
 ### "Can't connect to backend"