Skip to content

Commit 5baa254

Browse files
Update feature-support-40.md
1 parent d21a422 commit 5baa254

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/cosmos-db/mongodb/feature-support-40.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about Azure Cosmos DB's API for MongoDB 4.0 server version su
44
ms.service: cosmos-db
55
ms.subservice: cosmosdb-mongo
66
ms.topic: overview
7-
ms.date: 08/26/2021
7+
ms.date: 04/05/2022
88
author: gahl-levy
99
ms.author: gahllevy
1010
---
@@ -577,5 +577,5 @@ Some applications rely on a [Write Concern](https://docs.mongodb.com/manual/refe
577577
- Learn how to [use Robo 3T](connect-using-robomongo.md) with Azure Cosmos DB's API for MongoDB.
578578
- Explore MongoDB [samples](nodejs-console-app.md) with Azure Cosmos DB's API for MongoDB.
579579
- Trying to do capacity planning for a migration to Azure Cosmos DB? You can use information about your existing database cluster for capacity planning.
580-
- If all you know is the number of vcores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](../convert-vcore-to-request-unit.md)
580+
- If all you know is the number of vCores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](../convert-vcore-to-request-unit.md)
581581
- If you know typical request rates for your current database workload, read about [estimating request units using Azure Cosmos DB capacity planner](estimate-ru-capacity-planner.md)

0 commit comments

Comments
 (0)