docs: Update README with WSL configuration details

Added workarounds for using chrome-devtools-mcp in WSL.

Author: OrKoN

README.md

@@ -677,3 +677,15 @@ Chrome that requires permissions to create its own sandboxes. As a workaround,
 either disable sandboxing for `chrome-devtools-mcp` in your MCP client or use
 `--browser-url` to connect to a Chrome instance that you start manually outside
 of the MCP client sandbox.
+
+### WSL
+
+In Windows WSL, the default configuration of `chrome-devtools-mcp` does not work
+if there is no Chrome installed inside the Linux machine. By defautl, `chrome-devtools-mcp`
+will try to start the Chrome instances on the Windows side but it fails due to https://github.com/microsoft/WSL/issues/14201.
+
+Possible workarounds are:
+
+- Install Google Chrome in WSL.
+- Configure Mirrored networking for WSL. Start Chrome on the Windows side we with `--remote-debugging-port=9222` and start `chrome-devtools-mcp` with `--browserUrl=http://127.0.0.1:9222`.
+- Use Powershell or Git bash instead of WSL.