diff --git a/docs/releasing_openttd.md b/docs/releasing_openttd.md
index 08c379dd81..ad16242076 100644
--- a/docs/releasing_openttd.md
+++ b/docs/releasing_openttd.md
@@ -38,8 +38,7 @@ This guide is for OpenTTD developers/maintainers, to release a new version of Op
 
 1. Go to https://github.com/OpenTTD/OpenTTD/releases/new and create a new tag matching the release number. For the body of the release, copy in the changelog. "Set as a pre-release" for a beta or RC.
 2. Wait for the OpenTTD release workflow to be complete.
-3. Merge the website PR. This will publish the release post.
-4. If this is a full release:
+3. If this is a full release:
    * for `Steam`: under Steamworks -> SteamPipe -> Builds, set the "testing" branch live on the "default" branch. This will request 2FA validation.
    * for `GOG`: under Builds, "Publish" the freshly uploaded builds to `Master`, `GOG-use only` and `Testing`.
    * for `Microsoft Store`: ask orudge to publish the new release.
@@ -50,4 +49,5 @@ For help and/or access to either or both, please contact TrueBrain.
 
 ## Step 4: Tell the world
 
-1. Make announcements on social media and store pages. You may need to coordinate with other developers who can make posts on TT-Forums, Twitter, Reddit, Fosstodon, Discord, Steam, GOG, Microsoft Store, etc.
+1. Merge the website PR. This will publish the release post.
+2. Make announcements on social media and store pages. You may need to coordinate with other developers who can make posts on TT-Forums, Twitter, Reddit, Fosstodon, Discord, Steam, GOG, Microsoft Store, etc.