Incorrect order of deployments and of current deployment before/after updates and rollbacks

[flozanorht]

From Yi He yih@redhat.com (RHEL for Edge QE engineer) on slack: https://redhat-internal.slack.com/archives/C022TDCV3FH/p1737452677286359?thread_ts=1736955677.870649&cid=C022TDCV3FH

I have reviewed the documents you listed there as
@micah
’s request, and I didn't find anything wrong there, looks good to me.
However, I may found some mistakes in other chapters:
in 6.i , there are two deployments listed, I think the second one "commit-httpd-v1" should be "commit-httpd-v2"
in 8.ii , should switch "commit-httpd-v3" and "commit-httpd-v2", the reason is that the vm is rollbacked from v3 to v2 but not reboot yet, so "commit-httpd-v2" should be the first deployment here, which means in next boot it will be the first and default deployment to boot. And as the vm is currently booted with "commit-httpd-v3", so the ● should be placed before it.

Have to check if this was already addressed alongside other fixes or not. Because I tested the course carefully for switching to HOL014, I think it's unlikely that I missed those. But checking means redoing all activities, from scratch, so not quick to verify.