Resolving Willie's comments

Author: alimaazamat

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

@@ -25,23 +25,22 @@ While the default Tilt setup recommends using a KIND cluster as the management c
     - `Microsoft.Authorization`
     - `Microsoft.ResourceHealth` (if the `EXP_AKS_RESOURCE_HEALTH` feature flag is enabled)
 - Install the [Azure CLI](https://learn.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)
-- A [supported version](https://github.com/kubernetes-sigs/cluster-api-provider-azure#compatibility) of `clusterctl`
+- A [supported version](https://github.com/kubernetes-sigs/cluster-api-provider-azure#compatibility) of [clusterctl](https://cluster-api.sigs.k8s.io/user/quick-start#install-clusterctl)
 - Basic understanding of Azure networking concepts, Cluster API, and CAPZ.
 - Go, Wget, and Tilt installed on your development machine.
 - If `tilt-settings.yaml` file exists in the root of your repo, clear out any values in `kustomize_settings` unless you want to use them instead of the values that will be set by running `make aks-create`.
 
 ### Managed Identity & Registry Setup
 1. Have a managed identity created from Azure Portal.
-2. Add the following lines to your shell config using `nano ~/.bashrc` or `nano ~/.zshrc`
+2. Add the following lines to your shell config such as `~/.bashrc` or `~/.zshrc`
     ```
    export USER_IDENTITY="<Managed Identity name>"
-   export AZURE_CLIENT_ID_USER_ASSIGNED_IDENTITY="<Client ID seen in the portal>"
+   export AZURE_CLIENT_ID_USER_ASSIGNED_IDENTITY="<your-client-id>"
    export AZURE_CLIENT_ID="${AZURE_CLIENT_ID_USER_ASSIGNED_IDENTITY}"
-   export AZURE_OBJECT_ID_USER_ASSIGNED_IDENTITY="<Object ID seen in the portal>"
-   export AZURE_LOCATION="<location of your choice>"
-   export REGISTRY=<registry of your choice>
+   export AZURE_OBJECT_ID_USER_ASSIGNED_IDENTITY="<your-object-id>"
+   export AZURE_LOCATION="<your-azure-location>"
+   export REGISTRY=<your-container-registry>
    ```
-   - We recommend using DockerHub: `export REGISTRY=docker.io/<DOCKERHUBUSERNAME>` then authenticate with `Docker login`.
 3. Be sure to reload with `source ~/.bashrc` or `source ~/.zshrc` and then verify the correct env vars values return with `echo $AZURE_CLIENT_ID` and `echo $REGISTRY`.
 
 ## Steps to Use Tilt with AKS as the Management Cluster
@@ -74,8 +73,8 @@ While the default Tilt setup recommends using a KIND cluster as the management c
    - This task will take a few minutes to complete. Wait for this to finish to avoid race conditions.
 8.  Checkmark the flavors you want to deploy and CAPZ will deploy the workload cluster with the selected flavor.
       - Flavors that leverage internal load balancer and are available for development in CAPZ for MSFT Tenant:
-         - [apiserver-ilb](../../../../templates/cluster-template-apiserver-ilb.yaml): VM based default flavor that brings up native K8s clusters with Linux nodes.
-         - [apiserver-ilb-windows](../../../../templates/cluster-template-windows-apiserver-ilb.yaml): VM based flavor that brings up native K8s clusters with Linux and Windows nodes.
+         - [apiserver-ilb](https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/main/templates/cluster-template-apiserver-ilb.yaml): VM based default flavor that brings up native K8s clusters with Linux nodes.
+         - [apiserver-ilb-windows](https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/main/templates/cluster-template-windows-apiserver-ilb.yaml): VM based flavor that brings up native K8s clusters with Linux and Windows nodes.
 
 ## Leveraging internal load balancer