Update storage-files-redundancy-overview.md

Author: jeffpatt24

includes/storage-files-redundancy-overview.md

@@ -5,15 +5,15 @@
  author: khdownie
  ms.service: azure-file-storage
  ms.topic: include
- ms.date: 06/09/2023
+ ms.date: 02/23/2025
  ms.author: kendownie
- ms.custom: include file
+ ms.custom: Include file
 ---
-To protect the data in your Azure file shares against data loss or corruption, Azure Files stores multiple copies of each file as they are written. Depending on your requirements, you can select different degrees of redundancy. Azure Files currently supports the following data redundancy options:
+To protect data in your Azure file shares against data loss or corruption, Azure Files stores multiple copies of each file as they're written. Depending on your requirements, you can select different degrees of redundancy. Azure Files currently supports the following data redundancy options:
 
 - **Locally-redundant storage (LRS)**: With LRS, every file is stored three times within an Azure storage cluster. This protects against data loss due to hardware faults, such as a bad disk drive. 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.
 - **Zone-redundant storage (ZRS)**: With ZRS, three copies of each file are stored. However, these copies are physically isolated in three distinct storage clusters in different Azure *availability zones*. Availability zones are unique physical locations within an Azure region. Each zone is made up of one or more data centers equipped with independent power, cooling, and networking. A write to storage isn't accepted until it's written to the storage clusters in all three availability zones. 
-- **Geo-redundant storage (GRS)**: With GRS, you have two regions, a primary region and a secondary region. Files are stored three times within an Azure storage cluster in the primary region. Writes are asynchronously replicated to a Microsoft-defined secondary region. GRS provides six copies of your data spread between two Azure regions. In the event of a major disaster such as the permanent loss of an Azure region due to a natural disaster or other similar event, Microsoft will perform a failover. In this case, the secondary becomes the primary, serving all operations. Because the replication between the primary and secondary regions is asynchronous, in the event of a major disaster, data not yet replicated to the secondary region will be lost. You can also perform a manual failover of a geo-redundant storage account.
+- **Geo-redundant storage (GRS)**: With GRS, you have two regions, a primary region and a secondary region. Files are stored three times within an Azure storage cluster in the primary region. Writes are asynchronously replicated to a Microsoft-defined secondary region. GRS provides six copies of your data spread between two Azure regions. If a major disaster such as the permanent loss of an Azure region due to a natural disaster or other similar event, Microsoft will perform a failover. In this case, the secondary becomes the primary, serving all operations. Because the replication between the primary and secondary regions is asynchronous, if a major disaster occurs, data not yet replicated to the secondary region will be lost. You can also perform a manual failover of a geo-redundant storage account.
 - **Geo-zone-redundant storage (GZRS)**: You can think of GZRS as ZRS, but with geo-redundancy. With GZRS, files are stored three times across three distinct storage clusters in the primary region. All writes are then asynchronously replicated to a Microsoft-defined secondary region. The failover process for GZRS works the same as GRS.
 
 Standard file shares support all four redundancy types. Premium file shares only support LRS and ZRS.