edit

dlepow · dlepow · commit 1a04dac4b502 · 2026-03-11T17:58:23.000-07:00
diff --git a/articles/redis/architecture.md b/articles/redis/architecture.md
@@ -131,7 +131,7 @@ This table shows a general example of the relationship of _Size_ to _vCPUs/prima
 
 You can run without high availability (HA) mode enabled. This configuration means that your Redis instance doesn't have replication enabled and doesn't have access to the availability SLA. Don't run in non-HA mode outside of development and test scenarios. You can't disable high availability in an instance that you already created. You can enable high availability in an instance that doesn't have it. Because an instance running without high availability uses fewer VMs and nodes, vCPUs aren't used as efficiently, so performance might be lower.
 
-When you enable HA mode, your instance is deployed with primary and replica shards distributed across at least two nodes. This configuration is recommended for all production scenarios and for access to the availability SLA. In regions that support availability zones, Azure Managed Redis distributes the nodes across zones by default. In regions without availability zones, the primary and replica shards are distributed across at least two nodes in the same zone. For more information, see [Reliability in Azure Managed Redis](/azure/reliability/reliability-managed-redis).
+When you enable HA mode, your instance is deployed with primary and replica shards distributed across at least two nodes. This configuration is recommended for all production scenarios and for access to the availability SLA. In regions that support availability zones, Azure Managed Redis distributes the nodes across zones by default. For more information, see [Reliability in Azure Managed Redis](/azure/reliability/reliability-managed-redis).
 
 ## Reserved memory
 
diff --git a/articles/redis/overview.md b/articles/redis/overview.md
@@ -101,8 +101,6 @@ The following table helps describe some of the features supported by tier:
 
 In regions that support availability zones, Azure Managed Redis distributes the nodes across zones by default. For more information, see [Reliability in Azure Managed Redis](/azure/reliability/reliability-managed-redis). 
 
-In regions without availability zones, the primary and replica shards are distributed across at least two nodes in the same zone. 
-
 > [!IMPORTANT]
 > The Balanced B0 and B1 SKU options don't support active geo-replication.
 >

Original file line number	Diff line number	Diff line change
`@@ -101,8 +101,6 @@ The following table helps describe some of the features supported by tier:`
`101`	`101`
`102`	`102`	`In regions that support availability zones, Azure Managed Redis distributes the nodes across zones by default. For more information, see [Reliability in Azure Managed Redis](/azure/reliability/reliability-managed-redis).`
`103`	`103`
`104`		`-In regions without availability zones, the primary and replica shards are distributed across at least two nodes in the same zone.`
`105`		`-`
`106`	`104`	`> [!IMPORTANT]`
`107`	`105`	`> The Balanced B0 and B1 SKU options don't support active geo-replication.`
`108`	`106`	`>`