Date update + proofreading + fr-fr deletion

Author: Y0Coss

pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/guide.en-gb.md

@@ -1,7 +1,7 @@
 ---
 title: "Comparison of Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ"
 excerpt: "Explore OVHcloud's Public Cloud Analytics deployment modes"
-updated: 2025-06-10
+updated: 2025-06-11
 ---
 
 ## Objective
@@ -10,10 +10,10 @@ OVHcloud offers two deployment modes for its [Analytics](/links/public-cloud/ana
 
 ## Concepts
 
-OVHcloud managed analytics services offer two main deployment modes, each optimized for specific use cases and offering various levels of resilience and failover:
+OVHcloud managed Analytics services offer two main deployment modes, each optimized for specific use cases and offering various levels of resilience and failover:
 
-1. **1-AZ Region**: for standard analytics workloads, offering basic resilience with optimized cost.
-2. **3-AZ Region**: suitable for highly availability analytics workloads with low RTO/RPO and resilience to availability zone outage.
+1. **1-AZ Region**: for standard Analytics workloads, offering basic resilience with optimized cost.
+2. **3-AZ Region**: suitable for highly availability Analytics workloads with low RTO/RPO and resilience to availability zone outage.
 
 ## Deployment modes
 
@@ -23,16 +23,16 @@ OVHcloud managed analytics services offer two main deployment modes, each optimi
 
 ### 1-AZ Region
 
-A 1-AZ Region consists of a **single availability zone covering multiple data centers within the same geographical region**. When a multi-node analytics service is deployed, this single AZ setup offers resilience against node and disk failures but may be vulnerable to a complete OpenStack region outage. Note that in a 1-AZ region, the analytics service is located in a specific OpenStack region that spans over multiple data center. The nodes of a multi-node analytics service are scattered in different hosts that **may be** located in different data centers. If an outage occurs in a specific data center hosting one or multiple nodes of the analytics service, access to data could be impacted, even if other data centers in the zone remain operational.
+A 1-AZ Region consists of a **single availability zone covering multiple data centers within the same geographical region**. When a multi-node Analytics service is deployed, this single AZ setup offers resilience against node and disk failures but may be vulnerable to a complete OpenStack region outage. Note that in a 1-AZ region, the Analytics service is located in a specific OpenStack region that spans over multiple data centers. The nodes of a multi-node Analytics service are scattered in different hosts that **may be** located in different data centers. If an outage occurs in a specific data center hosting one or multiple nodes of the Analytics service, access to data could be impacted, even if other data centers in the zone remain operational.
 
 #### Characteristics
 
 - **Cost-Effectiveness:** Deploying in a 1-AZ region is generally more affordable, making it suitable for development, testing, and non-critical workloads where cost considerations are paramount.
-- **Host antiaffinity:** The nodes of a multi-node analytics service are deployed in different physical hosts offering resilience to host outage.
+- **Host antiaffinity:** The nodes of a multi-node Analytics service are deployed in different physical hosts offering resilience to host outage.
 
 #### Limitations
 
-- **Single Point of Failure:** In a 1-AZ region, the analytics service nodes **may be** deployed within a single data center. If this data center experiences an outage, access to your analytics service could be impacted, even if other data centers within the same availability zone remain operational.
+- **Single Point of Failure:** In a 1-AZ region, the Analytics service nodes **may be** deployed within a single data center. If this data center experiences an outage, access to your Analytics service could be impacted, even if other data centers within the same availability zone remain operational.
 
 <a name="3azregion"></a>
 
@@ -42,8 +42,8 @@ A 1-AZ Region consists of a **single availability zone covering multiple data ce
 
 #### Characteristics
 
-- **High Availability:** Multi-node analytics service is deployed across three independent availability zones, ensuring service continuity even if one zone experiences an outage.
-- **Low Latency:** The architecture offers ultra-low latency between availability zones, ensuring performance of analytics operations accross all the nodes of the cluster.
+- **High Availability:** Multi-node Analytics service is deployed across three independent availability zones, ensuring service continuity even if one zone experiences an outage.
+- **Low Latency:** The architecture offers ultra-low latency between availability zones, ensuring performance of Analytics operations accross all the nodes of the cluster.
 
 #### Ideal Use Cases