diff --git a/RELEASING.md b/RELEASING.md
index a8a6705f2..fe46b506a 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -3,17 +3,17 @@
 - [ ] Open gitk and review changes since last release.
 
 	- [ ] Print all public API changes:
-        `git diff $(git describe | sed 's/-.*//').. src/*.h`
+          `git diff $(git describe | sed 's/-.*//').. src/*.h`
 
     - [ ]  Document them in NEWS.
-        All API and API semantic changes should be clearly marked as API additions, API changes, or API deletions.
+           All API and API semantic changes should be clearly marked as API additions, API changes, or API deletions.
 
     - [ ] Document deprecations.
-        Ensure all new API / deprecations are in listed correctly in docs/harfbuzz-sections.txt.
-        If release added new API, add entry for new API index at the end of docs/harfbuzz-docs.xml.
+          Ensure all new API / deprecations are listed correctly in docs/harfbuzz-sections.txt.
+          If release added new API, add entry for new API index at the end of docs/harfbuzz-docs.xml.
 
-     If there's a backward-incompatible API change (including deletions for API used anywhere), that's a release blocker.
-     Do NOT release.
+          If there's a backward-incompatible API change (including deletions for API used anywhere), that's a release blocker.
+          Do NOT release.
 
 - [ ] Based on severity of changes, decide whether it's a minor or micro release number bump.
 
@@ -26,12 +26,16 @@
 - [ ] Do a `meson test -Cbuild` so it both checks the tests and updates hb-version.h (use `git diff` to see if is really updated).
 
 - [ ] Commit NEWS, meson.build, and src/hb-version.h, as well as any REPLACEME changes you made.
-        The commit message is simply the release number, e. g. "1.4.7"
+      The commit message is simply the release number, e. g. "1.4.7"
 
 - [ ] Do a `meson dist -Cbuild` that runs the tests against the latest committed changes.
-   If doesn't pass, something fishy is going on, reset the repo and start over.
+      If it does not pass, something fishy is going on, reset the repo and start over.
 
 - [ ] Tag the release and sign it: e.g. `git tag -s 1.4.7 -m 1.4.7`.
 	  Enter your GPG password.
 
 - [ ] Push the commit and tag out: `git push --follow-tags`.
+
+- [ ] Go to the github page and create a new release.
+      Make sure to select the correct tag and add a title and description.
+      The description should be the NEWS file additions.