Istio addon - address acrolinx and blocked configs

Author: shashankbarsin

articles/aks/istio-about.md

@@ -36,7 +36,7 @@ This service mesh add-on uses and builds on top of open-source Istio. The add-on
 
 * Istio versions are tested and verified to be compatible with supported versions of Azure Kubernetes Service.
 * Scaling of Istio control plane configured and handled by Microsoft.
-* Adjust configuration of AKS components like `coredns` when Istio is enabled.
+* Adjust scaling of AKS components like `coredns` when Istio is enabled.
 * Verified external and internal ingress set-up.
 * Verified to work with [Azure Monitor managed service for Prometheus][managed-prometheus-overview] and [Azure Managed Grafana][managed-grafana-overview].
 * Official Azure support provided for the add-on.
@@ -49,6 +49,7 @@ Istio-based service mesh add-on for AKS has the following limitations:
 * The add-on doesn't work on AKS clusters that are using [Open Service Mesh addon for AKS][open-service-mesh-about].
 * The add-on doesn't work on AKS clusters that have Istio installed on them already outside the add-on installation.
 * Istio doesn't support Windows Server containers.
+* Customization of mesh based on the following custom resources is blocked for now - `EnvoyFilter, ProxyConfig, WorkloadEntry, WorkloadGroup, Telemetry, IstioOperator, WasmPlugin`
 
 ## Next steps
 

articles/aks/istio-deploy-addon.md

@@ -46,7 +46,7 @@ az extension update --name aks-preview
 
 ### Register the _AzureServiceMeshPreview_ feature flag
 
-Register the `AzureServiceMeshPreview` feature flag by using the [az feature register][az-feature-register] command below:
+Register the `AzureServiceMeshPreview` feature flag by using the [az feature register][az-feature-register] command:
 
 ```azurecli-interactive
 az feature register --namespace "Microsoft.ContainerService" --name "AzureServiceMeshPreview"
@@ -212,9 +212,9 @@ az aks mesh disable --resource-group ${RESOURCE_GROUP} --name ${CLUSTER}
 > [!CAUTION]
 > Disabling the service mesh addon will completely remove the Istio control plane from the cluster.
 
-Note that Istio CRDs will not be deleted by default. To clean up CRDs, use:
+Istio `CustomResourceDefintion`s (CRDs) won't be deleted by default. To clean them up, use:
 
-```azurecli-interactive
+```bash
 kubectl delete crd $(kubectl get crd -A | grep "istio.io" | awk '{print $1}')
 ```
 

articles/aks/istio-deploy-ingress.md

@@ -31,7 +31,7 @@ Use `kubectl get svc` to check the service mapped to the ingress gateway:
 kubectl get svc aks-istio-ingressgateway-external -n aks-istio-ingress
 ```
 
-Check the external IP address of the service in the output:
+Observe from the output that the external IP address of the service is a publicly accessible one:
 
 ```
 NAME                                TYPE           CLUSTER-IP    EXTERNAL-IP     PORT(S)                                      AGE
@@ -109,6 +109,11 @@ Navigate to the URL from the output of the previous command and confirm that the
 curl -s "http://${GATEWAY_URL_EXTERNAL}/productpage" | grep -o "<title>.*</title>"
 ```
 
+Confirm that the sample application's product page is accessible. The expected output is:
+
+```html
+<title>Simple Bookstore App</title>
+```
 
 ## Enable internal ingress gateway
 
@@ -125,7 +130,7 @@ Use `kubectl get svc` to check the service mapped to the ingress gateway:
 kubectl get svc aks-istio-ingressgateway-internal -n aks-istio-ingress
 ```
 
-Check value of the external IP address of the service. For example:
+Observe from the output that the external IP address of the service isn't a publicly accessible one and is instead only locally accessible:
 
 ```
 NAME                                TYPE           CLUSTER-IP    EXTERNAL-IP     PORT(S)                                      AGE