Merge pull request #295915 from MSFTeegarden/patch-87

Updated wording

Author: prmerger-automator[bot]

articles/azure-cache-for-redis/cache-how-to-zone-redundancy.md

@@ -73,9 +73,7 @@ To create a cache, follow these steps:
 
 Azure Cache for Redis automatically allocates zones to the cache on behalf of the user based on the number of nodes per shard and region's zonal support such that the cache is spread across multiple zones for high availability.
 
-With this type of allocation, users don't need to worry about choosing the zones manually for the cache and the capacity issues associated with the zones as Azure handles them.
-
-The actual zones that are allocated to the cache are abstracted from the user.
+With this type of allocation, users don't need to worry about choosing zones manually. The actual zones that are allocated to the cache are abstracted from the user. Azure ensures that the cache's primary and replica nodes are spread across different zones for high availability.
 
 The REST API spec for different types of zonal allocation can be found at: [Create - ZonalAllocationPolicy](/rest/api/redis/redis/create#zonalallocationpolicy).
 

articles/reliability/migrate-cache-redis.md

@@ -19,9 +19,6 @@ Azure Cache for Redis supports zone redundancy in its Standard, Premium, Enterpr
 > [!NOTE]
    > Converting an existing resource from non-availability zone support to availability zone support is available for Standard and Premium tier caches. Enterprise and Enterprise Flash tier caches are created to be zonal by default. 
 
- > [!NOTE]
-   > Zone redundancy isn't supported with geo-replication on the Standard and Premium tiers. It is supported on the Enterprise and Enteprise Flash tiers.
-
 ## Enabling Zone Redundancy for Enterprise, and Enterprise Flash tiers
 
 Currently, the only way to convert an enterprise / enterprise flash resource from non-availability zone support to availability zone support is to redeploy your current cache.
@@ -67,7 +64,7 @@ Users can't disable zone redundancy once it's enabled.
 
 This update can also be done by passing `ZonalAllocationPolicy` as `Automatic` in the request body while updating the cache using REST API. For more information regarding the update process using REST API, see [Update - ZonalAllocationPolicy](/rest/api/redis/redis/update#zonalallocationpolicy).
 
-Updating `ZonalAllocationPolicy to any other value than `Automatic` isn't supported.
+Updating `ZonalAllocationPolicy` to any other value than `Automatic` isn't supported.
 
   > [!IMPORTANT]
   > Automatic Zonal Allocation cannot be modified once enabled for a cache.