build suffix cleanups

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

content/guides/apertis_release_process.md

@@ -229,7 +229,6 @@ those steps specific for stable point releases.
 
 Launch `fold-security-update-branches` script from the *apertis-infrastructure/release-scripts/gitlab/*, which automates many of the steps in a *Stable Point Release Preparation*
 
-* Increment the *Build Suffix* in the Project configuration for each repository relevant to the release. See section **Build Suffix** for more details
 * List the packages in the `:security`, `:updates` and other similar repositories
 * Fast Forward Merge `--ff-only` the respective security and updates branches on Git. For example, `apertis/v2020-security` and `apertis/v2020-updates` should be merged back to `apertis/v2020`. Note: Not able to perform a fast forward merge means something got broken and needs to be investigated and fixed.
 * Poke the pipeline and ensure that all the new packages (from the merged back changes to `apertis/v2020`) get built on OBS and land into the main repository.
@@ -449,5 +448,5 @@ Host images.apertis.org
   * Fork the OBS projects, copying packages and metadata
   * Clone and republish the OBS binary repositories
   * Restart the OBS schedulers
-* Update build suffix on OBS Project configuration (eg. `bv2021.0b<B_CNT>`, `bv2020dev0b<B_CNT>`). Please refer to section **Build Suffix** for more details about it
+* Update build suffix on OBS Project configuration (eg. `bv2021.0b<B_CNT>`, `bv2020dev0b<B_CNT>`). Please refer to section **Build Suffix** and **Stable Build Suffix** for more details about it