Replace 'aura' by 'aurora'

aura was deprecated in favor of aurora.

I haven't checked if the Publish Release Candidate part is still relevant.

content/guides/apertis_release_process.md

@@ -93,7 +93,7 @@ The above example complete the *semi-automated* aspect of the **Release Branchin
 After the completion of the **Release Branching** CI Jobs, a certain set of manual steps need to be performed, which are outlined below.
 
 * Add a directory for the release to the LAVA NFS path at: `/srv/images/public/lava/nfs/` on host images.apertis.org. The LAVA test jobs pick the kernel and initrd image from the release's directory path. Refer to the README for details
-* Instantiate a *new timer to rotate images* for the new release (eg. On host `aura`, run command `systemctl enable --now rotate-images@v2019.timer`)
+* Instantiate a *new timer to rotate images* for the new release (eg. On host `aurora`, run command `systemctl enable --now rotate-images@v2019.timer`)
 * Update the [ci-package-builder](https://gitlab.apertis.org/infrastructure/ci-package-builder/) to target the next release
 * Update the [gitlab-rulez](https://gitlab.apertis.org/infrastructure/gitlab-rulez/) recipe to point to the new development release
   * Set the default development branch for all git projects
@@ -208,7 +208,7 @@ Some notes about the `Archive Rebuild` task
 
 ## Publish Release Candidate
 
-* Run the `copy-release` script on the images server (aura) to prepare the RC.
+* Run the `copy-release` script on the images server (`aurora`) to prepare the RC.
  * `copy-release -v 20201203.0116 v2021pre.0rc1`
  * `copy-release -v -i 20201203.0116 v221pre.0rc1`
  * First for the public images and then second for Internal images (-i option).