Merge pull request #251226 from seesharprun/rework-mongodb-toc-introduction

Cosmos DB | Last-minute MongoDB fixes

Author: PMEds28

articles/cosmos-db/.openpublishing.redirection.cosmos-db.json

@@ -6161,9 +6161,9 @@
       "redirect_document_id": false
     },
     {
-      "source_path_from_root": "/articles/cosmos-db/mongodb/introduction.md",
-      "redirect_url": "/azure/cosmos-db/mongodb/ru/introduction",
-      "redirect_document_id": true
+      "source_path_from_root": "/articles/cosmos-db/mongodb/overview.md",
+      "redirect_url": "/azure/cosmos-db/mongodb/introduction",
+      "redirect_document_id": false
     }
   ]
 }

articles/cosmos-db/mongodb/TOC.yml

@@ -1,5 +1,5 @@
 - name: What is Azure Cosmos DB for MongoDB?
-  href: overview.md
+  href: introduction.md
 - name: Choose your model
   href: choose-model.md
 - name: Comparing MongoDB Atlas

articles/cosmos-db/mongodb/choose-model.md

@@ -33,7 +33,7 @@ Here are a few key factors to help you decide which is the right option for you.
 ### Choose vCore-based if
 
 - You're migrating (lift & shift) an existing MongoDB workload or building a new MongoDB application.
-- Your workload has more point reads (fetching a single item by its ID and shard key value) and few long-running queries and complex aggregation pipeline operations.
+- Your workload has more long-running queries, complex aggregation pipelines, distributed transactions, joins, etc.
 - You prefer high-capacity vertical and horizontal scaling with familiar vCore-based cluster tiers such as M30, M40, M50 and more.
 - You're running applications requiring 99.995% availability.