diff --git a/alerts/openshift-virtualization-operator/GuestVCPUQueueHighWarning.md b/alerts/openshift-virtualization-operator/GuestVCPUQueueHighWarning.md
index 47e24e61..29074a06 100644
--- a/alerts/openshift-virtualization-operator/GuestVCPUQueueHighWarning.md
+++ b/alerts/openshift-virtualization-operator/GuestVCPUQueueHighWarning.md
@@ -9,7 +9,7 @@ uninterruptible threads. The run‑queue length is derived from
 
 ## Impact
 
-* Moderate CPU contention inside the guest. Latency may spike but workload still
+* Moderate CPU contention inside the guest VM. Latency might spike but workload still
 progresses.
 
 * An early signal that the VM might need additional vCPUs or that a short‑lived
@@ -32,7 +32,7 @@ process is causing bursts.
 
 4. **Verify vCPU allocation**
    ```bash
-   oc get vmi $VM -ojsonpath='{.spec.domain.cpu}'
+   $ oc get vmi $VM -ojsonpath='{.spec.domain.cpu}'
    ```
 
 ## Mitigation
@@ -40,11 +40,11 @@ process is causing bursts.
 * **Immediately:** Consider live-migrating the VM to a node under a lighter
 load,
 or throttle demanding processes.
-* **Short term:** Hot-plug or increase vCPU limit; tune application thread
+* **Short term:** Hot plug or increase vCPU limit; tune application thread
 pools.
 * **Long term:** Implement horizontal scaling (HPA/KEDA, VMReplicaSet);
 review placement rules.
 
 If you cannot resolve the issue, log in to the
-[Customer Portal](https://access.redhat.com) and open a support case,
+[Red Hat Customer Portal](https://access.redhat.com) and open a support case,
 attaching the artifacts gathered during the diagnosis procedure.
\ No newline at end of file