try to pass acrolinx score

Author: markjbrown

articles/cosmos-db/high-availability.md

@@ -1,11 +1,11 @@
 ---
 title: High availability in Azure Cosmos DB 
 description: This article describes how to build a highly available solution using Cosmos DB
-author: rothja
+author: markjbrown
 ms.service: cosmos-db
 ms.topic: conceptual
-ms.date: 11/11/2021
-ms.author: jroth
+ms.date: 02/16/2022
+ms.author: mjbrown
 ms.reviewer: sngun
 
 ---
@@ -29,15 +29,15 @@ Refer to the [SLAs section](#slas) for the guaranteed availability SLAs.
 
 ## Replica outages
 Replica outages refer to outages of individual nodes in a Cosmos DB cluster deployed in an Azure region.
-Cosmos DB automatically mitigates replica outages by guaranteeing at least two replicas of your data at all times in each Azure region where your account is deployed.
-This results in RTO = 0 and and RPO = 0, for individual node outages, with no application changes or configurations required.
+Cosmos DB automatically mitigates replica outages by guaranteeing at least two replicas of your data in each Azure region for your account.
+This results in RTO = 0 and RPO = 0, for individual node outages, with no application changes or configurations required.
 
 In many Azure regions, it is possible to distribute your Cosmos DB cluster across **availability zones**, which results increased SLAs, as availability zones are physically separate and provide distinct power source, network, and cooling. See [Availability Zones](/azure/architecture/reliability/architect).
-When using this option, Cosmos DB provides RTO = 0 and and RPO = 0 even in case of outages of a whole availability zone.
+When using this option, Cosmos DB provides RTO = 0 and RPO = 0 even in outage of a whole availability zone.
 
-When deploying in a single Azure region, with no extra user input, Cosmos DB is resilient to node outages. Enabling redundancy across availability zones makes Cosmos DB resilient to entire availability zone outages at the cost of increased charges. Both SLAs and price are reported in the [SLAs section](#slas).
+When deploying in a single Azure region, with no extra user input, Cosmos DB is resilient to node outages. Enabling redundancy across availability zones makes Cosmos DB resilient to zone outages at the cost of increased charges. Both SLAs and price are reported in the [SLAs section](#slas).
 
-Zone redundancy can only be configured when adding a new region to an Azure Cosmos account. For existing regions, zone redundancy can be enabled by removing the region then adding it back with the zone redundancy enabled. For a single region account, this requires adding one additional region to temporarily failover to, then removing and adding the desired region with zone redundancy enabled.
+Zone redundancy can only be configured when adding a new region to an Azure Cosmos account. For existing regions, zone redundancy can be enabled by removing the region then adding it back with the zone redundancy enabled. For a single region account, this requires adding a region to temporarily failover to, then removing and adding the desired region with zone redundancy enabled.
 
 By default, a Cosmos DB account does not use multiple availability zones. You can enable deployment across multiple availability zones in the following ways: