Merge pull request #309160 from stevenmatthew/redundancy1208

redundancy1208

Author: prmerger-automator[bot]

articles/storage/common/storage-redundancy.md

@@ -40,7 +40,7 @@ The redundancy setting for a storage account is shared for all storage services
 
 Azure Storage offers two options for how your data is replicated in the primary region:
 
-- **Locally redundant storage (LRS)** replicates the data within your storage accounts to one or more Azure availability zones located in the primary region of your choice.
+- **Locally redundant storage (LRS)** replicates the data within your storage accounts to a single physical datacenter located in the primary region of your choice.
 
 - **Zone-redundant storage (ZRS)** copies your data synchronously across three or more Azure availability zones in the primary region. For applications requiring high availability, Microsoft recommends using ZRS in the primary region, and also replicating to a secondary region.
 
@@ -49,7 +49,7 @@ Azure Storage offers two options for how your data is replicated in the primary
 
 ### Locally redundant storage
 
-Locally redundant storage (LRS) replicates the data within your storage accounts to one or more Azure availability zones located in the primary region of your choice. Choosing your preferred availability zone isn't supported, and Azure might move or expand LRS accounts across zones to improve load balancing. LRS provides at least 99.999999999% (11 nines) durability of objects over a given year. Visit the [What are Azure availability zones](../../reliability/availability-zones-overview.md) article to learn more about availability zone reliability.
+Locally redundant storage (LRS) replicates the data within your storage accounts to a single physical datacenter in the primary region of your choice. Although choosing an availability zone isn't supported, Azure might move or expand LRS accounts across zones to improve load balancing. LRS provides at least 99.999999999% (11 nines) durability of objects over a given year. Visit the [What are Azure availability zones](../../reliability/availability-zones-overview.md) article to learn more about availability zone reliability.
 
 LRS is the lowest-cost redundancy option and offers the least durability compared to other options. LRS protects your data against drive, server, and rack failures. However, if a disaster such as fire or flooding occurs within the data center, all replicas of a storage account using LRS might be lost or unrecoverable. If a temporary event, such as a thermal event, occurs within the data center, all replicas might be temporarily unavailable until the event is resolved. To mitigate these risks, Microsoft recommends using [zone-redundant storage](#zone-redundant-storage) (ZRS), [geo-redundant storage](#geo-redundant-storage) (GRS), or [geo-zone-redundant storage](#geo-zone-redundant-storage) (GZRS).
 
@@ -107,7 +107,7 @@ When you utilize GRS or GZRS, the data in the secondary region isn't available f
 If the primary region becomes unavailable, you can choose to fail over to the secondary region. After the failover operation completes, the secondary region becomes the primary region and you're able to read and write data. For more information on disaster recovery and to learn how to fail over to the secondary region, see [Disaster recovery and storage account failover](storage-disaster-recovery-guidance.md).
 
 > [!IMPORTANT]
-> Because data is replicated to the secondary region asynchronously, a failure that affects the primary region might result in data loss if the primary region can't be recovered. The interval between the most recent writes to the primary region and the last write to the secondary region is known as the recovery point objective (RPO). The RPO indicates the point in time to which data can be recovered. Azure Storage now offers Geo priority replication which ensures the RPO for Block Blobs are less than or equal to 15 minutes. For more information, see the [Azure Storage Geo Priority Replication](storage-redundancy-priority-replication.md) article.
+> Because data is replicated to the secondary region asynchronously, a failure that affects the primary region might result in data loss if the primary region can't be recovered. The interval between the most recent writes to the primary region and the last write to the secondary region is known as the recovery point objective (RPO). The RPO indicates the point in time to which data can be recovered. Azure Storage now offers Geo priority replication, which ensures the RPO for Block Blobs are less than or equal to 15 minutes. For more information, see the [Azure Storage Geo Priority Replication](storage-redundancy-priority-replication.md) article.
 
 ### Geo-redundant storage
 
@@ -163,10 +163,10 @@ The following table describes key parameters for each redundancy option:
 | Parameter | LRS | ZRS | GRS/RA-GRS | GZRS/RA-GZRS |
 |:-|:-|:-|:-|:-|
 | Percent durability of objects over a given year | at least 99.999999999% (11 9s) | at least 99.9999999999% (12 9s) | at least 99.99999999999999% (16 9s) | at least 99.99999999999999% (16 9s) |
-| Availability for read requests | At least 99.9% (99% for cool/cold/archive access tiers) | At least 99.9% (99% for cool/cold access tier) | At least 99.9% (99% for cool/cold/archive access tiers) for GRS<br/><br/>At least 99.99% (99.9% for cool/cold/archive access tiers) for RA-GRS | At least 99.9% (99% for cool/cold access tier) for GZRS<br/><br/>At least 99.99% (99.9% for cool/cold access tier) for RA-GZRS |
-| Availability for write requests | At least 99.9% (99% for cool/cold/archive access tiers) | At least 99.9% (99% for cool/cold access tier) | At least 99.9% (99% for cool/cold/archive access tiers) | At least 99.9% (99% for cool/cold access tier) |
+| Availability for read requests | At least 99.9%; 99% for cool/cold/archive access tiers | At least 99.9%; 99% for cool/cold access tier | At least 99.9% for GRS; 99% for cool/cold/archive access tiers<br/><br/>At least 99.99% for RA-GRS; 99.9% for cool/cold/archive access tiers | At least 99.9% for GZRS; 99% for cool/cold access tier<br/><br/>At least 99.99% for RA-GZRS; 99.9% for cool/cold access tier |
+| Availability for write requests | At least 99.9%; 99% for cool/cold/archive access tiers | At least 99.9%; 99% for cool/cold access tier | At least 99.9%; 99% for cool/cold/archive access tiers | At least 99.9%; 99% for cool/cold access tier |
 
-Note: GRS provides geographic replication but does not allow read access from the secondary region. To maintain read availability during a primary region outage, RA-GRS or RA-ZRS must be used.
+Note: GRS provides geographic replication but doesn't allow read access from the secondary region. To maintain read availability during a primary region outage, RA-GRS or RA-ZRS must be used.
 
 For more information, see the [Service Level Agreement for Storage Accounts](https://azure.microsoft.com/support/legal/sla/storage/v1_5/).
 
@@ -198,8 +198,9 @@ The following table shows the redundancy options supported by each Azure Storage
 
 <sup>1</sup> SSD file shares are supported on LRS and ZRS.<br/>
 <sup>2</sup> ZRS managed disks have certain limitations. See the [Limitations](/azure/virtual-machines/disks-redundancy#limitations) section of the redundancy options for managed disks article for details.<br/>
+
 > [!NOTE]
-> For storage accounts that leverage the smart tier public preview, redundancy conversions and account failover scenarios have additional dependencies. For more information, see [Optimize costs with smart tier](../blobs/access-tiers-smart.md)
+> For storage accounts that utilize the smart tier public preview, redundancy conversions and account failover scenarios have dependencies. For more information, see [Optimize costs with smart tier](../blobs/access-tiers-smart.md)
 
 ### Supported storage account types