diff --git a/content/modules/ROOT/pages/02-aap-smart-inventory.adoc b/content/modules/ROOT/pages/02-aap-smart-inventory.adoc
index d5fdd06..b23b82f 100644
--- a/content/modules/ROOT/pages/02-aap-smart-inventory.adoc
+++ b/content/modules/ROOT/pages/02-aap-smart-inventory.adoc
@@ -70,7 +70,7 @@ OpenShift environment.
 Ensure that you can ping those VMs
 within the **AAP** dashboard {aap_controller_web_url} as follows:
 
-. Login to the AAP Dashboard using the credentials above.
+. Login to the AAP Dashboard using the credentials provided in the `Setup` step.
 +
 . Navigate to Automation Execution -> Infrastructure -> Inventories
    * Select the `OpenShift Virtual Machines` Inventory
diff --git a/content/modules/ROOT/pages/04-vm-patching.adoc b/content/modules/ROOT/pages/04-vm-patching.adoc
index 5c1e8ac..5a55dbd 100644
--- a/content/modules/ROOT/pages/04-vm-patching.adoc
+++ b/content/modules/ROOT/pages/04-vm-patching.adoc
@@ -15,7 +15,15 @@ The following steps will guide you in creating the `update_security_packages.yml
 and the corresponding Ansible Playbook that will be called within your `Patch
 VMs` Job Template.
 
-NOTE: To ensure the virtual machines can access the required repositories for patch updates, the environment is configured to use the `redhatone.vm_management.rhsm_subscription` role for managing subscriptions. Additionally, a `Vault Credential` was created within Ansible Automation Platform to securely handle credentials during the automation process. These configurations have already been created for you and require no additional setup.
+
+[NOTE]
+====
+To ensure the virtual machines can access the required repositories for patch updates, the environment is configured to use the `redhatone.vm_management.rhsm_subscription` role for managing subscriptions. Additionally, a `Vault Credential` was created within Ansible Automation Platform to securely handle credentials during the automation process.
+
+Vault Credentials provide a significant security advantage: credentials are *one-way encrypted*, meaning they can be used within automation workflows but never exposed in plain text. This ensures sensitive information remains secure while simplifying credential management. This is a key benefit of Ansible Automation Platform that is often overlooked by ansible-core users.
+====
+
+
 
 === Create the `update_security_packages.yml` file.
 
diff --git a/content/modules/ROOT/pages/05-vm-hot-add.adoc b/content/modules/ROOT/pages/05-vm-hot-add.adoc
index 94fb5ec..4103fc6 100644
--- a/content/modules/ROOT/pages/05-vm-hot-add.adoc
+++ b/content/modules/ROOT/pages/05-vm-hot-add.adoc
@@ -138,7 +138,7 @@ managing resources across multiple VMs.
     - *cpu*: Specifies the number of CPU sockets for the VM (e.g., `2`).
     - *memory*: Defines the memory allocated to the VM, (e.g., `4Gi`).
 
-WARNING: Non-Legacy VMs are not part of this lab exercise and the Legacy Method is for informational purposes only.
+WARNING: Legacy VMs are not part of this lab exercise and the Legacy Method is for informational purposes only.
 
 == Create and Run the Hot-Plug Job Template
 . Within the AAP UI Dashboard, navigate to *Automation Execution → Templates*.