diff --git a/10.-Setting-the-solution-up-in-AKS-(Azure-Kubernetes-Service).md b/10.-Setting-the-solution-up-in-AKS-(Azure-Kubernetes-Service).md
index 1476d5f..364a078 100644
--- a/10.-Setting-the-solution-up-in-AKS-(Azure-Kubernetes-Service).md
+++ b/10.-Setting-the-solution-up-in-AKS-(Azure-Kubernetes-Service).md
@@ -202,11 +202,17 @@ In order to see your ACR credentials type:
 Keep those credentials in a safe place.
 
 
-# Deploy the eShopOnContainers application into the Kuberentes cluster with the deployment script
+# Deploy the nginx-ingress and eShopOnContainers application into the Kuberentes cluster with deployment scripts
 
-1. Open a PowerShell command line at the `k8s` directory of your local eShopOnContainers repository.
-1. Ensure `docker`, `docker-compose`, and `kubectl` are on the path, and configured for your Docker machine and Kubernetes cluster.
-1. Just the first time you deploy into the cluster, you need to deploy the nginx-ingress tier with two scripts:
+- Open a PowerShell command line at the `k8s` directory of your local eShopOnContainers repository.
+- Ensure `docker`, `docker-compose`, and `kubectl` are on the path, and configured for your Docker machine and Kubernetes cluster.
+
+### Setup the nginx-ingress
+
+Just the first time you deploy eShopOnContainers into the cluster, you need to deploy the nginx-ingress tier with two scripts.
+
+None of these PowerShell scripts accept any parameter. 
+The first script creates the generic nginx-ingress resources and the second script creates specific resources for using nginx-ingress under Azure AKS.
 
 Run first script for ingress:
 >```
@@ -214,13 +220,21 @@ Run first script for ingress:
 >```
 ![image](https://user-images.githubusercontent.com/1712635/40210019-942b7292-59f7-11e8-8a41-94b67cb8f57e.png)
 
-Run second script for ingress (it has several patches related to Azure):
+Run second script for ingress:
 >```
 >./deploy-ingress-azure.ps1
 >```
 ![image](https://user-images.githubusercontent.com/1712635/40210064-c79f3834-59f7-11e8-8f03-b4b1c1ec9a24.png)
 
-**IMPORTANT** - You need to wait for a while until the ingress tiers are created before trying to deploy the application containers. Other than that you will still get the error "Must install ingress first - Run deploy-ingress.ps1 and  deploy-ingress-azure.ps1".
+To ensure that everything is installed you can type `kubectl get services -n ingress-nginx`. Output should be something like:
+
+```
+NAME                   TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)                      AGE
+default-http-backend   ClusterIP      10.0.200.205   <none>          80/TCP                       2h
+ingress-nginx          LoadBalancer   10.0.52.205    xx.xx.xx.xx     80:31608/TCP,443:32518/TCP   2h
+```
+>**IMPORTANT**: The EXTERNAL-IP of the ingress-nginx takes a few minutes to appear. This will be the external IP of the cluster.
+You also need to wait for a while until the ingress tiers are created before trying to deploy the application containers. Other than that you will still get the error "Must install ingress first - Run deploy-ingress.ps1 and  deploy-ingress-azure.ps1".
 
 Errors if ingresses are still not available:
 ![image](https://user-images.githubusercontent.com/1712635/40210277-df007906-59f8-11e8-88c6-a6044eb61844.png)