diff --git a/docker-for-mac/networking.md b/docker-for-mac/networking.md
index 0376286d58..c7f8d2110b 100644
--- a/docker-for-mac/networking.md
+++ b/docker-for-mac/networking.md
@@ -3,19 +3,19 @@ description: Networking
 keywords: mac, networking
 redirect_from:
 - /mackit/networking/
-title: Networking features in Docker for Mac
+title: Networking features in Docker Desktop for Mac
 ---
 {% assign Arch = 'Mac' %}
 
-Docker for {{Arch}} provides several networking features to make it
+Docker Desktop for {{Arch}} provides several networking features to make it
 easier to use.
 
 ## Features
 
 ### VPN Passthrough
 
-Docker for {{Arch}}'s networking can work when attached to a VPN. To do this,
-Docker for {{Arch}} intercepts traffic from the containers and injects it into
+Docker Desktop for {{Arch}}'s networking can work when attached to a VPN. To do this,
+Docker Desktop for {{Arch}} intercepts traffic from the containers and injects it into
 {{Arch}} as if it originated from the Docker application.
 
 ### Port Mapping
@@ -26,7 +26,7 @@ When you run a container with the `-p` argument, for example:
 $ docker run -p 80:80 -d nginx
 ```
 
-Docker for {{Arch}} makes whatever is running on port 80 in the container (in
+Docker Desktop for {{Arch}} makes whatever is running on port 80 in the container (in
 this case, `nginx`) available on port 80 of `localhost`. In this example, the
 host and container ports are the same. What if you need to specify a different
 host port? If, for example, you already have something running on port 80 of
@@ -45,18 +45,18 @@ See [Proxies](index#proxies).
 
 ## Known limitations, use cases, and workarounds
 
-Following is a summary of current limitations on the Docker for {{Arch}}
+Following is a summary of current limitations on the Docker Desktop for {{Arch}}
 networking stack, along with some ideas for workarounds.
 
 ### There is no docker0 bridge on macOS
 
-Because of the way networking is implemented in Docker for Mac, you cannot see a
+Because of the way networking is implemented in Docker Desktop for Mac, you cannot see a
 `docker0` interface on the host. This interface is actually within the virtual
 machine.
 
 ### I cannot ping my containers
 
-Docker for Mac can't route traffic to containers.
+Docker Desktop for Mac can't route traffic to containers.
 
 ### Per-container IP addressing is not possible
 
@@ -72,7 +72,7 @@ The host has a changing IP address (or none if you have no network access). From
 18.03 onwards our recommendation is to connect to the special DNS name
 `host.docker.internal`, which resolves to the internal IP address used by the
 host.
-This is for development purpose and will not work in a production environment outside of Docker for Mac.
+This is for development purpose and will not work in a production environment outside of Docker Desktop for Mac.
 
 The gateway is also reachable as `gateway.docker.internal`.