diff --git a/docs/book/src/developers/development.md b/docs/book/src/developers/development.md
index ff753b0559e..bffaae5168f 100644
--- a/docs/book/src/developers/development.md
+++ b/docs/book/src/developers/development.md
@@ -21,8 +21,8 @@
     - [Tilt for dev in CAPZ](#tilt-for-dev-in-capz)
     - [Tilt for dev in both CAPZ and CAPI](#tilt-for-dev-in-both-capz-and-capi)
     - [Deploying a workload cluster](#deploying-a-workload-cluster)
-    - [Tilt for dev using internal ILB for internode communication](#tilt-for-dev-using-internal-ilb-for-internode-communication)
-      - [Flavors for development using internal ILB for internode communication](#flavors-for-development-using-internal-ilb-for-internode-communication)
+    - [Tilt for dev using internal LB for cluster VNet node-apiserver communication](#tilt-for-dev-using-internal-lb-for-cluster-vnet-node-apiserver-communication)
+      - [Flavors for development using internal LB for cluster VNet node-apiserver communication](#flavors-for-development-using-internal-lb-for-cluster-vnet-node-apiserver-communication)
     - [Viewing Telemetry](#viewing-telemetry)
     - [Debugging](#debugging)
   - [Manual Testing](#manual-testing)
@@ -155,7 +155,7 @@ development will span both CAPZ and CAPI, then follow the [CAPI and CAPZ instruc
 
 <aside class="note warning">
 <h1> Warning </h1>
-If you are looking to leverage the internal LB for internode communication in your workload cluster, please follow the instructions in the [Tilt for dev using internal ILB for internode communication](#tilt-for-dev-using-internal-ilb-for-internode-communication) section.
+If you are looking to leverage the internal LB for internode communication in your workload cluster, please follow the instructions in the [Tilt for dev using internal LB for cluster VNet node-apiserver communication](#tilt-for-dev-using-internal-lb-for-cluster-vnet-node-apiserver-communication) section.
 </aside>
 
 If you want to develop in CAPZ and get a local development cluster working quickly, this is the path for you.
@@ -254,7 +254,7 @@ make delete-workload-cluster
 
 > Check out the [self-managed](../self-managed/troubleshooting.md) and [managed](../managed/troubleshooting.md) troubleshooting guides for common errors you might run into.
 
-#### Tilt for dev using internal ILB for internode communication
+#### Tilt for dev using internal LB for cluster VNet node-apiserver communication
 
 This flow is for developers who want to leverage the internal LB for internode communication in their workload cluster.
 You can achieve this by setting the `EXP_APISERVER_ILB` environment variable to `true` in your shell (run `export EXP_APISERVER_ILB=true`) and then create the CAPZ management cluster.
@@ -278,7 +278,7 @@ TODO:
 2. VNet peering should be exported out as a shell script for users to run.
 ```
 
-##### Flavors for development using internal ILB for internode communication
+##### Flavors for development using internal LB for cluster VNet node-apiserver communication
 
 There are two flavors 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.