Updating based on comments

Author: Jake Willey

articles/cosmos-db/secure-access-to-data.md

@@ -43,7 +43,7 @@ Primary, secondary, read only, and read-write master keys can be retrieved and r
 The process of rotating your master key is simple. 
 
 1. Navigate to the Azure portal to retrieve your secondary key.
-2. Replace your primary key with your secondary key in your application.
+2. Replace your primary key with your secondary key in your application. Make sure that all the Cosmos DB clients across all the deployments are promptly restarted and will start using the updated key.
 3. Rotate the primary key in the Azure portal.
 4. Validate the new primary key works against all resource. Key rotation process can take any where from less than a minute to hours depending on the size of the Cosmos DB account.
 5. Replace the secondary key with the new primary key.

articles/cosmos-db/troubleshoot-dot-net-sdk.md

@@ -106,7 +106,7 @@ If you received the following error message: "The MAC signature found in the HTT
    1. 401 MAC signature issue is seen shortly after a container creation, and only occur until the container creation is completed.
 
  ### HTTP Error 400. The size of the request headers is too long.
- The size of the header has grown to large and is exceeding the maximum allowed size. It's always recommended to use the latest SDK. Make sure to use at least version [2.9.3](https://github.com/Azure/azure-cosmos-dotnet-v2/blob/master/changelog.md#-293) or [3.5.1](https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/changelog.md#-351---2019-12-11), which adds header size tracing to the exception message.
+ The size of the header has grown to large and is exceeding the maximum allowed size. It's always recommended to use the latest SDK. Make sure to use at least version [3.x](https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/changelog.md) or [2.x](https://github.com/Azure/azure-cosmos-dotnet-v2/blob/master/changelog.md), which adds header size tracing to the exception message.
 
 Causes:
  1. The session token has grown to large. The session token grows as the number of partitions increase in the container.