diff --git a/11.-Setting-the-solution-up-in-Service-Fabric.md b/11.-Setting-the-solution-up-in-Service-Fabric.md
index a5df593..de49a91 100644
--- a/11.-Setting-the-solution-up-in-Service-Fabric.md
+++ b/11.-Setting-the-solution-up-in-Service-Fabric.md
@@ -5,7 +5,7 @@ The ARM script will generate all the necessary Azure resources to publish eShopO
 
 Once the SF resources have been successfully created, the next step is to publish the SF projects. These projects are under the directory [SF Directory](https://github.com/dotnet-architecture/eShopOnContainers/tree/eShopOnServiceFabric-Win/ServiceFabric) and contains all the xml config files needed to configure and publish eShopOnContainers. SF is composed by 4 SF apps:
 
-<img src="eShopOnContainers/img/sf/sf-directory.PNG">
+<img src="https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/img/sf/sf-directory.PNG">
 
 - eShopOnServiceFabric: contains all the api services consumed by eShop.
 - eShopOnServiceFabricIdSrv: contains the Identity server for authentication.
@@ -15,26 +15,26 @@ Once the SF resources have been successfully created, the next step is to publis
 
 Before deploying, replace **ALL** the external urls in the cloud.xml config file of each SF app which reference the SF dns name with the dns name of your SF. Example:
 
-<img src="img/sf/cloud-config.png">
+<img src="https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/img/sf/cloud-config.png">
 
-<img src="img/sf/cloud-config-idsrv.png">
+<img src="https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/img/sf/cloud-config-idsrv.png">
 
-<img src="img/sf/cloud-config-spa.png">
+<img src="https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/img/sf/cloud-config-spa.png">
 
-<img src="img/sf/cloud-config-mvc.png">
+<img src="https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/img/sf/cloud-config-mvc.png">
 
 To deploy the SF apps, open the eShopOnContainers-ServicesAndWebApps.sln with vs2017 (Service Fabric SDK installation must be installed) and right-click on each SF project selecting the publish button. 
 
-<img src="img/sf/publish-button.png">
+<img src="https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/img/sf/publish-button.png">
 
 A new window will be prompted allowing you to select the SF cluster you have previously created.
 
-<img src="img/sf/publish-window.png">
+<img src="https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/img/sf/publish-window.png">
 
 Open the SF explorer page to check out the deployment and healthcheck status.
 
-<img src="img/sf/explorer-apps-status.png">
+<img src="https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/img/sf/explorer-apps-status.png">
 
-<img src="img/sf/explorer-deployment-status.png">
+<img src="https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/img/sf/explorer-deployment-status.png">
 
 ### - Deploying eShopOncontainers as Linux Containers to Azure Service Fabric (TBD)
\ No newline at end of file