Remove mentions of multi-az from Cloud documentation (#5096)

* remove mentions of multi-az from cloud documentation

* add back mult-az content that should stay

* updated heading formatting

content/influxdb/cloud-dedicated/reference/internals/security.md

@@ -77,9 +77,8 @@ InfluxDB Cloud Dedicated is available on the following cloud providers:
 - [Microsoft Azure](https://azure.microsoft.com/en-us/) _(Coming)_
 - [Google Cloud Platform (GCP)](https://cloud.google.com/) _(Coming)_
 
-To ensure data security, availability, and durability:
-- Each instance is isolated and protected in its own virtual private cloud (VPC).
-- Clusters are deployed across multiple provider availability zones.
+To ensure data security, availability, and durability, each instance is isolated
+and protected in its own virtual private cloud (VPC).
 
 Users interact with InfluxDB Cloud Dedicated only through Cloud Dedicated established APIs.
 For cluster management activities, authorized users interact with the Granite service.
@@ -99,7 +98,6 @@ Each VPC within AWS is segmented into public and private subnets:
 - The private subnet contains supporting infrastructure (for example, compute and storage)
   not exposed to the public internet.
 
-To ensure fault tolerance across the data layer, clusters are deployed across multiple availability zones.
 AWS data centers are compliant with many physical and information security standards.
 For detail about AWS's physical security and data center protocols, see [AWS's Compliance](https://aws.amazon.com/compliance/).
 
@@ -109,7 +107,6 @@ In Google Cloud Platform (GCP), InfluxDB Cloud Dedicated uses the Google Kuberne
 and Google Compute Engine to deploy individual cluster components.
 Clusters are isolated at the project level
 to enhance access controls and data governance, and support auditing.
-To ensure fault tolerance across the data layer, clusters are deployed across multiple availability zones.
 
 Google Cloud Platform data centers are compliant with many physical and information security standards.
 For detail about physical security in GCP data centers, see [Google's Compliance website](https://cloud.google.com/security/compliance/).
@@ -120,7 +117,6 @@ In Microsoft Azure, InfluxDB Cloud Dedicated uses Azure Kubernetes Service (AKS)
 and Azure Virtual Machines to deploy individual cluster components.
 To support auditing and authorization control within Azure,
 clusters are deployed into dedicated VNets within each region.
-To ensure fault tolerance across the data layer, clusters are deployed across multiple availability zones.
 
 Microsoft Azure data centers are compliant with many physical and information security standards.
 For detail about physical security within Microsoft Azure data centers, see [Microsoft's Compliance website](https://www.microsoft.com/en-us/trust-center/compliance/compliance-overview).

content/influxdb/cloud/reference/internals/durability.md

@@ -18,13 +18,13 @@ data is consistent and readable.
 
 ##### On this page
 
-<!-- [Data replication](#data-replication)
--->
+- [Data replication](#data-replication)
 - [Backup processes](#backup-processes)
 - [Recovery](#recovery)
 - [Data verification](#data-verification)
 
-<!-- ## Data replication
+## Data replication
+
 InfluxDB Cloud replicates data in both the write tier and the storage tier.
 
 - **Write tier:** all data written to InfluxDB is processed by a durable message queue.
@@ -32,9 +32,9 @@ InfluxDB Cloud replicates data in both the write tier and the storage tier.
   replicates each partition across other physical nodes in the message queue.
 - **Storage tier:** all data in the underlying storage tier is replicated across
   two availability zones in a cloud region.
--->
 
 ## Backup processes
+
 InfluxDB Cloud backs up all data in the following way:
 
 - [Backup on write](#backup-on-write)
@@ -42,6 +42,7 @@ InfluxDB Cloud backs up all data in the following way:
 - [Periodic TSM snapshots](#periodic-tsm-snapshots)
 
 ### Backup on write
+
 All inbound write requests to InfluxDB Cloud are added to a durable message queue.
 The message queue does the following:
 
@@ -60,6 +61,7 @@ To minimize potential data loss due to defects introduced in the InfluxDB Cloud
 we minimize the code used between the data ingest and backup processes.
 
 ### Backup after compaction
+
 The InfluxDB storage engine compresses data over time in a process known as
 [compaction](/influxdb/cloud/reference/glossary/#compaction).
 When each compaction cycle completes, InfluxDB Cloud stores compressed
@@ -67,10 +69,12 @@ When each compaction cycle completes, InfluxDB Cloud stores compressed
 in object storage.
 
 ### Periodic TSM snapshots
+
 To provide multiple data recovery points, InfluxDB Cloud takes weekly snapshots of TSM files uploaded to object storage. The TSM snapshot includes a copy of all (non-deleted) data when the snapshot is created.
 These snapshots are preserved for 100 days.
 
 ## Recovery
+
 InfluxDB Cloud uses the following out-of-band backups stored in object storage to recover data:
 
 - **Message queue backup:** line protocol from inbound write requests within the last 96 hours
@@ -85,12 +89,14 @@ For example, if we need to rebuild all data from the TSM snapshots and message q
 it could take 24 hours or longer.
 
 ## Data verification
+
 InfluxDB Cloud has two data verification services running at all times:
 
 - **Entropy detection:** ensures that replicated data is consistent
 - **Data verification:** verifies that data written to InfluxDB is readable
 
 ## InfluxDB Cloud status
+
 InfluxDB Cloud regions and underlying services are monitored at all times.
 For information about the current status of InfluxDB Cloud, see the
 [InfluxDB Cloud status page](https://status.influxdata.com).

content/influxdb/cloud/reference/internals/security.md

@@ -69,9 +69,8 @@ InfluxDB Cloud is available on the following cloud providers:
 - [Microsoft Azure](https://azure.microsoft.com/en-us/)
 - [Google Cloud Platform (GCP)](https://cloud.google.com/)
 
-To ensure data security, availability, and durability:
-- Each instance is isolated and protected in its own virtual private cloud (VPC)
-- Clusters are deployed across multiple provider availability zones
+To ensure data security, availability, and durability, each instance is isolated
+and protected in its own virtual private cloud (VPC).
 
 ### Amazon Web Services (AWS)
 
@@ -81,7 +80,6 @@ Each VPC within AWS is segmented into public and private subnets:
 - The public subnet contains resources exposed to the public internet, including load balancers and network address translation (NAT) gateways.
 - The private subnet contains supporting infrastructure (e.g., compute, storage) not exposed to the public internet.
 
-To ensure fault tolerance across the data layer, clusters are deployed across multiple availability zones.
 AWS data centers are compliant with many physical and information security standards.
 For detail about AWS's physical security and data center protocols, see [AWS's Compliance](https://aws.amazon.com/compliance/).
 
@@ -91,7 +89,6 @@ In Google Cloud Platform (GCP), InfluxDB Cloud uses the Google Kubernetes Engine
 and Google Compute Engine to deploy individual cluster components.
 Clusters are isolated at the project level
 to enhance access controls, data governance, and support auditing.
-To ensure fault tolerance across the data layer, clusters are deployed across multiple availability zones.
 
 Google Cloud Platform data centers are compliant with many physical and information security standards.
 For detail about physical security in GCP data centers, see [Google's Compliance website](https://cloud.google.com/security/compliance/).
@@ -102,7 +99,6 @@ In Microsoft Azure, InfluxDB Cloud uses Azure Kubernetes Service (AKS)
 and Azure Virtual Machines to deploy individual cluster components.
 To support auditing and authorization control within Azure,
 clusters are deployed into dedicated VNets within each region.
-To ensure fault tolerance across the data layer, clusters are deployed across multiple availability zones.
 
 Microsoft Azure data centers are compliant with many physical and information security standards.
 For detail about physical security within Microsoft Azure data centers, see [Microsoft's Compliance website](https://www.microsoft.com/en-us/trust-center/compliance/compliance-overview).