Clarifying section.

Author: roygara

articles/storage/elastic-san/elastic-san-delete.md

@@ -49,19 +49,20 @@ Copy the script from [here](https://github.com/Azure-Samples/azure-elastic-san/b
 
 You can delete your SAN by using the Azure portal, Azure PowerShell, or Azure CLI. If you delete a SAN or a volume group, the corresponding child resources are deleted along with it. The delete commands for each of the resource levels are below.
 
-
-The following commands delete your volumes. These commands use `ForceDelete false`, `-DeleteSnapshot false`, `--x-ms-force-delete false`, and `--x-ms-delete-snapshots false` parameters for PowerShell and CLI, respectively. If you set `ForceDelete` or `--x-ms-force-delete` to `true`, it causes volume deletion to succeed even if you have active iSCSI connections. If you set `-DeleteSnapshot` or `--x-ms-delete-snapshots` to `true`, it deletes all snapshots associated with the volume, and the volume itself.
-
 ### Delete a volume 
 
 # [PowerShell](#tab/azure-powershell)
 
+The following command deletes a volume. If you set `ForceDelete` to `true`, then your volume is deleted even when there are active iSCSI connections. If you set `-DeleteSnapshot` to `true`, it deletes all snapshots associated with the volume, and the volume itself.
+
 ```azurepowershell
 Remove-AzElasticSanVolume -ResourceGroupName $resourceGroupName -ElasticSanName $sanName -VolumeGroupName $volumeGroupName -Name $volumeName -ForceDelete false -DeleteSnapshot false
 ```
 
 # [Azure CLI](#tab/azure-cli)
 
+The following command deletes a volume. If you set `--x-ms-force-delete` to `true`, then your volume is deleted even when there are active iSCSI connections.. If you set `--x-ms-delete-snapshots` to `true`, it deletes all snapshots associated with the volume, and the volume itself.
+
 ```azurecli
 az elastic-san volume delete -e $sanName -g $resourceGroupName -v $volumeGroupName -n $volumeName --x-ms-force-delete false --x-ms-delete-snapshots false
 ```