Simplify status to prevent them from being falsely exhaustive

Author: Ndpnt

content/collections/reference/status.md

@@ -3,21 +3,10 @@ title: Status
 weight: 5
 ---
 
-# Collection Status
+# Collection status
 
 This reference documentation outlines the different status levels that a collection can have within the system. Understanding these statuses is crucial for users to assess a collection's reliability, maintenance level, and current operational state.
 
-## Status Overview
-
-| Status | Tracking | Engine and infrastructure updates | Roles activity | Quality |
-|:-----------------|:---------|:------------|:-----------|:------------|
-| `Active` | ✅ Operational | ✅ All | ✅ All | ✅ Stable |
-| `Maintenance requested` | ⚠️ May have interupts | ⚠️ Critical only | ⚠️ Admin only | ⚠️ Decreasing |
-| `Abandoned` | ⚠️ Unknown | ❌ None | ❌ None | ❌ Poor |
-| `Terminated` | ❌ Stopped | N/A | N/A | Depends on maintenance level during active period |
-
-## Detailed status descriptions
-
 ### `Active`
 
 - The optimal operational state for a collection.
@@ -30,18 +19,6 @@ This reference documentation outlines the different status levels that a collect
 
 ---
 
-### `Maintenance requested`
-
-- Indicates a collection that needs attention but remains functional.
-
-- Regular record saving continues, however, the collection shows signs of strain with limited or no updates to terms declarations. The number of tracked terms is declining, and tracking quality is decreasing.
-
-- Technical maintenance continues but at a reduced level, critical dependency updates are applied, though often with delays. The collection maintains access to essential engine features and infrastructure updates to ensure basic functionality, but may not receive all new feature improvements.
-
-- Some roles are inactive; while hosts and administrators remain partially active, curators and maintainers have become inactive.
-
----
-
 ### `Abandoned`
 
 - Collection may be functional but shows clear signs of neglect.