[OSDOCS-11101]: Update example OCP version in HCP docs

Author: lahinson

modules/hcp-aws-hc-ext-dns.adoc

@@ -64,7 +64,7 @@ $ hcp create cluster aws \
 <5> Specify the public hosted zone that the service consumer owns, for example, `service-consumer-domain.com`.
 <6> Specify the node replica count, for example, `2`.
 <7> Specify the path to your pull secret file.
-<8> Specify the supported {ocp-short} version that you want to use, for example, `4.14.0-x86_64`.
+<8> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`.
 <9> Specify the public hosted zone that the service provider owns, for example, `service-provider-domain.com`.
 <10> Set as `PublicAndPrivate`. You can use external DNS with `Public` or `PublicAndPrivate` configurations only.
 <11> Specify the path to your {aws-short} STS credentials file, for example, `/home/user/sts-creds/sts-creds.json`.

modules/hcp-bm-hc-mirror.adoc

@@ -52,4 +52,4 @@ $ hcp create cluster agent \
 <6> Specify the `icsp.yaml` file that defines ICSP and your mirror registries.
 <7> Specify the path to your SSH public key. The default file path is `~/.ssh/id_rsa.pub`.
 <8> Specify your hosted cluster namespace.
-<9> Specify the supported {product-title} version that you want to use, for example, `4.14.0-x86_64`. If you are using a disconnected environment, replace `<ocp_release_image>` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_.
+<9> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`. If you are using a disconnected environment, replace `<ocp_release_image>` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_.

modules/hcp-bm-hc.adoc

@@ -55,7 +55,7 @@ $ hcp create cluster agent \
 <7> Specify the path to your SSH public key. The default file path is `~/.ssh/id_rsa.pub`.
 <8> Specify your hosted cluster namespace.
 <9> The default value for the control plane availability policy is `HighlyAvailable`.
-<10> Specify the supported {product-title} version that you want to use, for example, `4.14.0-x86_64`. If you are using a disconnected environment, replace `<ocp_release_image>` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_.
+<10> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`. If you are using a disconnected environment, replace `<ocp_release_image>` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_.
 
 +
 . After a few moments, verify that your hosted control plane pods are up and running by entering the following command:

modules/hcp-bm-ingress.adoc

@@ -186,4 +186,4 @@ clusteroperator.config.openshift.io/console
 clusteroperator.config.openshift.io/ingress                                      4.x.y     True        False         False      53m
 ----
 +
-Replace `<4.x.y>` with the supported {product-title} version that you want to use, for example, `4.14.0-x86_64`.
+Replace `<4.x.y>` with the supported {product-title} version that you want to use, for example, `4.17.0-multi`.

modules/hcp-create-hc-arm64-aws.adoc

@@ -36,7 +36,7 @@ $ hcp create cluster aws \
 <4> Specify the path to your pull secret, for example, `/user/name/pullsecret`.
 <5> Specify the path to your AWS STS credentials file, for example, `/home/user/sts-creds/sts-creds.json`.
 <6> Specify the AWS region name, for example, `us-east-1`.
-<7> Specify the supported {product-title} version that you want to use, for example, `4.14.0-x86_64`. If you are using a disconnected environment, replace `<ocp_release_image>` with the digest image. To extract the {product-title} release image digest, see "Extracting the {product-title} release image digest".
+<7> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`. If you are using a disconnected environment, replace `<ocp_release_image>` with the digest image. To extract the {product-title} release image digest, see "Extracting the {product-title} release image digest".
 <8> Specify the Amazon Resource Name (ARN), for example, `arn:aws:iam::820196288204:role/myrole`.
 <9> The `multi-arch` flag indicates that the hosted cluster supports both `amd64` and `arm64` node pools. When you set the flag and supply a release image, the release image must be a multi-architecture release image. When you set the flag and supply a release stream, the release stream must be a multi-architecture release stream. If you do not set the `multi-arch` flag, the management cluster and node pool CPU architectures must match. Otherwise, a warning is displayed. A node pool supports only one CPU architecture within the same node pool.
 

modules/hcp-ibmz-scale-np.adoc

@@ -21,7 +21,7 @@ When you scale down a node pool, Agents are unbound from the corresponding clust
 $ oc -n <clusters_namespace> scale nodepool <nodepool_name> --replicas 2
 ----
 +
