Apply suggestions from code review

Co-authored-by: Devin <[email protected]>

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/diag-logs.mdx

@@ -50,13 +50,13 @@ This command will output the status of each diagnostic task and place a `cloudfl
 
 1. Determine the [metrics server port](/cloudflare-one/connections/connect-networks/monitor-tunnels/metrics/#default-metrics-server-address) for the `cloudflared` instance running in Docker.
 
-2. Re-deploy the container with port forwarding enabled. The diagnostic feature will request information from the Docker instance using local port `20241`, therefore you should forward port `20241` to the container port obtained in Step 1:
+2. Ensure the container is deployed with port forwarding enabled. The diagnostic feature will request information from the Docker instance using local port `20241`, therefore you should forward port `20241` to the container port obtained in Step 1:
 
 		```sh
 		docker run -d -p 20241:<metrics_port> docker.io/cloudflare/cloudflared tunnel ...
 		```
 
-3. Verify that you can reach the metrics server address:
+3. Verify that you can reach the metrics server address from the Docker host environment:
 
 		```curl
 		curl localhost:20241/diag/tunnel
@@ -109,9 +109,9 @@ The diagnostic feature will request data from the [tunnel metrics server](/cloud
 		For example, if you set the metrics server address to `0.0.0.0:12345`:
 
 		```sh
-		kubectl port-forward http-echo-6d4897585b-r8kfz 20244:12345
+		kubectl port-forward cloudflared-6d4897585b-r8kfz 20244:12345
 		```
-		Connections made to local port `20244` are forwarded to port `1234` of the pod that is running the tunnel.
+		Connections made to local port `20244` are forwarded to port `12345` of the pod that is running the tunnel.
 
 3. Run the diagnostic: