Fixed broken link

Author: flang-msft

articles/redis/best-practices-managed-cache.md

@@ -15,7 +15,7 @@ Here are some best practices for Azure Managed Redis.
 
 ## Zone redundancy
 
-We strongly recommend that you deploy new caches in a [zone redundant](high-availability.md) configuration. Zone redundancy ensures that Redis Enterprise nodes are spread among three availability zones, boosting redundancy from data center-level outages. Using zone redundancy increases availability. For more information, see [Service Level Agreements (SLA) for Online Services](https://azure.microsoft.com/support/legal/sla/cache/v1_1/).
+We strongly recommend that you deploy new caches in a zone redundant configuration. Zone redundancy ensures that Redis Enterprise nodes are spread among three availability zones, boosting redundancy from data center-level outages. Using zone redundancy increases availability. For more information, see [Service Level Agreements (SLA) for Online Services](https://azure.microsoft.com/support/legal/sla/cache/v1_1/).
 
 Zone redundancy is important on the Enterprise tier because your cache instance always uses at least three nodes. Two nodes are data nodes, which hold your data, and a _quorum node_. Increasing capacity scales the number of data nodes in even-number increments.
 

articles/redis/how-to-active-geo-replication.md

@@ -262,4 +262,3 @@ Manage access to the feature using [Azure role-based access control](/azure/role
 ## Next steps
 
 - [Azure Managed Redis service tiers](overview.md#choosing-the-right-tier)
-- [High availability for Azure Cache for Redis](high-availability.md)

articles/redis/how-to-persistence.md

@@ -11,7 +11,7 @@ ms.custom:
 ---
 # Configure data persistence (preview) for an Azure Managed Redis instance
 
-[Redis persistence (preview)](https://redis.io/topics/persistence) allows you to persist data stored in cache instance. If there's a hardware failure, the cache instance is rehydrated with data from the persistence file when it comes back online. The ability to persist data is an important way to boost the durability of a cache instance because all cache data is stored in memory. Data loss is possible if a failure occurs when cache nodes are down. Persistence should be a key part of your [high availability and disaster recovery](high-availability.md) strategy with Azure Managed Redis.
+[Redis persistence (preview)](https://redis.io/topics/persistence) allows you to persist data stored in cache instance. If there's a hardware failure, the cache instance is rehydrated with data from the persistence file when it comes back online. The ability to persist data is an important way to boost the durability of a cache instance because all cache data is stored in memory. Data loss is possible if a failure occurs when cache nodes are down. Persistence should be a key part of your high availability and disaster recovery strategy with Azure Managed Redis.
 
 > [!IMPORTANT]
 >
@@ -187,4 +187,3 @@ For more information on scaling, see [What happens if I've scaled to a different
 
 - [Azure Managed Redis service tiers](overview.md#choosing-the-right-tier)
 - [Export data from Azure Managed Redis](how-to-import-export-data.md)
-- [High availability and disaster recovery](high-availability.md)

articles/redis/index.yml

@@ -87,8 +87,6 @@ landingContent:
            url: how-to-redis-cli-tool.md
       - linkListType: concept
         links:
-         - text: High availability
-           url: high-availability.md
          - text: Storing embeddings vectors and performing vector similarity search
            url: overview-vector-similarity.md
          - text: Redis modules

articles/redis/troubleshoot-connectivity.md

@@ -90,4 +90,3 @@ If you've configured any networking or security resource to use your cache's pub
 ## Related content
 
 - [Best practices for connection resilience](best-practices-connection.md)
-- [High availability for Azure Managed Redis](high-availability.md)