Added v4 perf tips links in troubleshooting

Author: anfeldma-ms

articles/cosmos-db/troubleshoot-java-sdk-v4-sql.md

@@ -23,7 +23,7 @@ Start with this list:
 
 * Take a look at the [Common issues and workarounds] section in this article.
 * Look at the Java SDK in the Azure Cosmos DB monorepo, which is available [open source on GitHub](https://github.com/Azure/azure-sdk-for-java/tree/master/sdk/cosmos/azure-cosmos). It has an [issues section](https://github.com/Azure/azure-sdk-for-java/issues) that's actively monitored. Check to see if any similar issue with a workaround is already filed. One helpful tip is to filter issues by the *cosmos:v4-item* tag.
-* Review the [performance tips for Java SDK v4](), and follow the suggested practices.
+* Review the [performance tips for Java SDK v4](performance-tips-java-sdk-v4-sql.md), and follow the suggested practices.
 * Read the rest of this article, if you didn't find a solution. Then file a [GitHub issue](https://github.com/Azure/azure-sdk-for-java/issues). If there is an option to add tags to your GitHub issue, add a *cosmos:v4-item* tag.
 
 ## <a name="common-issues-workarounds"></a>Common issues and workarounds
@@ -44,7 +44,7 @@ Run the following command.
 ```bash
 ulimit -a
 ```
-The number of max allowed open files, which are identified as "nofile," needs to be at least double your connection pool size. For more information, see [Performance tips]().
+The number of max allowed open files, which are identified as "nofile," needs to be at least double your connection pool size. For more information, see [Performance tips](performance-tips-java-sdk-v4-sql.md).
 
 ##### <a name="snat"></a>Azure SNAT (PAT) port exhaustion