Update docs

Signed-off-by: nshankar <[email protected]>

Author: nshankar13

articles/aks/istio-about.md

@@ -50,19 +50,16 @@ Istio-based service mesh add-on for AKS currently has the following limitations:
 * The add-on doesn't support adding pods associated with virtual nodes to be added under the mesh.
 * The add-on doesn't support egress gateways for outbound traffic control.
 * The add-on doesn't support the sidecar-less Ambient dataplane mode.
-* The add-on doesn't support multi-cluster, multi-mesh, multi-cloud, or hybrid deployments.
-* The add-on restricts mesh-wide configuration options for the [Istio meshconfig][istio-meshconfig].
-* The add-on doesn't support static IP address, port, or other customizations for the [Istio add-on ingress gateways][istio-ingress].
+* The add-on doesn't support multi-cluster deployments.
 * Istio doesn't support Windows Server containers.
-* Customization of mesh through the following custom resources is blocked for now - `ProxyConfig, WorkloadEntry, WorkloadGroup, Telemetry, IstioOperator, WasmPlugin`. For `EnvoyFilter`, the add-on only supports customization of Lua script filters (`type.googleapis.com/envoy.extensions.filters.http.lua.v3.Lua`) - other `EnvoyFilter` types are currently blocked.
-
-* Gateway API for Istio ingress gateway or managing mesh traffic (GAMMA) are currently not yet supported with Istio addon.
+* Customization of mesh through the following custom resources is blocked for now - `ProxyConfig, WorkloadEntry, WorkloadGroup, Telemetry, IstioOperator, WasmPlugin`. For `EnvoyFilter`, the add-on only supports customization of Lua filters (`type.googleapis.com/envoy.extensions.filters.http.lua.v3.Lua`) - other `EnvoyFilter` types are currently blocked.
+* Gateway API for Istio ingress gateway or managing mesh traffic (GAMMA) are currently not yet supported with Istio addon. It's planned to allow customizations such as Static IP address in the Gateway API Istio implementation as part of the Istio add-on in future.
 
 ## Next steps
 
 ### Feedback and Feature Requests
 
-Feedback and feature requests for the Istio-based service mesh add-on should be raised as a new issue in the [AKS github repository][aks-gh-issues]. Please open a new issue with and add the `mesh` label. 
+Feedback and feature requests for the Istio-based service mesh add-on should be raised as a new issue in the [AKS github repository][aks-gh-issues]. Please open a new issue with the `mesh` label. 
 
 * [Deploy Istio-based service mesh add-on][istio-deploy-addon]
 * [Troubleshoot Istio-based service mesh add-on][istio-troubleshooting]

articles/aks/istio-deploy-addon.md

@@ -242,12 +242,11 @@ az group delete --name ${RESOURCE_GROUP} --yes --no-wait
 
 ### Feedback and Feature Requests
 
-Feedback and feature requests for the Istio-based service mesh add-on should be raised as a new issue in the [AKS github repository][aks-gh-issues]. Please open a new issue with and add the `mesh` label. 
+Feedback and feature requests for the Istio-based service mesh add-on should be raised as a new issue in the [AKS github repository][aks-gh-issues]. Please open a new issue and add the `mesh` label. 
 
 * [Deploy external or internal ingresses for Istio service mesh add-on][istio-deploy-ingress]
 * [Scale istiod and ingress gateway HPA][istio-scaling-guide]
 
-
 <!--- External Links --->
 [install-aks-cluster-istio-bicep]: https://github.com/Azure-Samples/aks-istio-addon-bicep
 [uninstall-istio-oss]: https://istio.io/latest/docs/setup/install/istioctl/#uninstall-istio

articles/aks/istio-deploy-ingress.md

@@ -17,7 +17,7 @@ This article shows you how to deploy external or internal ingresses for Istio se
 
 ## Prerequisites
 
-This guide assumes you followed the [documentation][istio-deploy-addon] to enable the Istio add-on on an AKS cluster, deploy a sample application and set environment variables.
+This guide assumes you followed the [documentation][istio-deploy-addon] to enable the Istio add-on on an AKS cluster, deploy sample applications, and set environment variables.
 
 ## Enable external ingress gateway
 
@@ -41,8 +41,7 @@ aks-istio-ingressgateway-external   LoadBalancer   10.0.10.249   <EXTERNAL_IP>
 ```
 
 > [!NOTE]
-> Customizations to IP address on internal and external gateways aren't supported yet. IP address customizations on the ingress are reverted back by the Istio add-on. 
-It's planned to allow these customizations in Gateway API Istio implementation as part of the Istio add-on in future.
+> Customizations to IP address on internal and external gateways aren't supported yet. IP address customizations on the ingress specifications are reverted back by the Istio add-on. It's planned to allow these customizations in Gateway API Istio implementation as part of the Istio add-on in future.
 
 Applications aren't accessible from outside the cluster by default after enabling the ingress gateway. To make an application accessible, map the sample deployment's ingress to the Istio ingress gateway using the following manifest:
 
@@ -129,7 +128,6 @@ Use `az aks mesh enable-ingress-gateway` to enable an internal Istio ingress on
 az aks mesh enable-ingress-gateway --resource-group $RESOURCE_GROUP --name $CLUSTER --ingress-gateway-type internal
 ```
 
-
 Use `kubectl get svc` to check the service mapped to the ingress gateway:
 
 ```bash
@@ -143,7 +141,7 @@ NAME                                TYPE           CLUSTER-IP    EXTERNAL-IP
 aks-istio-ingressgateway-internal   LoadBalancer   10.0.182.240  <IP>      15021:30764/TCP,80:32186/TCP,443:31713/TCP   87s
 ```
 
-Applications aren't mapped to the Istio ingress gateway after enabling the ingress gateway. Use the following manifest to map the sample deployment's ingress to the Istio ingress gateway:
+After enabling the ingress gateway, applications need to be exposed through the gateway and routing rules need to be configured accordingly. Use the following manifest to map the sample deployment's ingress to the Istio ingress gateway:
 
 ```bash
 kubectl apply -f - <<EOF
@@ -228,6 +226,12 @@ Confirm that the sample application's product page is accessible. The expected o
 
 ## Delete resources
 
+If you want to clean up the Istio external or internal ingresses, but leave the mesh enabled on the cluster, run the following command:
+
+```azure-cli-interactive
+az aks mesh disable-ingress-gateway --ingress-gateway-type <external/internal> --resource-group ${RESOURCE_GROUPS}
+```
+
 If you want to clean up the Istio service mesh and the ingresses (leaving behind the cluster), run the following command:
 
 ```azurecli-interactive