diff --git a/src/content/docs/code-push/rollback.mdx b/src/content/docs/code-push/rollback.mdx
index d82b2c64..aabc21e4 100644
--- a/src/content/docs/code-push/rollback.mdx
+++ b/src/content/docs/code-push/rollback.mdx
@@ -17,21 +17,21 @@ In the [Shorebird Console](https://console.shorebird.dev/), navigate to the
 release that contains the patch you want to roll back. On the right side of the
 patch row, click the "more" icon (three vertical dots) and select "Rollback":
 
-![](https://github.com/user-attachments/assets/941fdc46-d0f3-463f-835f-5c8eb8a02e83)
+![The Shorebird Console showing a "roll back patch" button](https://github.com/user-attachments/assets/941fdc46-d0f3-463f-835f-5c8eb8a02e83)
 
 ## What happens when a patch is rolled back?
 
 Imagine we have a release with three patches:
 
-![](https://github.com/user-attachments/assets/ee5d4e2b-eca3-4318-99e9-038c0134bfff)
+![The Shorebird Console showing three patches, with patch 3 as the active patch](https://github.com/user-attachments/assets/ee5d4e2b-eca3-4318-99e9-038c0134bfff)
 
 When a user downloads this release from the store, Shorebird will see that patch
 3 is the latest available patch and download it.
 
 If we discover that there is a problem with patch 3, we can roll it back. The
-console will look like this after a rollback:
+Console will look like this after a rollback:
 
-![](https://github.com/user-attachments/assets/7ba4ff2c-5823-4c9f-a260-68ca6ce1e10a)
+![The Shorebird Console showing three patches, with patch 3 rolled back and patch 2 as the active patch](https://github.com/user-attachments/assets/7ba4ff2c-5823-4c9f-a260-68ca6ce1e10a)
 
 Users who download the app from the store will now get patch 2 instead of patch 3. Users who already had patch 3 installed will be downgraded to patch 2.