OSDOCS-20340: CQA-RHCL-update

_topic_maps/_topic_map.yml

@@ -60,7 +60,7 @@ Topics:
 - Name: Install MCP gateway
   File: mcp-gateway-install
 ---
-Name: Deploying Red Hat Connectivity Link
+Name: Deploy Red Hat Connectivity Link
 Dir: deployment
 Distros: rhcl
 Topics:
@@ -112,11 +112,11 @@ Topics:
 - Name: Observing MCP gateway
   File: mcp-gateway-observe
 ---
-Name: Troubleshooting
+Name: Troubleshoot
 Dir: troubleshoot
 Distros: rhcl
 Topics:
-- Name: Troubleshooting MCP gateway
+- Name: Troubleshoot MCP gateway
   File: mcp-gateway-troubleshooting
 ---
 Name: Get support
@@ -126,9 +126,9 @@ Topics:
 - Name: Getting support
   File: getting-support
 ---
-Name: Updating Red Hat Connectivity Link
-Dir: updating
+Name: Update Red Hat Connectivity Link
+Dir: update
 Distros: rhcl
 Topics:
-- Name: Updating Connectivity Link
+- Name: Update Connectivity Link
   File: updating-rhcl

modules/con-update-rhcl-with-web-console.adoc

@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: CONCEPT
 [id="con-update-rhcl-with-web-console_{context}"]
-= Updating {prodname} with the {ocp} web console
+= Update {prodname} with the {ocp} web console
 
 [role="_abstract"]
 You can update from {prodname} {version-1} to {prodname} {version} by using the {ocp} web console. Make sure that the {ocp} version you have is compatible with the {prodname} version you want to update to. See the link:https://access.redhat.com/RedHatConnectivityLink[Red Hat Connectivity LInk Life Cycle Policy] for details about version support and {ocp} compatibility.
@@ -13,4 +13,3 @@ You can update from {prodname} {version-1} to {prodname} {version} by using the
 ====
 On {ocp} 4.19 or later, if you are updating your cluster from a previous {ocp} version that contains Gateway API Custom Resource Definitions (CRDs), you must ensure that these resources exactly match the Gateway API version supported by {ocp} 4.19. For more information, see the https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html-single/updating_clusters/index#nw-ingress-gateway-api-manage-succession_updating-cluster-prepare[OpenShift documentation on managing Gateway API resources].
 ====
-//Q: how else can I update? can I use OLM? any other method?

modules/proc-update-rhcl-with-web-console.adoc

@@ -4,7 +4,7 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="proc-update-rhcl-with-web-console_{context}"]
-= Updating to {prodname} {version} in the web console
+= Update to {prodname} {version} in the web console
 
 [role="_abstract"]
 Update your {product-title} with the {ocp} web console.

updating/updating-rhcl.adoc → update/updating-rhcl.adoc

@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 include::_attributes/attributes.adoc[]
 [id="updating-rhcl"]
-= Updating {prodname} {version}
+= Update {prodname} {version}
 :context: updating-rhcl
 
 toc::[]
@@ -19,4 +19,4 @@ include::modules/proc-update-rhcl-with-web-console.adoc[leveloffset=+1]
 [role="_additional-resources"]
 == Additional resources
 
-* link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html/operators/administrator-tasks#olm-upgrading-operators[Updating installed Operators]
+* link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/operators/administrator-tasks#olm-upgrading-operators[Updating installed Operators]