Merge pull request #6628 from RobinDeBock/main

📖 More generic explanation about issue getting kubeconfig on certain systems using Docker

Author: k8s-ci-robot

docs/book/src/clusterctl/developers.md

@@ -189,10 +189,9 @@ The command for getting the kubeconfig file for connecting to a workload cluster
 clusterctl get kubeconfig capi-quickstart > capi-quickstart.kubeconfig
 ```
 
-### Fix kubeconfig (when using docker on macOS)
+### Fix kubeconfig when using Docker Desktop
 
-When using docker on macOS, you will need to do a couple of additional
-steps to get the correct kubeconfig for a workload cluster created with the Docker provider:
+When using using Docker Desktop on macOS or Docker Desktop (Docker Engine works fine) on Linux, you'll need to take a few extra steps to get the kubeconfig for a workload cluster created with the Docker provider.
 
 ```bash
 # Point the kubeconfig to the exposed port of the load balancer, rather than the inaccessible container IP.

docs/book/src/user/quick-start.md

@@ -975,9 +975,7 @@ clusterctl get kubeconfig capi-quickstart > capi-quickstart.kubeconfig
 
 <h1>Warning</h1>
 
-If you are using Docker on MacOS, you will need to do a couple of additional
-steps to get the correct kubeconfig for a workload cluster created with the Docker provider.
-See [Additional Notes for the Docker Provider](../clusterctl/developers.md#additional-notes-for-the-docker-provider).
+If you're using Docker Desktop on macOS, or Docker Desktop (Docker Engine works fine) on Linux, you'll need to take a few extra steps to get the kubeconfig for a workload cluster created with the Docker provider. See [Additional Notes for the Docker provider](../clusterctl/developers.md#additional-notes-for-the-docker-provider).
 
 </aside>