address feedback

docs/en/observability/apm/view-and-analyze/filter-and-search/cross-cluster-search.asciidoc

@@ -49,19 +49,14 @@ include remote clusters.
 * In `kibana.yml` -- Update the {kibana-ref}/apm-settings-kb.html[`xpack.apm.indices.*`] configuration values to
 include remote clusters.
 
-// I'm not sure if this is better presented as a troubleshooting topic (i.e. reactive)
-// or a best practice (i.e. preventative). For now I've added it as a tip, but it could
-// be more integrated into the content on this page.
 [TIP]
 .Exclude data tiers from search
 ====
 In a cross-cluster search (CCS) environment, it's possible for different clusters to serve different data tiers in responses.
 If one of the requested clusters responds slowly, it can cause a timeout at the proxy after 320 and 502 responses presented
 as failure toast messages in the UI with no data loaded.
 
-// Fix or prevent?
-To fix/prevent this, you can exclude {ref}/data-tiers.html[data tiers] that might slow down responses from search
-(for example, the `data_frozen` tier). To exclude data tiers from search in the APM UI:
+To prevent this, you can exclude {ref}/data-tiers.html[data tiers] that might slow down responses from search: the `data_frozen` and `data_cold` tiers. To exclude data tiers from search in the APM UI:
 
 . In {kib}, go to *Stack Management* → *Advanced Settings*.
 . In the *Observability* section, update the *Excluded data tiers from search* option with a list of data tiers.