From db293a4325685d0486b115ca000a02a9f915eb3f Mon Sep 17 00:00:00 2001 From: Stefan Scherer Date: Fri, 18 Dec 2020 17:27:06 +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 628877f548..bec55644c7 100644 --- a/get-started/nodejs/develop.md +++ b/get-started/nodejs/develop.md @@ -18,7 +18,7 @@ In this module, we’ll walk through setting up a local development environment First, we’ll take a look at running a database in a container and how we use volumes and networking to persist our data and allow our application to talk with the database. Then we’ll pull everything together into a compose file which will allow us to setup and run a local development environment with one command. Finally, we’ll take a look at connecting a debugger to our application running inside a container. -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. +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.