Apply suggestions from code review

Co-authored-by: Matias Quaranta <[email protected]>
Co-authored-by: Courtney Wales <[email protected]>

Author: 3 people

articles/cosmos-db/nosql/troubleshoot-bad-request.md

@@ -47,15 +47,15 @@ A response with this error means you are executing an operation and passing a pa
 ### Solution
 Send the partition key value parameter that matches the document property value.
 
-## <a name="partition-key-value-precision-loss"></a>Numeric partition key value precision loss
+## Numeric partition key value precision loss
 On this scenario, it's common to see errors like:
 
 *The requested partition key is out of key range, possibly because of loss of precision of partition key value*
 
-A response with this error is likely to be caused by an operation on a document with a numeric partition key whose value is outside what is supported by Azure Cosmos DB. Refer [Per-item limits](https://learn.microsoft.com/en-us/azure/cosmos-db/concepts-limits#per-item-limits) for the maximum length of numeric property value.
+A response with this error is likely to be caused by an operation on a document with a numeric partition key whose value is outside what is supported by Azure Cosmos DB. Refer [Per-item limits](/azure/cosmos-db/concepts-limits#per-item-limits) for the maximum length of numeric property value.
 
 ### Solution
-Consider using type `string` for partition key.
+Consider using type `string` for partition key if requiring precise numeric values.
 
 ## Next steps
 * [Diagnose and troubleshoot](troubleshoot-dotnet-sdk.md) issues when you use the Azure Cosmos DB .NET SDK.