Merge pull request #54301 from sheriff-rh/issues-49547

GH#49547 updating oc adm upgrade command

Author: mburke5678

modules/update-upgrading-cli.adoc

@@ -76,18 +76,18 @@ VERSION IMAGE
 4.10.13 quay.io/openshift-release-dev/ocp-release@sha256:4f516616baed3cf84585e753359f7ef2153ae139c2e80e0191902fbd073c4143
 ----
 
-. Based on your organization requirements, set the upgrade channel to `stable-4.10`, `fast-4.10`, or `eus-4.10`:
+. Based on your organization requirements, set the upgrade channel to `stable-{product-version}`, `fast-{product-version}`, or `eus-{product-version}`:
 +
 [source,terminal]
 ----
 $ oc adm upgrade channel <channel>
 ----
 +
-For example, to set the channel to `stable-4.10`:
+For example, to set the channel to `stable-{product-version}`:
 +
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
-$ oc adm upgrade channel stable-4.10
+$ oc adm upgrade channel stable-{product-version}
 ----
 +
 [IMPORTANT]
@@ -120,15 +120,15 @@ $ oc get clusterversion -o json|jq ".items[0].spec"
 ----
 +
 .Example output
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
 {
-  "channel": "stable-4.10",
+  "channel": "stable-{product-version}",
   "clusterID": "990f7ab8-109b-4c95-8480-2bd1deec55ff",
   "desiredUpdate": {
     "force": false,
     "image": "quay.io/openshift-release-dev/ocp-release@sha256:9c5f0df8b192a0d7b46cd5f6a4da2289c155fd5302dec7954f8f06c878160b8b",
-    "version": "4.10.13" <1>
+    "version": "<version>" <1>
   }
 }
 ----
@@ -181,10 +181,10 @@ $ oc get clusterversion
 ----
 +
 .Example output
-[source,terminal]
+[source,terminal,subs="attributes+"]
 ----
 NAME      VERSION     AVAILABLE   PROGRESSING   SINCE     STATUS
-version   4.10.13      True        False         2m        Cluster version is 4.10.13
+version   {product-version}      True        False         2m        Cluster version is {product-version}
 ----
 
 . If you are upgrading your cluster to the next minor version, like version 4.y to 4.(y+1), it is recommended to confirm your nodes are upgraded before deploying workloads that rely on a new feature: