template required changes

Author: flang-msft

articles/azure-cache-for-redis/cache-troubleshoot-timeouts.md

@@ -38,6 +38,8 @@ This section discusses troubleshooting for latency and timeout issues that occur
 
 ## Client-side troubleshooting
 
+Here's the client-side troubleshooting.
+
 ### Traffic burst and thread pool configuration
 
 Bursts of traffic combined with poor `ThreadPool` settings can result in delays in processing data already sent by the Redis server but not yet consumed on the client side. Check the metric "Errors" (Type: UnresponsiveClients) to validate if your client hosts can keep up with a sudden spike in traffic.
@@ -117,6 +119,8 @@ If you're using `RedisSessionStateProvider`, ensure you set the retry timeout co
 
 ## Server-side troubleshooting
 
+Here's the server-side troubleshooting.
+
 ### Server maintenance
 
 Planned or unplanned maintenance can cause disruptions with client connections. The number and type of exceptions depends on the location of the request in the code path, and when the cache closes its connections. For instance, an operation that sends a request but doesn't receive a response when the failover occurs might get a time-out exception. New requests on the closed connection object receive connection exceptions until the reconnection happens successfully.