Skip to content

Commit d2b07e6

Browse files
committed
fix broken header links
1 parent 798e9c9 commit d2b07e6

File tree

2 files changed

+7
-6
lines changed

2 files changed

+7
-6
lines changed

articles/cosmos-db/mongodb-mongoose.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@ ms.subservice: cosmosdb-mongo
66
ms.devlang: nodejs
77
ms.topic: conceptual
88
ms.date: 03/20/2020
9-
author: tisande
10-
ms.author: timsander1
9+
author: timsander1
10+
ms.author: tisande
1111
ms.custom: seodec18
1212
---
1313
# Connect a Node.js Mongoose application to Azure Cosmos DB

articles/cosmos-db/mongodb-post-migration.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,11 @@ ms.author: lbosq
1515
After you migrate the data stored in MongoDB database to Azure Cosmos DB's API for MongoDB, you can connect to Azure Cosmos DB and manage the data. This guide provides the steps you should consider after the migration. See the [Migrate MongoDB to Azure Cosmos DB's API for MongoDB tutorial](../dms/tutorial-mongodb-cosmos-db.md) for the migration steps.
1616

1717
In this guide, you will learn how to:
18-
- [Connect your application](#connect-account)
19-
- [Optimize the indexing policy](#indexing)
20-
- [Configure global distribution for Azure Cosmos DB's API for MongoDB](#distribute-data)
21-
- [Set consistency level](#consistency)
18+
19+
- [Connect your application](#connect-your-application)
20+
- [Optimize the indexing policy](#optimize-the-indexing-policy)
21+
- [Configure global distribution for Azure Cosmos DB's API for MongoDB](#globally-distribute-your-data)
22+
- [Set consistency level](#set-consistency-level)
2223

2324
> [!NOTE]
2425
> The only mandatory post-migration step on your application level is changing the connection string in your application to point to your new Azure Cosmos DB account. All other migration steps are recommended optimizations.

0 commit comments

Comments
 (0)