Skip to content

Commit 63f363f

Browse files
authored
Formatting
1 parent 59a22d8 commit 63f363f

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/cosmos-db/mongodb-mongoose.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,10 @@ Let's create a Cosmos account. If you already have an account you want to use, y
3232

3333
### Create a database
3434
In this application we will cover two ways of creating your collections on Cosmos DB:
35-
- **Storing each object model in a separate collection**: We recommend [creating a database with dedicated throughput](set-throughput.md#set-throughput-on-a-database). Using this capacity model will give you better cost efficiency.
35+
- **Storing each object model in a separate collection**: We recommend [creating a database with dedicated throughput](set-throughput.md#set-throughput-on-a-database). Using this capacity model will give you better cost efficiency.
36+
3637
![Node.js tutorial - Screenshot of the Azure portal, showing how to create a database in the Data Explorer for an Azure Cosmos DB account, for use with the Mongoose Node module][db-level-throughput.png]
38+
3739
- **Storing all object models in a single Cosmos DB collection**: If you'd prefer to store all models in a single collection, you can just create a new database without selecting the Provision Throughput option. Using this capacity model will create each collection with its own throughput capacity for every object model.
3840

3941
After you create the database, you'll use the name in the `COSMOSDB_DBNAME` environment variable below.

0 commit comments

Comments
 (0)