diff --git a/doc/source/operations/ubuntu-noble.rst b/doc/source/operations/ubuntu-noble.rst
index 4ac5847168..f0e89654db 100644
--- a/doc/source/operations/ubuntu-noble.rst
+++ b/doc/source/operations/ubuntu-noble.rst
@@ -79,15 +79,21 @@ To sync host packages:
 
 .. code-block:: console
 
-   kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-sync.yml -e stackhpc_pulp_sync_ubuntu_jammy=true -e stackhpc_pulp_sync_ubuntu_noble=true
-   kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-publish.yml
+   kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-sync.yml \
+       -e stackhpc_pulp_sync_ubuntu_jammy=true \
+       -e stackhpc_pulp_sync_ubuntu_noble=true
+   kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-publish.yml \
+       -e stackhpc_pulp_sync_ubuntu_jammy=true \
+       -e stackhpc_pulp_sync_ubuntu_noble=true
 
 Once the host package content has been tested in a test/staging environment, it
 may be promoted to production:
 
 .. code-block:: console
 
-   kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-promote-production.yml
+   kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-promote-production.yml \
+       -e stackhpc_pulp_sync_ubuntu_jammy=true \
+       -e stackhpc_pulp_sync_ubuntu_noble=true
 
 To sync container images:
 
@@ -165,7 +171,7 @@ Always back up the overcloud DB before starting:
 Potential issues
 ----------------
 
--  If the system uses OVS as a network driver, there's a change that kolla
+-  If the system uses OVS as a network driver, there's a chance that kolla
    services can struggle to find reply queues from RabbitMQ during the upgrade.
    Currently this could be observed when rolling reboot of controllers are done
    or deploying Ubuntu Noble based Kolla containers are deployed after all
@@ -236,7 +242,7 @@ Full procedure for one controller
 
       .. code-block:: console
 
-         kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-enter-maintenance.yml --limit <host>
+         kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-exit-maintenance.yml --limit <host>
 
    3. Make sure that everything is back in working condition before moving
       on to the next host:
@@ -321,7 +327,7 @@ Full procedure for one batch of hosts
 
       .. code-block:: console
 
-         kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-enter-maintenance.yml --limit <hosts>
+         kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/ceph-exit-maintenance.yml --limit <hosts>
 
    3. Make sure that everything is back in working condition before moving
       on to the next host: