Acrolinx and other edits

Author: flang-msft

articles/azure-cache-for-redis/cache-best-practices-enterprise-tiers.md

@@ -43,7 +43,7 @@ The tables show the number of vCPUs used for the primary shards, not the replica
 ### E10
 
 |Capacity|Effective vCPUs|
-|---|---:|
+|---:|---:|
 | 2 | 2 |
 | 4 | 6 |
 | 6 | 6 |
@@ -53,7 +53,7 @@ The tables show the number of vCPUs used for the primary shards, not the replica
 
 ### E20
 |Capacity|Effective vCPUs|
-|---|---|
+|---:|---:|
 |2| 2|
 |4|6|
 |6|6|
@@ -63,7 +63,7 @@ The tables show the number of vCPUs used for the primary shards, not the replica
 ### E50
 
 |Capacity|Effective vCPUs|
-|---|---|
+|---:|---:|
 |2|6|
 |4|6|
 |6|6|
@@ -73,7 +73,7 @@ The tables show the number of vCPUs used for the primary shards, not the replica
 
 ### E100
 |Capacity|Effective vCPUs|
-|---|---|
+|---:|---:|
 |2| 6|
 |4|30|
 |6|30|
@@ -82,13 +82,13 @@ The tables show the number of vCPUs used for the primary shards, not the replica
 
 ### F300
 |Capacity|Effective vCPUs|
-|---|---|
+|---:|---:|
 |3| 6|
 |9|30|
 
 ### F700
 |Capacity|Effective vCPUs|
-|---|---|
+|---:|---:|
 |3| 30|
 |9| 30|
 
@@ -122,19 +122,21 @@ For example, consider these tips:
 
 - Identify in advance which other cache in the geo-replication group to switch over to if a region goes down.
 - Ensure that firewalls are set so that any applications and clients can access the identified backup cache.
-- Each cache in the geo-replication group has its own access key. Determine how the application switches access keys when targeting a backup cache. 
+- Each cache in the geo-replication group has its own access key. Determine how the application will switch access keys when targeting a backup cache. 
 - If a cache in the geo-replication group goes down, a buildup of metadata starts to occur in all the caches in the geo-replication group. The metadata can't be discarded until writes can be synced again to all caches. You can prevent the metadata build-up by force unlinking the cache that is down. Consider monitoring the available memory in the cache and unlinking if there's memory pressure, especially for write-heavy workloads.
 <!-- My revision - should the last sentence be its own bullet?  -->
 
-It's also possible to use a [circuit breaker pattern](/azure/architecture/patterns/circuit-breaker) to automatically redirect traffic away from a cache suffering a region outage and towards a backup cache in the same geo-replication group. Use Azure services such as [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md) or [Azure Load Balancer](../load-balancer/load-balancer-overview.md) to enable the redirection.
+It's also possible to use a [circuit breaker pattern](/azure/architecture/patterns/circuit-breaker). Use the pattern to automatically redirect traffic away from a cache experiencing a region outage, and towards a backup cache in the same geo-replication group. Use Azure services such as [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md) or [Azure Load Balancer](../load-balancer/load-balancer-overview.md) to enable the redirection.
 
 ## Data Persistence vs Data Backup
 
 The [data persistence](cache-how-to-premium-persistence.md) feature in the Enterprise and Enterprise Flash tiers is designed to automatically provide a quick recovery point for data when a cache goes down. The quick recovery is made possible by storing the RDB or AOF file in a managed disk that is mounted to the cache instance. Persistence files on the disk aren't accessible to users.
 
-Many customers want to use persistence to take periodic backups of the data on their cache. While this is a great idea, data persistence isn’t recommended to be used in this way. Instead, use the [import/export](cache-how-to-import-export-data.md) feature. You can export copies of cache data in RDB format directly into your chosen storage account and trigger the data export as frequently as you require. Export can be triggered either from the portal or by using the CLI, PowerShell, or SDK tools. 
+Many customers want to use persistence to take periodic backups of the data on their cache. We don't recommend that you use data persistence in this way. Instead, use the [import/export](cache-how-to-import-export-data.md) feature. You can export copies of cache data in RDB format directly into your chosen storage account and trigger the data export as frequently as you require. Export can be triggered either from the portal or by using the CLI, PowerShell, or SDK tools. 
 
-<!-- Not sure about this sentence - While this is a great idea, data persistence isn’t recommended to be used in this way. Instead, use the [import/export](cache-how-to-import-export-data.md) feature. -->
+<!-- Not sure about this sentence - While this is a great idea, data persistence isn’t recommended to be used in this way. Instead, use the [import/export](cache-how-to-import-export-data.md) feature. 
+It's a great idea but don't do it? See my revision.
+-->
 
 ## Next steps