Update after tech review

Author: thild42

pages/public_cloud/public_cloud_databases/databases_regions_comparison/guide.en-gb.md

@@ -1,7 +1,7 @@
 ---
 title: "Comparison of Public Cloud Databases Deployment Modes - Understanding 3-AZ / 1-AZ"
 excerpt: "Explore OVHcloud's Public Cloud Databases deployment modes"
-updated: 2025-05-23
+updated: 2025-05-27
 ---
 
 ## Objective
@@ -10,7 +10,7 @@ OVHcloud offers two deployment modes for its [Public Cloud Databases](/links/pub
 
 ## Concepts
 
-OVHcloud managed databases offer two main deployment modes, each optimized for specific use cases and offering various levels of redundancy and fault tolerance:
+OVHcloud managed databases 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 applications, offering basic resilience with optimized cost.
 2. **3-AZ Region**: suitable for applications that require high availability with low RTO/RPO and resilience to availability zone outage.
@@ -23,9 +23,7 @@ OVHcloud managed databases offer two main deployment modes, each optimized for s
 
 ### 1-AZ Region
 
-#### Infrastructure and Redundancy
-
-A 1-AZ Region consists of a **single availability zone covering multiple data centers within the same geographical region**, utilizing a 2N+1 redundancy design. When a database service is deployed with multiple nodes, 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 database service is located in a specific OpenStack region that spans over multiple data center. The nodes of a multi-node database services 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 database 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 database service is deployed with multiple nodes, 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 database service is located in a specific OpenStack region that spans over multiple data center. The nodes of a multi-node database services 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 database service, access to data could be impacted, even if other data centers in the zone remain operational.
 
 #### Characteristics
 
@@ -36,20 +34,10 @@ A 1-AZ Region consists of a **single availability zone covering multiple data ce
 
 - **Single Point of Failure:** In a 1-AZ region, the database services nodes **may be** deployed within a single data center. If this data center experiences an outage, access to your database services could be impacted, even if other data centers within the same availability zone remain operational.
 
-#### Redundancy Specifications for 1-AZ
-
-| Specification         | Description |
-|-----------------------|-------------|
-| **Redundancy Type** | 2N+1 across multiple data centers. |
-| **Fault Tolerance** | Server and disk-level fault tolerance. Data center outage risk. |
-| **Use Case Examples** | Suitable for development, testing, and non-critical databases workloads where cost-effectiveness is prioritized over maximum availability. |
-
 <a name="3azregion"></a>
 
 ### 3-AZ Region
 
-#### Infrastructure and Redundancy
-
 3-AZ Regions consist of **three independent availability zones**, each isolated in terms of power, cooling, and network systems, providing true fault isolation. This architecture ensures **service availability** even if an entire availability zone experiences an outage.
 
 #### Characteristics
@@ -61,14 +49,6 @@ A 1-AZ Region consists of a **single availability zone covering multiple data ce
 
 3-AZ Regions are particularly suited to mission-critical and availability-sensitive applications, where data governance requires continuous availability. This includes sectors such as e-commerce, healthcare platforms, financial services or live streaming applications.
 
-#### Performance Specifications for 3-AZ
-
-| Specification         | Description |
-|-----------------------|-------------|
-| **Connectivity** | Low latency between availability zones. |
-| **High Availability** | Maintains access even in the event of zone failures. |
-| **Use Case Examples** | Mission-critical and availability-sensitive applications, e-commerce, healthcare platforms, financial services, or live-streaming applications. |
-
 ## Go Further
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case.