diff --git a/enhancements/20230905-automatically-evict-replicas-while-draining.md b/enhancements/20230905-automatically-evict-replicas-while-draining.md
index a0d03d4c61..ee2195ca91 100644
--- a/enhancements/20230905-automatically-evict-replicas-while-draining.md
+++ b/enhancements/20230905-automatically-evict-replicas-while-draining.md
@@ -191,13 +191,9 @@ Make changes so that:
   `replica.status.evictionRequested` to influence replica scheduling/deletion behavior (e.g. rebuild an extra replica
   to replace the evicting one or delete the evicting one once rebuilding is complete).
 - The node controller sets `replica.spec.evictionRequested = false` when:
-  - `spec.evictionRequested == false` on the replica's node, AND
-  - `spec.evictionRequested == false` on the replica's disk, AND
-  - `status.Unschedulable == false` on the associated Kubernetes node object, OR
-  - `status.Unschedulable == true` on the associated Kubernetes node object and the node drain policy is not
-    `block-for-eviction` or `block-for-eviction-if-contains-last-replica`, OR
-  - `status.Unschedulable == true` on the associated Kubernetes node object, the node drain policy is
-    `block-for-eviction-if-contains-last-replica`, and there is another PDB-protected replica.
+  - The user is not requesting eviction with `node.spec.evictionRequested == true` or
+    `disk.spec.evictionRequested == true`, AND
+  - The conditions aren't right for auto-eviction based on the node status and drain policy.
 - The node controller sets `status.autoEvicting = true` when a node has evicting replicas because of the new drain
   policies and `status.autoEvicting == false` when it does not. This provides a clue to the user (and the UI) while auto
   eviction is ongoing.