fix(lifecycle updated)

README.md

@@ -116,9 +116,9 @@ If you would like to sponsor an additional feature, [see this page](https://chec
 
 1. A monitor executes a check (HTTP / ping / port / hardware via Capture agent)
 2. The result is stored (success/failure + response time)
-3. The system evaluates recent checks to determine status (up/down)
-4. If failure threshold is reached, the monitor becomes "down"
-5. If it stays down, an incident is created automatically
+3. Recent check results are evaluated against the monitor's configured status change threshold
+4. If the monitor's status change threshold is met and the current status is not equal to the previous status, the monitor's state changes (e.g. `initializing`, `up`, `down`, `breached`)
+5. Upon a state change: an incident is either created or resolved, depending on the monitor's current status
 6. Notifications are triggered based on configuration
 
 ## Screenshots