diff --git a/RELEASING.md b/RELEASING.md
index 24e6977..69b4a67 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -20,23 +20,24 @@ separate `v8` tag. Should automatically get `v8`, `v8.0`, `v8.0.0` as well as
 
 - [ ] Create/push a new patch tag for fixes/changes to `dagger-for-github`
 
-```console
-# Find the latest released patch https://github.com/dagger/dagger-for-github/releases
-# or via the `gh` CLI. Use that to figure out the NEXT_VERSION.
-gh release view --repo dagger/dagger-for-github --json tagName,publishedAt
+  ```console
+  # Find the latest released patch https://github.com/dagger/dagger-for-github/releases
+  # or via the `gh` CLI. Use that to figure out the NEXT_VERSION.
+  gh release view --repo dagger/dagger-for-github --json tagName,publishedAt
 
-NEXT_VERSION=vX.Y.Z # e.g. v1.2.3
+  NEXT_VERSION=vX.Y.Z # e.g. v1.2.3
 
-# Sign the tag, using the date as the comment, e.g. 2024-07-22
-git tag --sign -m $(date '+%Y-%m-%d') $NEXT_VERSION
-git push origin $NEXT_VERSION #shouldn't need to force since new tag
-```
+  # Sign the tag, using the date as the comment, e.g. 2024-07-22
+  git tag --sign -m $(date '+%Y-%m-%d') $NEXT_VERSION
+  git push origin $NEXT_VERSION #shouldn't need to force since new tag
+  ```
 
 - [ ] Create a new release from the patch tag (auto-fill release notes via the
       GitHub UI or via the `gh` CLI)
-- [ ] Submit PR to change the version mentioned in Dagger docs. See example [here](https://github.com/dagger/dagger/pull/9705/files)
 
-```console
-# --verify-tag will ensure the last tag creation step was done
-gh release create --generate-notes --verify-tag <NEXT_PATCH_VERSION>
-```
+  ```console
+  # --verify-tag will ensure the last tag creation step was done
+  gh release create --generate-notes --verify-tag <NEXT_PATCH_VERSION>
+  ```
+
+- [ ] Submit PR to change the version mentioned in Dagger docs. See example [here](https://github.com/dagger/dagger/pull/9705/files)