Doc bug in creating machines with ultra disks by using machine sets

Doc bug in creating machines with ultra disks by using machine sets
Here is the documentation link:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/storage/using-container-storage-interface-csi#machineset-creating-azure-ultra-disk_persistent-storage-csi-azure

In the above documentation:
  machine-set-name needs to be changed to "machine_set_name"
  node-name needs to be changed to "node_name"

Author: prithvipatil97

modules/machineset-creating-azure-ultra-disk.adoc

@@ -118,10 +118,10 @@ ifndef::cpmso[]
 +
 [source,terminal]
 ----
-$ oc edit machineset <machine-set-name>
+$ oc edit machineset <machine_set_name>
 ----
 +
-where `<machine-set-name>` is the machine set that you want to provision machines with ultra disks.
+where `<machine_set_name>` is the machine set that you want to provision machines with ultra disks.
 
 . Add the following lines in the positions indicated:
 +
@@ -162,7 +162,7 @@ endif::mapi[]
 +
 [source,terminal]
 ----
-$ oc create -f <machine-set-name>.yaml
+$ oc create -f <machine_set_name>.yaml
 ----
 endif::cpmso[]
 
@@ -300,10 +300,10 @@ The machines should be in the `Running` state.
 +
 [source,terminal]
 ----
-$ oc debug node/<node-name> -- chroot /host lsblk
+$ oc debug node/<node_name> -- chroot /host lsblk
 ----
 +
-In this command, `oc debug node/<node-name>` starts a debugging shell on the node `<node-name>` and passes a command with `--`. The passed command `chroot /host` provides access to the underlying host OS binaries, and `lsblk` shows the block devices that are attached to the host OS machine.
+In this command, `oc debug node/<node_name>` starts a debugging shell on the node `<node_name>` and passes a command with `--`. The passed command `chroot /host` provides access to the underlying host OS binaries, and `lsblk` shows the block devices that are attached to the host OS machine.
 
 .Next steps