TELCODOCS-1191: Clean up of SNO references in TALM docs (#56826)

* TELCODOCS-1191: Clean up of SNO references in TALM docs

* openshift-talm-pre-cache changed to openshift-talo-pre-cache

Author: amolnar-gh

modules/cnf-about-topology-aware-lifecycle-manager-config.adoc

@@ -16,6 +16,9 @@ The {cgu-operator-first} manages the deployment of {rh-rhacm-first} policies for
 * The order of policies remediated to the cluster
 * The assignment of a canary cluster
 
-For {sno}, the {cgu-operator-first} can create a backup of a deployment before an upgrade. If the upgrade fails, you can recover the previous version and restore a cluster to a working state without requiring a reprovision of applications.
+For {sno}, the {cgu-operator-first} offers the following features:
+
+* Create a backup of a deployment before an upgrade
+* Pre-caching images for clusters with limited bandwidth
 
 {cgu-operator} supports the orchestration of the {product-title} y-stream and z-stream updates, and day-two operations on y-streams and z-streams.

modules/cnf-topology-aware-lifecycle-manager-about-cgu-crs.adoc

@@ -168,7 +168,7 @@ Policies are missing or invalid, or an invalid platform image has been specified
 [id="precaching_{context}"]
 == Pre-caching
 
-Clusters might have limited bandwidth to access the container image registry, which can cause a timeout before the updates are completed. You can use pre-caching to avoid this. The container image pre-caching starts when you create a `ClusterGroupUpgrade` CR with the `preCaching` field set to `true`.
+Clusters might have limited bandwidth to access the container image registry, which can cause a timeout before the updates are completed. On {sno} clusters, you can use pre-caching to avoid this. The container image pre-caching starts when you create a `ClusterGroupUpgrade` CR with the `preCaching` field set to `true`.
 
 {cgu-operator} uses the `PrecacheSpecValid` condition to report status information as follows:
 
@@ -192,6 +192,7 @@ For more information see the "Using the container image pre-cache feature" secti
 
 [id="creating_backup_{context}"]
 == Creating a backup
+
 For {sno}, {cgu-operator} can create a backup of a deployment before an update. If the update fails, you can recover the previous version and restore a cluster to a working state without requiring a reprovision of applications. To use the backup feature you first create a `ClusterGroupUpgrade` CR with the `backup` field set to `true`. To ensure that the contents of the backup are up to date, the backup is not taken until you set the `enable` field in the `ClusterGroupUpgrade` CR to `true`.
 
 {cgu-operator} uses the `BackupSucceeded` condition to report the status and reasons as follows:

modules/cnf-topology-aware-lifecycle-manager-backup-feature.adoc

@@ -6,7 +6,7 @@
 [id="talo-backup-start_and_update_{context}"]
 = Creating a ClusterGroupUpgrade CR with backup
 
-For {sno}, you can create a backup of a deployment before an upgrade. If the upgrade fails you can use the `upgrade-recovery.sh` script generated by {cgu-operator-first} to return the system to its preupgrade state.
+You can create a backup of a deployment before an upgrade on {sno} clusters. If the upgrade fails you can use the `upgrade-recovery.sh` script generated by {cgu-operator-first} to return the system to its preupgrade state.
 The backup consists of the following items:
 
 Cluster backup:: A snapshot of `etcd` and static pod manifests.

modules/cnf-topology-aware-lifecycle-manager-precache-concept.adoc

@@ -6,7 +6,7 @@
 [id="talo-precache-feature-concept_{context}"]
 = Using the container image pre-cache feature
 
-Clusters might have limited bandwidth to access the container image registry, which can cause a timeout before the updates are completed.
+{sno-caps} clusters might have limited bandwidth to access the container image registry, which can cause a timeout before the updates are completed.
 
 [NOTE]
 ====
@@ -28,7 +28,7 @@ The pre-caching spec is incomplete.
 
 * `true`
 +
-TALM has concluded the pre-caching process. If pre-caching fails for any cluster, the update fails for that cluster but proceeds for all other clusters. A message informs you if pre-caching has failed for any clusters.
+{cgu-operator} has concluded the pre-caching process. If pre-caching fails for any cluster, the update fails for that cluster but proceeds for all other clusters. A message informs you if pre-caching has failed for any clusters.
 * `false`
 +
 Pre-caching is still in progress for one or more clusters or has failed for all clusters.

modules/cnf-topology-aware-lifecycle-manager-precache-feature.adoc

@@ -6,7 +6,7 @@
 [id="talo-precache-start_and_update_{context}"]
 = Creating a ClusterGroupUpgrade CR with pre-caching
 
-The pre-cache feature allows the required container images to be present on the spoke cluster before the update starts.
+For {sno}, the pre-cache feature allows the required container images to be present on the spoke cluster before the update starts.
 
 .Prerequisites
 
@@ -111,7 +111,7 @@ $ oc get cgu -n ztp-group-du-sno du-upgrade-4918 -o jsonpath='{.status}'
 +
 [source,terminal]
 ----
-$ oc get jobs,pods -n openshift-talm-pre-cache
+$ oc get jobs,pods -n openshift-talo-pre-cache
 ----
 +
 .Example output

scalability_and_performance/cnf-talm-for-cluster-upgrades.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-You can use the {cgu-operator-first} to manage the software lifecycle of multiple {sno} clusters. {cgu-operator} uses {rh-rhacm-first} policies to perform changes on the target clusters.
+You can use the {cgu-operator-first} to manage the software lifecycle of multiple clusters. {cgu-operator} uses {rh-rhacm-first} policies to perform changes on the target clusters.
 
 :FeatureName: {cgu-operator-full}