OCP 4.16: update for machineset

Author: alishaIBM

modules/machineset-manually-scaling.adoc

@@ -23,7 +23,7 @@ This guidance is relevant to fully automated, installer-provisioned infrastructu
 +
 [source,terminal]
 ----
-$ oc get machinesets -n openshift-machine-api
+$ oc get machinesets.machine.openshift.io -n openshift-machine-api
 ----
 +
 The compute machine sets are listed in the form of `<clusterid>-worker-<aws-region-az>`.
@@ -32,28 +32,28 @@ The compute machine sets are listed in the form of `<clusterid>-worker-<aws-regi
 +
 [source,terminal]
 ----
-$ oc get machine -n openshift-machine-api
+$ oc get machines.machine.openshift.io -n openshift-machine-api
 ----
 
 . Set the annotation on the compute machine that you want to delete by running the following command:
 +
 [source,terminal]
 ----
-$ oc annotate machine/<machine_name> -n openshift-machine-api machine.openshift.io/delete-machine="true"
+$ oc annotate machines.machine.openshift.io/<machine_name> -n openshift-machine-api machine.openshift.io/delete-machine="true"
 ----
 
 . Scale the compute machine set by running one of the following commands:
 +
 [source,terminal]
 ----
-$ oc scale --replicas=2 machineset <machineset> -n openshift-machine-api
+$ oc scale --replicas=2 machinesets.machine.openshift.io <machineset> -n openshift-machine-api
 ----
 +
 Or:
 +
 [source,terminal]
 ----
-$ oc edit machineset <machineset> -n openshift-machine-api
+$ oc edit machinesets.machine.openshift.io <machineset> -n openshift-machine-api
 ----
 +
 [TIP]
@@ -87,5 +87,5 @@ You can skip draining the node by annotating `machine.openshift.io/exclude-node-
 +
 [source,terminal]
 ----
-$ oc get machines
+$ oc get machines.machine.openshift.io
 ----