Draft: Resolve "Provide tooling to migrate an active cluster from Operator Istio to Helm Istio."

See: #2283

docs/guides/using-bigbang/migrating-istio-in-bb3.0.md

@@ -3,20 +3,20 @@
 ### *The new Istio Helm packages are BETA in Big Bang 2.x and will be stable in 3.0*
 
 ### Step 1 : Remove Istio from your current deployment
-Before upgrading to the new Helm-based Istio packages, first disable the Istio and Istio's Operator packages:
+Before upgrading to the new helm-based Istio packages, first disable the istio and istioOperator packages:
 ```yaml
 istio:
   enabled: false
 istioOperator:
   enabled: false
 ```
-After a few minutes, all pods in both the `istio-system` and `istio-operator` namespaces will have terminated. However, due due to Istio's finalizer, the `istio-system` namespace will be stuck in the `terminating` state.  
+After a few minutes, all pods in both the `istio-system` and `istio-operator` namespaces will have terminated. However, due to Istio's finalizer, the `istio-system` namespace will be stuck in the _**terminating**_ state.  
   
 Force the deletion of this namespace:
 ```bash
 kubectl get ns istio-system -o json | jq '.spec.finalizers = []' | kubectl replace --raw "/api/v1/namespaces/istio-system/finalize" -f -
 ```
-Both Istio namespaces are now removed yet other remnants of Istio still linger in the cluster including custom resources. Remove them as they will be recreated via the helm deployment of Istio. The quickest way to do this is by using the [istioctl CLI tool](https://istio.io/latest/docs/ops/diagnostic-tools/istioctl/).  
+Both Istio namespaces are now removed yet other remnants still linger, not limited to, but including custom resources. Remove them as they will be recreated via the helm deployment of Istio. The quickest way to do this is by using the [istioctl CLI tool](https://istio.io/latest/docs/ops/diagnostic-tools/istioctl/).  
   
 On macOS or Linux install it with:
 ```bash
@@ -92,7 +92,7 @@ do
 done
 ```
 ### Optionally reconcile Helm Releases
-It may be necessary, but not likely, to synchronize helm releases managed by Flux. Typically, this can occur when a Gitops deployment of Big Bang sees its helm resources get out of sync during an upgrade.  
+It may (but unlikely) be necessary to synchronize the helm releases managed by Flux. Typically, this can occur when a Gitops deployment of Big Bang has its helm resources get out of sync during an upgrade.  
   
 The `flux` CLI must be [installed locally](https://fluxcd.io/flux/installation/) -- on macOS and Linux:
 ```bash