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

Co-Authored-By: Matias Quaranta <[email protected]>

Author: j82w

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

@@ -98,7 +98,7 @@ The [query metrics](sql-api-query-metrics.md) will help determine where the quer
 ### The MAC signature found in the HTTP request is not the same as the computed signature
 If you received the following error message: "The MAC signature found in the HTTP request is not the same as the computed signature." it can be caused by the following scenarios.
 
-1. The key was rotated and did not follow the [best practices](secure-access-to-data.md#key-rotation). This is usually the case. Comos DB account key rotation can take anywhere from a few seconds to possibly days depending on the Cosmos DB account size.
+1. The key was rotated and did not follow the [best practices](secure-access-to-data.md#key-rotation). This is usually the case. Cosmos DB account key rotation can take anywhere from a few seconds to possibly days depending on the Cosmos DB account size.
    1. 401 MAC signature is seen shortly after a key rotation and eventually stops without any changes. 
 2. The key is misconfigured on the application so the key does not match the account. For instance cases where the key is read from a file and localization is not taken in consideration.
    1. 401 MAC signature issue will be consistent and happens for all calls
@@ -124,4 +124,4 @@ Solution:
 [Request rate too large]: #request-rate-too-large
 [Request Timeouts]: #request-timeouts
 [Azure SNAT (PAT) port exhaustion]: #snat
-[Production check list]: #production-check-list
+[Production check list]: #production-check-list