Clarify step to be done for base-files

The branch is already created, only the build pipeline needs to be
triggered to create a merge request updating versions.

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

content/guides/apertis_release_process.md

@@ -101,7 +101,7 @@ After the completion of the **Release Branching** CI Jobs, a certain set of manu
   * Set the default development branch for all git projects.
   * Set the protection settings onto all `apertis/*` branches, which were unprotected in the initial release steps.
 * Update the [dashboard](https://gitlab.apertis.org/infrastructure/dashboard)'s channels to track the new release.
-* Manually branch the [base-files](https://gitlab.apertis.org/pkg/base-files/) package, after the new docker images have been built.
+* Trigger a build pipeline on the newly created branch of [base-files](https://gitlab.apertis.org/pkg/base-files/) package, after the new docker images have been built.
   * This step should automatically update the release specific attributes in the new package and auto propose the changes through a new merge request.
   * Validate the newly created pipeline ensuring that it generates the right set of changes with respect to the new release.
   * Validate the new package is built proper and pushed to OBS and the APT repositories.