Fixed Admonitions

deployments/platforms/virtualization/proxmox/Detecting and Removing Orphaned VM Disks.md

@@ -34,32 +34,32 @@ Adjust the storage ID and volume group names as needed for your environment.
 ## Safety Requirements
 
 !!! danger "Never delete based on the Storage UI alone"
-The Proxmox storage UI may show a volume as belonging to a VM because its name follows the pattern `vm-<vmid>-disk-<n>`. That does not prove the disk is currently attached to the VM.
+    The Proxmox storage UI may show a volume as belonging to a VM because its name follows the pattern `vm-<vmid>-disk-<n>`. That does not prove the disk is currently attached to the VM.
 
-```
+    ```
-Always verify against VM configuration files and active QEMU processes before deleting.
+    Always verify against VM configuration files and active QEMU processes before deleting.
-```
+    ```
 
 !!! warning "Run the audit before running any cleanup commands"
-The audit scripts in this document are read-only. The cleanup commands are destructive. Do not run cleanup commands until the audit output has been reviewed.
+    The audit scripts in this document are read-only. The cleanup commands are destructive. Do not run cleanup commands until the audit output has been reviewed.
 
 !!! warning "Snapshot volumes require extra caution"
-Volumes named like the following may be part of a snapshot chain:
+    Volumes named like the following may be part of a snapshot chain:
 
-````
+    ````
-```text
+    ```text
-snap_vm-<vmid>-disk-<n>_<snapshot-name>
+    snap_vm-<vmid>-disk-<n>_<snapshot-name>
-```
+    ```
 
-Do not remove snapshot volumes manually unless you have verified that the VM and snapshot are no longer known to Proxmox, no backing chain references them, and no QEMU process has them open.
+    Do not remove snapshot volumes manually unless you have verified that the VM and snapshot are no longer known to Proxmox, no backing chain references them, and no QEMU process has them open.
-````
+    ````
 
 !!! note "Shared storage does not mean shared config"
-In some cluster layouts, each node may only show VM config files for VMs assigned to that node. Therefore, an audit run from only one node can falsely report disks from other nodes as orphaned.
+    In some cluster layouts, each node may only show VM config files for VMs assigned to that node. Therefore, an audit run from only one node can falsely report disks from other nodes as orphaned.
 
-```
+    ```
-Run the confirmation script on every node in the cluster.
+    Run the confirmation script on every node in the cluster.
-```
+    ```
 
 ---
 
@@ -235,11 +235,11 @@ Interpretation:
 | `open=no`        | No process on this node has the volume open. Still confirm across all nodes.                            |
 
 !!! warning "Local reference analysis is not enough"
-If a VM runs on another cluster node, its config may not appear on the node where you ran the audit. This can make valid disks look orphaned.
+    If a VM runs on another cluster node, its config may not appear on the node where you ran the audit. This can make valid disks look orphaned.
 
-```
+    ```
-Continue to Phase 3 before deleting anything.
+    Continue to Phase 3 before deleting anything.
-```
+    ```
 
 ---
 
@@ -432,10 +432,10 @@ qemu-img info ...    no unexpected backing file dependency
 ```
 
 !!! danger "Stop if grep finds a reference"
-If the candidate volume appears in any `/etc/pve/qemu-server/*.conf` file, do not delete it.
+    If the candidate volume appears in any `/etc/pve/qemu-server/*.conf` file, do not delete it.
 
 !!! danger "Stop if lsof finds a process"
-If `lsof` shows the volume is open, do not delete it.
+    If `lsof` shows the volume is open, do not delete it.
 
 ---
 
@@ -493,7 +493,7 @@ vgs vg_proxmox_iscsi
 ```
 
 !!! warning "Prefer pvesm free over lvremove"
-`pvesm free` lets Proxmox remove the volume through its storage abstraction. Use direct `lvremove` only when Proxmox refuses and the orphan status is already proven.
+    `pvesm free` lets Proxmox remove the volume through its storage abstraction. Use direct `lvremove` only when Proxmox refuses and the orphan status is already proven.
 
 ---
 
@@ -568,7 +568,7 @@ Only consider manual removal if:
 * and Proxmox cannot delete it normally.
 
 !!! danger "Do not manually delete active snapshot-chain volumes"
-Deleting an active snapshot backing volume can corrupt the VM disk chain.
+    Deleting an active snapshot backing volume can corrupt the VM disk chain.
 
 ---