Merge pull request #101638 from cbippley/OCPBUGS-64614

OCPBUGS#64614 Formatting changes in updating a cluster by using the cli

Author: bergerhoffer

modules/update-upgrading-cli.adoc

@@ -113,7 +113,7 @@ endif::openshift-origin[]
 +
 [source,terminal]
 ----
-$ oc adm upgrade --to-latest=true <1>
+$ oc adm upgrade --to-latest=true
 ----
 
 ** To update to a specific version:
@@ -125,17 +125,17 @@ $ oc adm upgrade --to=<version> <1>
 <1> `<version>` is the update version that you obtained from the output of the
 `oc adm upgrade recommend` command.
 +
-.. If the cluster administrator evaluates the potential known risks and decides it is acceptable for the current cluster, then the administrator can waive the safety guards and proceed with the update by running the following command:
+[IMPORTANT]
+====
+When using `oc adm upgrade --help`, there is a listed option for `--force`. This is _heavily discouraged_, because using the `--force` option bypasses cluster-side guards, including release verification and precondition checks. Using `--force` does not guarantee a successful update. Bypassing guards puts the cluster at risk.
+====
++
+. If the cluster administrator evaluates the potential known risks and decides it is acceptable for the current cluster, then the administrator can waive the safety guards and proceed with the update by running the following command:
 +
 [source,terminal]
 ----
 $ oc adm upgrade --allow-not-recommended --to <version>
 ----
-+
-[IMPORTANT]
-====
-When using `oc adm upgrade --help`, there is a listed option for `--force`. This is *heavily discouraged*, as using the `--force` option bypasses cluster-side guards, including release verification and precondition checks. Using `--force` does not guarantee a successful update. Bypassing guards put the cluster at risk.
-====
 
 . Optional: Review the status of the Cluster Version Operator by running the following command:
 +