Merge pull request #97969 from mohatb/patch-5

Update ingress-basic.md

Author: jborsecnik

articles/aks/ingress-basic.md

@@ -292,14 +292,15 @@ helm install nginx-ingress ingress-nginx/ingress-nginx `
 Check the load balancer service by using `kubectl get services`.
 
 ```console
-kubectl get services --namespace ingress-basic -o wide -w nginx-ingress-ingress-nginx-controller
+kubectl get services --namespace ingress-basic -o wide -w ingress-nginx-controller
 ```
 
 When the Kubernetes load balancer service is created for the NGINX ingress controller, an IP address is assigned under *EXTERNAL-IP*, as shown in the following example output:
 
 ```
 NAME                                     TYPE           CLUSTER-IP    EXTERNAL-IP     PORT(S)                      AGE   SELECTOR
-nginx-ingress-ingress-nginx-controller   LoadBalancer   10.0.74.133   EXTERNAL_IP     80:32486/TCP,443:30953/TCP   44s   app.kubernetes.io/component=controller,app.kubernetes.io/instance=nginx-ingress,app.kubernetes.io/name=ingress-nginx
+NAME                       TYPE           CLUSTER-IP    EXTERNAL-IP     PORT(S)                      AGE   SELECTOR
+ingress-nginx-controller   LoadBalancer   10.0.65.205   EXTERNAL-IP     80:30957/TCP,443:32414/TCP   1m   app.kubernetes.io/component=controller,app.kubernetes.io/instance=ingress-nginx,app.kubernetes.io/name=ingress-nginx
 ```
 
 No ingress rules have been created yet, so the NGINX ingress controller's default 404 page is displayed if you browse to the external IP address. Ingress rules are configured in the following steps.
@@ -545,9 +546,9 @@ nginx-ingress           ingress-basic   1               2020-01-06 19:55:46.3582
 Uninstall the releases with the `helm uninstall` command. The following example uninstalls the NGINX ingress deployment.
 
 ```
-$ helm uninstall nginx-ingress --namespace ingress-basic
+$ helm uninstall ingress-nginx --namespace ingress-basic
 
-release "nginx-ingress" uninstalled
+release "ingress-nginx" uninstalled
 ```
 
 Next, remove the two sample applications: