diff --git a/deploy/az/servicefabric/WindowsContainers/readme.md b/deploy/az/servicefabric/WindowsContainers/readme.md
index 2cc4d9334..1cb69f943 100644
--- a/deploy/az/servicefabric/WindowsContainers/readme.md
+++ b/deploy/az/servicefabric/WindowsContainers/readme.md
@@ -1,4 +1,7 @@
-# Deploying a Service Fabric cluster based on Windows nodes (No Secured)
+# Deploying a Service Fabric cluster based on Windows nodes 
+
+## A. Not secured cluster (SF Windows cluster)
+For a secured cluster, see option B. below.
 You can always deploy a SF cluster through the Azure portal, as explained in this article: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started-azure-cluster
 
 However, when creating a cluster, there are quite a few configurations to take into account, like enabling the internal DNS service or Reverse Proxy service, choosing between Linux/Windows, open/publish your application ports in the load-balancer and most of all (the most complex setup) how to create a secure cluster.
@@ -43,7 +46,7 @@ create-resources.cmd servicefabric\WindowsContainers\servicefabricdeploy qa-esho
 
 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.
 
-# Deploying Azure Service Fabric (Secured)
+## B. Secured cluster (SF Windows cluster)
 
 The ARM template `servicefabricdeploysecured.json` and its parameter file (`servicefabricdeploysecured.parameters.json`) are used to create a service fabric cluster environment for windows containers secured with a certificate.