diff --git a/src/compiler/revert-button.png b/src/compiler/revert-button.png
deleted file mode 100644
index 7868a5335..000000000
Binary files a/src/compiler/revert-button.png and /dev/null differ
diff --git a/src/compiler/reviews.md b/src/compiler/reviews.md
index d43ac16a8..0c64b7fec 100644
--- a/src/compiler/reviews.md
+++ b/src/compiler/reviews.md
@@ -312,17 +312,16 @@ members pointing to this PR, or it's simply obvious to everyone involved). Only
 certainty if the issue is particularly critical or urgent to fix.
 
 #### Creating reverts
-The easiest method for creating a revert is to use the "Revert" button on Github. This appears
-next to the "bors merged commit abcd" message on a pull request, and creates a new pull request.
-
-![Location of the "Revert" button](revert-button.png)
-
-Alternatively, a revert commit can be created using the git CLI and then uploaded as a pull request:
+A revert commit can be created using the git CLI and then uploaded as a pull request:
 
 ```terminal
-$ git revert -m 1 62d5bee
+$ git revert -m 1 $COMMIT_HASH
 ```
 
+where `$COMMIT_HASH` can be found next to the merged status message:
+
+![merged commit hash](./reviews/merged-commit-hash.png)
+
 Don't rely *only* on the default commit title and message created by git. Instead, title the revert
 commit meaningfully, and link to the relevant PR that introduced the regression. Link to the
 specific PR that is being fully or partially reverted. Link to relevant issues and discussions.
diff --git a/src/compiler/reviews/merged-commit-hash.png b/src/compiler/reviews/merged-commit-hash.png
new file mode 100644
index 000000000..eed5545af
Binary files /dev/null and b/src/compiler/reviews/merged-commit-hash.png differ