diff --git a/README.md b/README.md
index 225895c2..e96561b7 100644
--- a/README.md
+++ b/README.md
@@ -187,9 +187,9 @@ Mac and Windows run the containers inside a VM and, on the contrary to Linux, th
 so the LoadBalancer assigned IP is not working for users.
 
 To solve this problem, cloud-provider-kind, leverages the existing docker portmap capabilities to expose the Loadbalancer IP and Ports
-on the host. When you start cloud-provider-kind and create a LoadBalancer service, you will notice that a container named `kindccm -...` is launched within Docker. You can access the service by using the port exposed from the container to the host machine with `localhost`.
+on the host. When you start cloud-provider-kind and create a LoadBalancer service, you will notice that a container named `kindccm-...` is launched within Docker. You can access the service by using the port exposed from the container to the host machine with `localhost`.
 
-For WSL2, it is recommended to use the default [NAT](https://learn.microsoft.com/en-us/windows/wsl/networking) network mode with Docker Desktop on Windows. In WSL2, you can access the service via the external IP. On Windows, you can access the service by leveraging Docker's portmap capabilities.
+For WSL2, it is recommended to use the default [NAT](https://learn.microsoft.com/en-us/windows/wsl/networking) network mode with Docker Desktop on Windows. On WSL2, you can access the service via the external IP. On Windows, you can access the service by leveraging Docker's portmap capabilities.
 
 Limitations: