Fix broken links

Author: flang-msft

articles/azure-cache-for-redis/cache-development-faq.yml

@@ -51,7 +51,7 @@ sections:
           ### Timeout values
             * Consider your workload and set the values to match. If you're storing large values, set the timeout to a higher value.
             * Set `AbortOnConnectFail` to false and let StackExchange.Redis reconnect for you.
-            * Use a single, long-lived `ConnectionMultiplexer` instance rather than creating a new connection for each request. For an example of how to manage a connection, see the `RedisConnection`` class in [Connect to the cache with RedisConnection](cache-dotnet-how-to-use-azure-redis-cache.md#connect-to-the-cache-with-redisconnection).
+            * Use a single, long-lived `ConnectionMultiplexer` instance rather than creating a new connection for each request. 
             * Set the `ConnectionMultiplexer.ClientName` property to an app instance unique name for diagnostic purposes.
             * Use multiple `ConnectionMultiplexer` instances for custom workloads.
               * You can follow this model if you have varying load in your application. For example:

articles/azure-cache-for-redis/cache-how-to-scale.md

@@ -451,7 +451,7 @@ Clustering is only available for Premium, Enterprise, and Enterprise Flash cache
 
 ### I'm getting MOVE exceptions when using StackExchange.Redis and clustering, what should I do?
 
-If you're using StackExchange.Redis and receive `MOVE` exceptions when using clustering, ensure that you're using [StackExchange.Redis 1.1.603](https://www.nuget.org/packages/StackExchange.Redis/) or later. For instructions on configuring your .NET applications to use StackExchange.Redis, see [Configure the cache clients](cache-dotnet-how-to-use-azure-redis-cache.md#configure-the-cache-client).
+If you're using StackExchange.Redis and receive `MOVE` exceptions when using clustering, ensure that you're using [StackExchange.Redis 1.1.603](https://www.nuget.org/packages/StackExchange.Redis/) or later.
 
 ### What is the difference between OSS Clustering and Enterprise Clustering on Enterprise tier caches?
 

articles/azure-cache-for-redis/cache-management-faq.yml

@@ -39,7 +39,7 @@ sections:
           ### StackExchange.Redis best practices
 
           * Set `AbortConnect` to false, then let the ConnectionMultiplexer reconnect automatically.
-          * Use a single, long-lived `ConnectionMultiplexer` instance rather than creating a new connection for each request. For an example of how to manage a connection, see the `RedisConnection` class in [Connect to the cache with Redisconnection](cache-dotnet-how-to-use-azure-redis-cache.md#connect-to-the-cache-with-redisconnection).
+          * Use a single, long-lived `ConnectionMultiplexer` instance rather than creating a new connection for each request.
           * Redis works best with smaller values, so consider chopping up bigger data into multiple keys. In [this Redis discussion](https://groups.google.com/forum/#!searchin/redis-db/size/redis-db/n7aa2A4DZDs/3OeEPHSQBAAJ), 100 kb is considered large. For more information, see [Best practices development](cache-best-practices-development.md#consider-more-keys-and-smaller-values).
           * Configure your [ThreadPool settings](#important-details-about-threadpool-growth) to avoid timeouts.
           * Use at least the default connectTimeout of 5 seconds. This interval gives StackExchange.Redis sufficient time to re-establish the connection if there's a network blip.

articles/azure-cache-for-redis/cache-redis-samples.md

@@ -40,8 +40,6 @@ For more information, see the [StackExchange.Redis](https://github.com/StackExch
 
 [How to use Azure Cache for Redis with Python](cache-python-get-started.md) shows how to get started with Azure Cache for Redis using Python and the [redis-py](https://github.com/andymccurdy/redis-py) client.
 
-[Work with .NET objects in the cache](cache-dotnet-how-to-use-azure-redis-cache.md#work-with-net-objects-in-the-cache) shows you one way to serialize .NET objects to write them to and read them from an Azure Cache for Redis instance.
-
 ## Use Azure Cache for Redis as a Scale out Backplane for ASP.NET SignalR
 
 The [Use Azure Cache for Redis as a Scale out Backplane for ASP.NET SignalR](https://github.com/rustd/RedisSamples/tree/master/RedisAsSignalRBackplane) sample demonstrates how to use Azure Cache for Redis as a SignalR backplane. For more information about backplane, see [SignalR Scaleout with Redis](https://www.asp.net/signalr/overview/performance/scaleout-with-redis).

articles/azure-cache-for-redis/cache-web-app-cache-aside-leaderboard.md

@@ -406,7 +406,7 @@ It isn't required to store the team statistics in multiple formats in the cache
     }
     ```
 
