Skip to content

Commit 4e7d3dc

Browse files
authored
Fixing image display
1 parent 0c61ad7 commit 4e7d3dc

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/cosmos-db/mongodb-mongoose.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Let's create a Cosmos account. If you already have an account you want to use, y
3434
In this application we will cover two ways of creating your collections on Cosmos DB:
3535
- **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.
3636

37-
![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]
37+
![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][dbleveltp]
3838

3939
- **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.
4040

@@ -319,3 +319,4 @@ As you can see, it is easy to work with Mongoose discriminators. So, if you have
319319

320320
[alldata]: ./media/mongodb-mongoose/mongo-collections-alldata.png
321321
[multiple-coll]: ./media/mongodb-mongoose/mongo-mutliple-collections.png
322+
[dbleveltp]: ./media/mongodb-mongoose/db-level-throughput.png

0 commit comments

Comments
 (0)