update documentation on running e2e test from a dev machine

Author: nawazkh

docs/book/src/developers/tilt-with-aks-as-mgmt-ilb.md

@@ -140,7 +140,7 @@ Building upon the [challenges and solutions](#challenges-and-solutions) from abo
 - The below steps for self-managed templates only. Does not apply to AKS workload clusters.
 
 - The below steps are for running the tests in a intuned device. If you are going to run the local tests from a dev machine in Azure, you have to first follow below steps and then proceed ahead.
-  1. Create a managed Identity 
+  1. Create a managed Identity
   2. Assign that managed identity a contributor role to your subscription
   3. Set `AZURE_CLIENT_ID_USER_ASSIGNED_IDENTITY`, `AZURE_OBJECT_ID_USER_ASSIGNED_IDENTITY`, `AZURE_USER_ASSIGNED_IDENTITY_RESOURCE_ID` to the user assigned managed identity.
 
@@ -261,9 +261,7 @@ We recommend running the test individually while debugging the test failure. Thi
 
    - Set `MGMT_CLUSTER_TYPE` to `"aks"` to leverage `AKS` as the management cluster.
    - Set `EXP_APISERVER_ILB` to `true` to enable the API Server ILB feature gate.
-   - Set `IS_DEV_BOX` to `"true"` to use the user assigned managed identity instead of the AKS created managed identity
-
-
+   - Set `AZURE_CLIENT_ID_USER_ASSIGNED_IDENTITY`, `AZURE_OBJECT_ID_USER_ASSIGNED_IDENTITY` and `AZURE_USER_ASSIGNED_IDENTITY_RESOURCE_ID` to use the user assigned managed identity instead of the AKS created managed identity.
 
 3. In a new terminal, wait for AzureClusters to be created by the above command. Check it using `kubectl get AzureClusters -A`. Note that this command will fail or will not output anything unless the above command, `GINKGO_FOCUS...`, has deployed the worker template and initiated workload cluster creation.