diff --git a/04.-Setting-eShopOnContainer-solution-up-in-a-Mac,-VS-for-Mac-or-with-CLI-environment--(dotnet-CLI,-Docker-CLI-and-VS-Code).md b/04.-Setting-eShopOnContainer-solution-up-in-a-Mac,-VS-for-Mac-or-with-CLI-environment--(dotnet-CLI,-Docker-CLI-and-VS-Code).md
index d611c55..2d0fc4a 100644
--- a/04.-Setting-eShopOnContainer-solution-up-in-a-Mac,-VS-for-Mac-or-with-CLI-environment--(dotnet-CLI,-Docker-CLI-and-VS-Code).md
+++ b/04.-Setting-eShopOnContainer-solution-up-in-a-Mac,-VS-for-Mac-or-with-CLI-environment--(dotnet-CLI,-Docker-CLI-and-VS-Code).md
@@ -231,11 +231,16 @@ You could generate the binaries manually, with 'dotnet publish', but for your co
  In addition, it runs the client build commands using *npm* to build the SPA application
  assets. Finally, it will remove old docker containers and images.
 
-After you've finished the build, you can create the Docker images defined at the docker-compose.yml file by using `docker-compose build`:
+After you've finished the build, you can create the Docker images defined at the docker-compose.yml file within the solution's root directory, by using `docker-compose build`:
+
+First, move to the solution's root directory with `cd ..`
+
+Check that you are in the folder where the docker-compose.yml files are, and finally run the following command:
 
 ```bash
 $ docker-compose build
 ```
+If you now run `$ docker images` you'll see the eShopOnContainers images are now ready to be used by Docker.
 
 To run the containers, you use `docker-compose up` again: