diff --git a/documentation/release.md b/documentation/release.md
index 69ce32aff..5f08e8f5a 100644
--- a/documentation/release.md
+++ b/documentation/release.md
@@ -22,7 +22,7 @@ This guide is to describe how to make releases for the current repository.
 2. Go to the GitHub interface, in the [`Release` section](https://github.com/meilisearch/meilisearch/releases).
 
 3. Select the already drafted release or click on the `Draft a new release` button if you want to start a blank one, and fill the form with the appropriate information.
-⚠️ Publish on `main`
+⚠️ Publish on a specific commit defined by the team. Or publish on `main`, but ensure you do want all the PRs merged in your release.
 
 ⚙️ The CIs will be triggered to:
 - [Upload binaries](https://github.com/meilisearch/meilisearch/actions/workflows/publish-binaries.yml) to the associated GitHub release.
@@ -31,7 +31,7 @@ This guide is to describe how to make releases for the current repository.
 - [Move the `latest` git tag to the release commit](https://github.com/meilisearch/meilisearch/actions/workflows/latest-git-tag.yml).
 
 
-### 🔥 How to do a patch release for an hotfix
+### 🔥 How to do a patch release for a hotfix
 
 It happens some releases come with impactful bugs in production (e.g. indexation or search issues): we obviously don't wait for the next cycle to fix them and we release a patched version of Meilisearch.