From 6af37044805ff5616f1410a1d0271510ea5e705b Mon Sep 17 00:00:00 2001
From: jamesEmerson112 <36806380+jamesEmerson112@users.noreply.github.com>
Date: Mon, 26 Sep 2022 22:50:56 -0700
Subject: [PATCH 1/2] Update README.md

Adjusted some grammatical errors
---
 6-Docker_Compose_For_Multi-Container_Apps/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/6-Docker_Compose_For_Multi-Container_Apps/README.md b/6-Docker_Compose_For_Multi-Container_Apps/README.md
index 40ad53a7..b860c2ca 100644
--- a/6-Docker_Compose_For_Multi-Container_Apps/README.md
+++ b/6-Docker_Compose_For_Multi-Container_Apps/README.md
@@ -72,7 +72,7 @@ Luckily for you, this problem had already been solved for you before you even kn
 
 - [ ] Rather than spending forever talking about what Docker Compose does and why it's great, let's just dive into a demonstration. `cd` into the directory '/6-Docker_Compose_For_Multi-Container_Apps'
 
-- [ ] Run the command `ls` and notice that we have directories that contain the source code for the services of our polling app from the previous Module (the 'survey_server' and 'results_server'). Each of these directories contains it's own Dockerfile that defines the steps to build it's requisite image. This should all be familiar to you.
+- [ ] Run the command `ls` and notice that we have directories that contain the source code for the services of our polling app from the previous Module (the 'survey_server' and 'results_server'). Each of these directories contains its own Dockerfile that defines the steps to build its requisite image. This should all be familiar to you.
 
 - [ ] Also notice that there is a file in Module 6 that you may not be familiar with, the one named 'docker-compose.yml'. We'll dive into this shortly.
 

From 008c1675b71f41044018f78f4f49bd7a21da755c Mon Sep 17 00:00:00 2001
From: jamesEmerson112 <36806380+jamesEmerson112@users.noreply.github.com>
Date: Mon, 26 Sep 2022 22:55:15 -0700
Subject: [PATCH 2/2] Update README.md

Some features of mongo:4.x are deprecated in the latest version (the latest mongo promises request promise format instead of callback functions from index.js of both survey-server and results-server)
---
 5-Make_Multiple_Containers_Work_Together/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/5-Make_Multiple_Containers_Work_Together/README.md b/5-Make_Multiple_Containers_Work_Together/README.md
index 5be1d173..6075dbd2 100644
--- a/5-Make_Multiple_Containers_Work_Together/README.md
+++ b/5-Make_Multiple_Containers_Work_Together/README.md
@@ -89,13 +89,13 @@ Docker is the only thing you need from now on! So let's get started spinning the
 
 - [ ] Build your results server image and tag it with the name 'results' by running `docker build -t results .`
 
-- [ ] Pull down a MongoDB image by running `docker pull mongo:latest`
+- [ ] Pull down a MongoDB image by running `docker pull mongo:4.0`
 
 This saves us a lot of time - since we straight up just need a MongoDB database and don't need to configure it in any way we'll just pull the official image from Dockerhub. As with every other time you used the `docker pull` command it grabs the image from Dockerhub and caches it on your machine. This time is no different. However, the way you spin up the official MongoDB image is a little different than we are used to; let's check it out ->
 
 **Second:** Run the containers:
 
-- [ ] First, we'll spin up the MongoDB container. Run `docker run -d --name mongo mongo:latest`
+- [ ] First, we'll spin up the MongoDB container. Run `docker run -d --name mongo mongo:4.0`
 
 You might be wondering, **'Where's the -p port mapping option that we've used EVERY OTHER TIME?!?!?'**