diff --git a/site/content/docs/user/known-issues.md b/site/content/docs/user/known-issues.md
index 156f3dde..a91f0d7a 100644
--- a/site/content/docs/user/known-issues.md
+++ b/site/content/docs/user/known-issues.md
@@ -41,7 +41,7 @@ description: |-
 * [Docker Desktop for macOS and Windows](#docker-desktop-for-macos-and-windows)
 * [Older Linux Distributions](#older-linux-distributions)
 * [Failure to Create Cluster on WSL2](#failure-to-create-cluster-on-wsl2)
-* [VPN CIDR clashes](#vpn-cidr-clashes)
+* [Local Subnet Clashes](#local-subnet-clashes)
 
 ## Troubleshooting Kind
 
@@ -417,11 +417,11 @@ the project relies on community support and feedback. It has been noted that the
 steps detailed in [https://github.com/spurin/wsl-cgroupsv2](https://github.com/spurin/wsl-cgroupsv2)
 have been necessary to resolve this issue.
 
-## VPN CIDR Clashes
+## Local Subnet Clashes
 
 KIND creates a separate docker network named `kind` that will be configured with default IPAM settings. If you are using the default IPAM configuration in your `daemon.json` you
-may have conflicts with existing VPNs that route the 172.17.x.x networks. To resolve this you can reconfigure the daemon-wide IPAM so that all networks will be created in subnets
-that do not have these conflicts.
+may have conflicts with existing networks (like VPNs, labs, etc) that route the 172.17.x.x networks. To resolve this you can reconfigure the daemon-wide IPAM so that all 
+networks will be created in subnets that do not have these conflicts.
 
 An example configuration that you can add to your `daemon.json` is below. This would configure `10.253.0.0/16` as the defauld CIDR with each individual network receiving a /24
 subnet to use for allocation.