diff --git a/Documentation/postmortems/v3.5-data-inconsistency.md b/Documentation/postmortems/v3.5-data-inconsistency.md
index 718097657..27e15500e 100644
--- a/Documentation/postmortems/v3.5-data-inconsistency.md
+++ b/Documentation/postmortems/v3.5-data-inconsistency.md
@@ -115,18 +115,18 @@ To reflect this action items should have assigned priority:
 * P1 - Important for long term success of the project. Blocks v3.6 release.
 * P2 - Stretch  goals that would be nice to have for v3.6, however should not be blocking.
 
-| Action Item                                                                         | Type     | Priority | Bug                                          |
-|-------------------------------------------------------------------------------------|----------|----------|----------------------------------------------|
-| etcd testing can reproduce historical data inconsistency issues                     | Prevent  | P0       | https://github.com/etcd-io/etcd/issues/14045 |
-| etcd detects data corruption by default                                             | Detect   | P0       | https://github.com/etcd-io/etcd/issues/14039 |
-| etcd testing is high quality, easy to maintain and expand                           | Prevent  | P1       | https://github.com/etcd-io/etcd/issues/13637 |
-| etcd apply code should be easy to understand and validate correctness               | Prevent  | P1       |                                              |
-| Critical etcd features are not abandoned when contributors move on                  | Prevent  | P1       | https://github.com/etcd-io/etcd/issues/13775 |
-| etcd is continuously qualified with failure injection                               | Prevent  | P1       |                                              |
-| etcd can reliably detect data corruption (hash is linearizable)                     | Detect   | P1       |                                              |
-| etcd checks consistency of snapshots sent between leader and followers              | Detect   | P1       | https://github.com/etcd-io/etcd/issues/13973 |
-| etcd recovery from data inconsistency procedures are documented and tested          | Mitigate | P1       |                                              |
-| etcd can imminently detect and recover from data corruption (implement Merkle root) | Mitigate | P2       | https://github.com/etcd-io/etcd/issues/13839 |
+| Action Item                                                                         | Type     | Priority | Bug                                          | Status |
+|-------------------------------------------------------------------------------------|----------|----------|----------------------------------------------|--------|
+| etcd testing can reproduce historical data inconsistency issues                     | Prevent  | P0       | https://github.com/etcd-io/etcd/issues/14045 | DONE   |
+| etcd detects data corruption by default                                             | Detect   | P0       | https://github.com/etcd-io/etcd/issues/14039 | DONE   |
+| etcd testing is high quality, easy to maintain and expand                           | Prevent  | P1       | https://github.com/etcd-io/etcd/issues/13637 |        |
+| etcd apply code should be easy to understand and validate correctness               | Prevent  | P1       |                                              |        |
+| Critical etcd features are not abandoned when contributors move on                  | Prevent  | P1       | https://github.com/etcd-io/etcd/issues/13775 | DONE   |
+| etcd is continuously qualified with failure injection                               | Prevent  | P1       | https://github.com/etcd-io/etcd/pull/14911   | DONE   |
+| etcd can reliably detect data corruption (hash is linearizable)                     | Detect   | P1       |                                              |        |
+| etcd checks consistency of snapshots sent between leader and followers              | Detect   | P1       | https://github.com/etcd-io/etcd/issues/13973 | DONE   |
+| etcd recovery from data inconsistency procedures are documented and tested          | Mitigate | P1       |                                              |        |
+| etcd can imminently detect and recover from data corruption (implement Merkle root) | Mitigate | P2       | https://github.com/etcd-io/etcd/issues/13839 |        |
 
 ## Timeline