[docs-scanner] Inconsistent Windows backend process name between networking pages

[docker-agent]

File: content/manuals/desktop/features/networking/networking-how-tos.md

Issue

The networking how-tos page incorrectly states that Windows uses com.docker.backend as the process name, contradicting the overview page which correctly identifies it as com.docker.backend.exe.

In networking-how-tos.md, the "Connect to a container from the host" section states:

All inbound connections pass through the Docker Desktop backend process (com.docker.backend (Mac), com.docker.backend (Windows), or qemu (Linux)

However, in _index.md (the overview page in the same directory), the documentation consistently uses:

• Windows: com.docker.backend.exe
• Mac: com.docker.backend
• Linux: qemu

This is confirmed in multiple places in the overview:

• The backend components table
• The "Firewalls and endpoint visibility" section: "apply rules to com.docker.backend.exe (Windows) com.docker.backend (Mac) or qemu (Linux)"

Why this matters

Windows users following the how-tos page to configure firewalls or monitor network traffic would look for the wrong process name. The .exe extension is significant on Windows systems when creating firewall rules or identifying processes.

Suggested fix

In networking-how-tos.md, change the process name reference to match the overview page:

All inbound connections pass through the Docker Desktop backend process (`com.docker.backend` (Mac), `com.docker.backend.exe` (Windows), or `qemu` (Linux)

---

Found by nightly documentation quality scanner