-    The `GetFromList` method reads the team statistics from cache as a serialized `List<Team>`. If the statistics aren't present in the cache, a cache miss occurs. For a cache miss, the team statistics are read from the database and then stored in the cache for the next request. In this sample, JSON.NET serialization is used to serialize the .NET objects to and from the cache. For more information, see [How to work with .NET objects in Azure Cache for Redis](cache-dotnet-how-to-use-azure-redis-cache.md#work-with-net-objects-in-the-cache).
+    The `GetFromList` method reads the team statistics from cache as a serialized `List<Team>`. If the statistics aren't present in the cache, a cache miss occurs. For a cache miss, the team statistics are read from the database and then stored in the cache for the next request. In this sample, JSON.NET serialization is used to serialize the .NET objects to and from the cache.
 
     ```csharp
     List<Team> GetFromList()

articles/azure-cache-for-redis/managed-redis/managed-redis-development-faq.yml

@@ -48,7 +48,7 @@ sections:
           ### Timeout values
             * Consider your workload and set the values to match. If you're storing large values, set the timeout to a higher value.
             * Set `AbortOnConnectFail` to false and let StackExchange.Redis reconnect for you.
-            * Use a single, long-lived `ConnectionMultiplexer` instance rather than creating a new connection for each request. For an example of how to manage a connection, see the `RedisConnection`` class in [Connect to the cache with RedisConnection](../cache-dotnet-how-to-use-azure-redis-cache.md#connect-to-the-cache-with-redisconnection).
+            * Use a single, long-lived `ConnectionMultiplexer` instance rather than creating a new connection for each request.
             * Set the `ConnectionMultiplexer.ClientName` property to an app instance unique name for diagnostic purposes.
             * Use multiple `ConnectionMultiplexer` instances for custom workloads.
               * You can follow this model if you have varying load in your application. For example:

articles/azure-cache-for-redis/managed-redis/managed-redis-management-faq.yml

@@ -31,7 +31,7 @@ sections:
           ### StackExchange.Redis best practices
 
           * Set `AbortConnect` to false, then let the ConnectionMultiplexer reconnect automatically.
-          * Use a single, long-lived `ConnectionMultiplexer` instance rather than creating a new connection for each request. For an example of how to manage a connection, see the `RedisConnection` class in [Connect to the cache with Redisconnection](../cache-dotnet-how-to-use-azure-redis-cache.md#connect-to-the-cache-with-redisconnection).
+          * Use a single, long-lived `ConnectionMultiplexer` instance rather than creating a new connection for each request.
           * Redis works best with smaller values, so consider chopping up bigger data into multiple keys. In [the Redis discussion](https://groups.google.com/forum/#!searchin/redis-db/size/redis-db/n7aa2A4DZDs/3OeEPHSQBAAJ), 100 kb is considered large. For more information, see [Best practices development](managed-redis-best-practices-development.md#consider-more-keys-and-smaller-values).
           * Configure your [ThreadPool settings](#important-details-about-threadpool-growth) to avoid timeouts.
           * Use at least the default connectTimeout of 5 seconds. This interval gives StackExchange.Redis sufficient time to re-establish the connection if there's a network blip.