From f555a16653fc3ffcc2740ee7e705ddd144e7ae1c Mon Sep 17 00:00:00 2001 From: Stefan Scherer Date: Fri, 18 Dec 2020 17:27:16 +0100 Subject: [PATCH] Update get-started/nodejs/develop.md Co-authored-by: Usha Mandya <47779042+usha-mandya@users.noreply.github.com> --- get-started/nodejs/develop.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/get-started/nodejs/develop.md b/get-started/nodejs/develop.md index bec55644c7..6f094bf153 100644 --- a/get-started/nodejs/develop.md +++ b/get-started/nodejs/develop.md @@ -20,7 +20,7 @@ First, we’ll take a look at running a database in a container and how we use v Instead of downloading MongoDB, installing, configuring and then running the Mongo database as a service, we can use the Docker Official Image for MongoDB and run it in a container. -Before we run MongoDB in a container, we want to create a couple of volumes that Docker can manage to store our persistent data and configuration. I like to use the managed volumes feature that docker provides instead of using bind mounts. You can read all about volumes in our documentation. +Before we run MongoDB in a container, we want to create a couple of volumes that Docker can manage to store our persistent data and configuration. Let's use the managed volumes feature that docker provides instead of using bind mounts. You can read all about volumes in our documentation. Let’s create our volumes now. We’ll create one for the data and one for configuration of MongoDB.