Updated 04. Setting eShopOnContainer solution up in a Mac, VS for Mac or with CLI environment (dotnet CLI, Docker CLI and VS Code) (markdown)

04.-Setting-eShopOnContainer-solution-up-in-a-Mac,-VS-for-Mac-or-with-CLI-environment--(dotnet-CLI,-Docker-CLI-and-VS-Code).md

@@ -129,7 +129,7 @@ The first time you run this command it'll take some more additional time as it n
 
 It should take a few minutes to compile all the .NET Core projects plus the SPA application (Angular/TypeScript/JavaScript) which has additional processes and dependencies using NPM.
 
-- When the `docker-compose build` command finishes, you can check out with Docker CLI the images created by typing in the PowerShell console the command: 
+- When the `docker-compose build` command finishes, you can check out with Docker CLI the images created by typing in Bash the following Docker command: 
 
 `docker images`
 
@@ -156,7 +156,7 @@ Finally, you can see how the scripts waits after deploying all the containers:
 
 <img src="img/cli-windows/docker-compose-up-2.png">
 
-- <b>Check out the containers running in your Docker host</b>: Once docker-compose up finishes, you will have the original PowerShell window busy and showing the execution's output in a "wait state", so in order to ask to Docker about "how it went" and see what containers are running, you need to open a second PowerShell window and type "docker ps" so you'll see all the running containers, as shown in the following screenshot.
+- <b>Check out the containers running in your Docker host</b>: Once docker-compose up finishes, you will have the original bash window busy and showing the execution's output in a "wait state", so in order to ask to Docker about "how it went" and see what containers are running, you need to open a second bash window and type "docker ps" so you'll see all the running containers, as shown in the following screenshot.
 
 ![image](https://user-images.githubusercontent.com/1712635/34506448-9f08318a-efe1-11e7-8567-a15e307bb991.png)