diff --git a/docs/dev-proc/standard-release-process.md b/docs/dev-proc/standard-release-process.md
index dac684528a..034e1b95bf 100644
--- a/docs/dev-proc/standard-release-process.md
+++ b/docs/dev-proc/standard-release-process.md
@@ -9,17 +9,20 @@ should be maintained in that way.
 
 ## Process steps
 
-1. Checkout new branch `<platform>_rel_vX.Y.Z` from recent commit on `dasharo` -
-   to understand versioning scheme please read [Versioning](versioning.md)
-   section
-2. Merge current platform development branches to `<platform>_rel_vX.Y.Z`
-3. (Optional) Create a release candidate by tagging `<platform>_vX.Y.Z-rcN`
-4. Run platform regression test suite
-5. Fix all required issues and repeat from point 3 until fixed - this doesn't
-   mean all tests pass, this mean that approved set passed
-6. If results are accepted merge it to `dasharo` branch
-7. Add tag, which should trigger CI and publish binaries. Tag should be
-   annotated and signed. For example:
+1. Checkout new branch `<platform>_rel_vX.Y.Z-rcN` from recent commit on
+   `dasharo` - to understand versioning scheme please read
+   [Versioning](versioning.md) section
+2. Merge current platform development/bugfix branches to
+   `<platform>_rel_vX.Y.Z-rcN`.
+3. Merge `<platform>_rel_vX.Y.Z-rcN` branch it to `dasharo` branch
+4. Change the CONFIG_LOCALVERSION in coreboot configs appropriately and create
+   a release candidate by tagging `<platform>_vX.Y.Z-rcN`
+5. Run platform regression test suite.
+6. If all required tests passed, go to 8.
+7. Fix all required issues and repeat from point 1 until fixed.
+8. Change the CONFIG_LOCALVERSION in coreboot configs appropriately and add a
+   tag, which should trigger CI and publish binaries. Tag should be annotated,
+   signed and placed on the `dasharo` branch. For example:
 
     ```bash
     git tag -a -s -m "<platform>_vX.Y.Z" <platform>_vX.Y.Z