-The Cluster API agent provider randomly picks two agents that are then assigned to the hosted cluster. Those agents go through different states and finally join the hosted cluster as {ocp-short} nodes. The agents pass through the transition phases in the following order:
+The Cluster API agent provider randomly picks two agents that are then assigned to the hosted cluster. Those agents go through different states and finally join the hosted cluster as {product-title} nodes. The agents pass through the transition phases in the following order:
 
 * `binding`
 * `discovering`
@@ -69,7 +69,7 @@ da503cf1-a347-44f2-875c-4960ddb04091   hosted-forwarder   true          auto-ass
 $ hcp create kubeconfig --namespace <clusters_namespace> --name <hosted_cluster_namespace> > <hosted_cluster_name>.kubeconfig
 ----
 
-. After the agents reach the `added-to-existing-cluster` state, verify that you can see the {ocp-short} nodes by entering the following command:
+. After the agents reach the `added-to-existing-cluster` state, verify that you can see the {product-title} nodes by entering the following command:
 +
 [source,terminal]
 ----

modules/hcp-managed-aws-hc-separate.adoc

@@ -25,7 +25,7 @@ $ hcp create cluster aws \
 <1> Replace `<infra_id>` with the same ID that you specified in the `create infra aws` command. This value identifies the IAM resources that are associated with the hosted cluster.
 <2> Replace `<hosted_cluster_name>` with the name of your hosted cluster.
 <3> Replace `<path_to_sts_credential_file>` with the same name that you specified in the `create infra aws` command.
-<4> Replace `<path_to_pull_secret>` with the name of the file that contains a valid {ocp-short} pull secret.
+<4> Replace `<path_to_pull_secret>` with the name of the file that contains a valid {product-title} pull secret.
 <5> The `--generate-ssh` flag is optional, but is good to include in case you need to SSH to your workers. An SSH key is generated for you and is stored as a secret in the same namespace as the hosted cluster.
 <6> Replace `<role_name>` with the Amazon Resource Name (ARN), for example, `arn:aws:iam::820196288204:role/myrole`. Specify the Amazon Resource Name (ARN), for example, `arn:aws:iam::820196288204:role/myrole`. For more information about ARN roles, see "Identity and Access Management (IAM) permissions".
 

modules/hcp-non-bm-hc-mirror.adoc

@@ -52,4 +52,4 @@ $ hcp create cluster agent \
 <6> Specify the `icsp.yaml` file that defines ICSP and your mirror registries.
 <7> Specify the path to your SSH public key. The default file path is `~/.ssh/id_rsa.pub`.
 <8> Specify your hosted cluster namespace.
-<9> Specify the supported {product-title} version that you want to use, for example, `4.14.0-x86_64`. If you are using a disconnected environment, replace `<ocp_release_image>` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_.
+<9> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`. If you are using a disconnected environment, replace `<ocp_release_image>` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_.

modules/hcp-non-bm-hc.adoc

@@ -53,7 +53,7 @@ $ hcp create cluster agent \
 <7> Specify the path to your SSH public key. The default file path is `~/.ssh/id_rsa.pub`.
 <8> Specify your hosted cluster namespace.
 <9> The default value for the control plane availability policy is `HighlyAvailable`.
-<10> Specify the supported {ocp-short} version that you want to use, for example, `4.14.0-x86_64`.
+<10> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`.
 
 .Verification
 
@@ -70,4 +70,4 @@ $ oc -n <hosted_control_plane_namespace> get pods
 NAME                                             READY   STATUS    RESTARTS   AGE
 catalog-operator-6cd867cc7-phb2q                 2/2     Running   0          2m50s
 control-plane-operator-f6b4c8465-4k5dh           1/1     Running   0          4m32s
-----
+----

modules/hcp-virt-map-storage.adoc

@@ -46,7 +46,7 @@ The following table shows how volume and access mode capabilities map to KubeVir
 | RWX: `Block` or `Filesystem`
 | `ReadWriteOnce` (RWO) `Block` or `Filesystem` RWX `Block` only
 | Supported
-| Use `Block` mode because `Filesystem` volume mode results in degraded hosted `Block` mode performance. RWX `Block` volume mode is supported only when the hosted cluster is {ocp-short} 4.16 or later.
+| Use `Block` mode because `Filesystem` volume mode results in degraded hosted `Block` mode performance. RWX `Block` volume mode is supported only when the hosted cluster is {product-title} 4.16 or later.
 
 | RWO `Block` storage
 | RWO `Block` storage or `Filesystem`