From c16b1120a09185bdb98099464b33ac95da0be748 Mon Sep 17 00:00:00 2001
From: Cesar De la Torre <cesardl@microsoft.com>
Date: Mon, 16 Oct 2017 14:38:54 -0700
Subject: [PATCH] Update readme.md

---
 .../servicefabric/WindowsContainers/readme.md | 27 ++++++++++++-------
 1 file changed, 17 insertions(+), 10 deletions(-)

diff --git a/deploy/az/servicefabric/WindowsContainers/readme.md b/deploy/az/servicefabric/WindowsContainers/readme.md
index 016279e0a..c995883dc 100644
--- a/deploy/az/servicefabric/WindowsContainers/readme.md
+++ b/deploy/az/servicefabric/WindowsContainers/readme.md
@@ -12,26 +12,33 @@ Within eShopOnContainers root folder, at the folder [..\deploy\az\servicefabric\
 Edit the following params in `servicefabricdeploy.parameters.json` file to set your values:
 
 - clusterName: Name of your SF cluster
+- clusterLocation: Datacenter location, like westus or westeurope
+- computeLocation: Datacenter location, like westus or westeurope
+- adminUserName: user-name for VMs administration
+- adminPassword: user-password for VMs administration
 - dnsName: Name assigned to your SF dns
-- adminUserName: user name for administration
-- adminPassword: user password for administration
 
-Optionally, you can modify which ports are opened in the LoadBalancer for accessing externally to the apps:
-
-- webMvcHttpPort: port externally exposed for the WebMVC app
-- webSpaHttpPort: port externally exposed for the WebSPA app
-- webStatusHttpPort: port externally exposed for the WebStatus app
-- IdSrvHttpRule: port externally exposed for the Identity app
+Optionally, you could modify which ports are opened in the LoadBalancer for the multiple eShopOnContainer apps and API services.
+By default, they are setup as:
+- webMvcHttpPort:       5100
+- webSpaHttpPort:       5104
+- webStatusHttpPort:    5107
+- IdSrvHttpRule:        5105
+- BasketApiHttpRule:    5103
+- CatalogApiHttpRule:   5101
+- OrderingApiHttpRule:  5102
+- MarketingApiHttpRule: 5110
+- LocationsApiHttpRule: 5109
 
 ## Deploy the template
 
 Once parameter file is edited you can deploy it using [create-resources script](../readme.md).
 
-i. e. if you are in windows, to deploy sql databases in a new resourcegroup located in westus, go to `deploy\az` folder and type:
-
+For example, to deploy the cluster to a new resourcegroup located in westus, go to `deploy\az` folder and type:
 ```
 create-resources.cmd servicefabric\WindowsContainers\servicefabricdeploy newResourceGroup -c westus
 ```
+
 ## Deploy eShopOnServiceFabric with Visual Studio.
 
 Alternatively, instead of using ARM templates, you can deploy eShop on service fabric directly by publishing the project eShopOnServiceFabric in eShopOnContainers-ServicesAndWebApps.sln with Visual Studio publish tool.