diff --git a/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md b/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md
index 4655cd1..77ebf64 100644
--- a/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md
+++ b/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md
@@ -122,7 +122,10 @@ At this point, after waiting sometime for the Nuget packages to be properly rest
 
 <img src="img/vs2017/debug-F5-button.png">
 
-VS 2017 should compile the .NET projects, then create the Docker images and finally deploy the containers in the Docker host (your by default Linux VM in Docker for Windows). Finally, because the docker-compose configuration project is configured to open the MVC application, it should open your by default browser and show the MVC application with data coming from the microservices/containers:
+VS 2017 should compile the .NET projects, then create the Docker images and finally deploy the containers in the Docker host (your by default Linux VM in Docker for Windows). 
+Note that the first time you hit F5 it'll take more time, a few minutes at least, because in addition to compile your bits, it needs to pull/download the base images (SQL for Linux Docker Image, Redis Image, ASPNET image, etc.) and register them in the local image repo of your PC. The next time you hit F5 it'll be much faster.
+
+Finally, because the docker-compose configuration project is configured to open the MVC application, it should open your by default browser and show the MVC application with data coming from the microservices/containers:
 <img src="img/vs2017/vs2017-f5-with-eshoponcontainers-web-mvc-in-browser.png">
 
 Here's how the docker-compose configuration project is configured to open the MVC application: