diff --git a/content/feed/rollback-data-changes/ctrl-z.jpeg b/content/feed/rollback-data-changes/ctrl-z.jpeg
new file mode 100644
index 0000000..25db45e
Binary files /dev/null and b/content/feed/rollback-data-changes/ctrl-z.jpeg differ
diff --git a/content/feed/rollback-data-changes/index.md b/content/feed/rollback-data-changes/index.md
index 62cca12..c60fb24 100644
--- a/content/feed/rollback-data-changes/index.md
+++ b/content/feed/rollback-data-changes/index.md
@@ -6,7 +6,7 @@ author: 'Data Controller'
 authorLink: https://www.linkedin.com/showcase/data-controller-for-sas
 tags:
   - Announcements
-previewImg: './rollback-trains-meme.jpeg'
+previewImg: './ctrl-z.jpeg'
 ---
 
 # Oops! Now You Can Roll Back Data Changes
@@ -15,6 +15,8 @@ Despite the MANY checks and guarantees in Data Controller for SAS®, sometimes i
 
 Thankfully, it is now possible to **roll back** data changes to a previous state.
 
+![Two trains colliding - the wrong data changes applied](rollback-trains-meme.jpeg)
+
 ## How it works in practice
 
 Behind the scenes, rollback is not a silent undo. It is a **first-class approval workflow** just like any other edit. When you choose to restore a previous version, the backend - via the [`%mp_stripdiffs`](https://core.sasjs.io/mp__stripdiffs_8sas.html) macro - reads the `MPE_AUDIT` table (or a custom `AUDIT_LIBDS` configured for the table) and computes every difference between the current state and the version you want to go back to.