fix:

  1. Updated the text **Conformation** to **CloudFormation** in https://aws-observability.github.io/observability-best-practices/guides/cost/cost-visualization/amazon-prometheus on line 7

  2. Updated Pros and Cons > Advantages for "Configuring High-Availability is a challenge","Too many copies of Collector in use", and "Too many copies of Collector in use" to sound more positive in https://aws-observability.github.io/observability-best-practices/guides/operational/adot-at-scale/operating-adot-collector between line 80-83

docs/en/guides/cost/cost-visualization/amazon-prometheus.md

@@ -4,7 +4,7 @@ Amazon Managed Service for Prometheus cost and usage visuals will allow you to g
 
 To visualize and analyze the cost and usage data, you need to create a custom Athena view.
 
-1.	Before proceeding, make sure that you’ve created the CUR (step #1) and deployed the AWS Conformation Template (step #2) mentioned in the [Implementation overview][cid-implement].
+1.	Before proceeding, make sure that you’ve created the CUR (step #1) and deployed the AWS CloudFormation Template (step #2) mentioned in the [Implementation overview][cid-implement].
 
 2.	Now, Create a new Amazon Athena [view][view] by using the following query. This query fetches cost and usage of Amazon Managed Service for Prometheus across all the AWS Accounts in your Organization.
 

docs/en/guides/operational/adot-at-scale/operating-adot-collector.md

@@ -78,9 +78,9 @@ The same architecture can also be used for collecting traces. In this case, inst
 **Advantages**
 
 * Minimal scaling concerns
-* Configuring High-Availability is a challenge
-* Too many copies of Collector in use
-* Can be easy for Logs support
+* High availability configuration options
+* Flexibility in Collector deployment
+* Simplified log support process
 
 **Disadvantages**