diff --git a/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md b/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md
index 5615cc8..22a9d4c 100644
--- a/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md
+++ b/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md
@@ -60,7 +60,9 @@ Once Docker for Windows is installed in your machine, enter into its Settings an
 <img src="img/docker_settings.png">
 
 ### Share drives in Docker settings 
-This step is optional but recommended, as Docker sometimes needs to access the shared drives when building, depending on the actions. With the by default eShopOnContainers build process you don't need it, but if you were running a CI build container or Visual Studio, you might need it.
+This step is optional but recommended, as Docker sometimes needs to access the shared drives when building, depending on the build actions. 
+With the by default eShopOnContainers build process in the CLI, you don't need it.
+But if you were to use Visual Studio or to run a CI build container, it is mandatory to share the drive where your code resides.
 
 The drive you'll need to share depends on where you place your source code.