From fef2c3c12e0f83051e6ee4b656de3d4a45bc1b03 Mon Sep 17 00:00:00 2001
From: hermes <hermes@datacontroller.io>
Date: Thu, 20 Aug 2026 22:14:47 +0100
Subject: [PATCH] chore: li update

---
 content/feed/rollback-data-changes/index.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/content/feed/rollback-data-changes/index.md b/content/feed/rollback-data-changes/index.md
index 97d729c..62cca12 100644
--- a/content/feed/rollback-data-changes/index.md
+++ b/content/feed/rollback-data-changes/index.md
@@ -51,11 +51,13 @@ Full documentation is here: https://docs.datacontroller.io/rollback-data-changes
 <!--
 Source LinkedIn post:
 
-"Which submission introduced this value?" should never be a hard question to answer.
 
-Yet for many teams managing reference data, mappings, and regulatory adjustments in SAS®, a wrong approval means exactly that - an uncomfortable audit conversation, a forensic exercise, and a quiet hope that nobody upstream consumed the bad data.
 
-Data Controller now lets you ROLL BACK a table to a previous state.
+"Can we put it back the way it was?" should never be a hard question to answer.
+
+Yet for many teams managing reference data, mappings, and regulatory adjustments in SAS®, a wrong approval means exactly that — a forensic exercise, an uncomfortable audit conversation, and a quiet hope that nobody upstream consumed the bad data.
+
+Data Controller now lets you ROLL BACK a table to any previous state.
 
 Not by silently rewinding history - the one thing your auditor definitely does not want. Instead, the reversion is packaged as a brand NEW change that goes through the same review and approval as any other edit: