HDDS-13229. [Doc] Fix incorrect CLI argument order in OM upgrade docs

hadoop-hdds/docs/content/design/omprepare.md

@@ -42,19 +42,20 @@ author: Aravindan Vijayan
 # Usage
 
 ## How do you prepare an Ozone manager quorum
-    ozone admin om -id=<om-sevice-id> prepare
-
+
+    ozone admin om prepare -id=<om-sevice-id>
+
 This leaves the Ozone manager in a state where it cannot accept new writes.
 
 ## How do you cancel a "prepared" Ozone manager quorum
 
 In the case of a cancelled upgrade, the OM can be brought out off the
 prepared state by using the following command.
- 
-    ozone admin om -id=<om-sevice-id> cancelprepare
+
+    ozone admin om cancelprepare -id=<om-sevice-id>
 
 # Link
 
   https://issues.apache.org/jira/secure/attachment/13015491/OM%20Prepare%20Upgrade.pdf
 
-  https://issues.apache.org/jira/secure/attachment/13015411/OM%20Prepare%20Upgrade%2CDowngrade.jpg
+  https://issues.apache.org/jira/secure/attachment/13015411/OM%20Prepare%20Upgrade%2CDowngrade.jpg

hadoop-hdds/docs/content/design/upgrade-dev-primer.md

@@ -84,12 +84,12 @@ An action run once during finalization of layout version (feature). This action
 Used to flush all transactions to disk, take a DB snapshot, and purge the logs, leaving Ratis in a clean state without unapplied log entries. This prepares the OM for upgrades/downgrades so that no request in the log is applied to the database in the old version of the code in one OM, and the new version of the code in another OM.
 
 To prepare an OM quorum, run
- 
-    ozone admin om -id=<om-sevice-id> prepare
+
+    ozone admin om prepare -id=<om-sevice-id>
 
 To cancel preparation of an OM quorum, run
- 
-    ozone admin om -id=<om-sevice-id> cancelprepare
+
+    ozone admin om cancelprepare -id=<om-sevice-id>
 
 
 ## When do you bring in a change as a Layout feature?