Apply suggestions from code review

Co-authored-by: emily-shen <[email protected]>

Author: dario-piotrowicz

src/content/docs/containers/local-dev.mdx

@@ -52,15 +52,15 @@ you are using in your container code.
 In production, all of your container's ports will be accessible by your Worker,
 so you do not need to specifically expose ports using the [`EXPOSE` instruction](https://docs.docker.com/reference/dockerfile/#expose) in your Dockerfile.
 
-But for local development on non-Linux systems, you most likely need to expose a port to access your container properly; for example: `EXPOSE 4000`.
+But for local development on non-Linux systems, you will need to declare any ports you need to access in your Dockerfile with the EXPOSE instruction; for example: `EXPOSE 4000`, if you will be accessing port 4000.
 
-If you have not exposed any ports, you will see the following type of error when building or pulling your container image:
+If you have not exposed any ports, you will see the following error in local development:
 
 ```text
 The container "MyContainer" does not expose any ports, please expose any port that you want to use with `getTCPPort()`.
 ```
 
-And if you call `getTCPPort()` on an unexposed port you will see the following error:
+And if you call `getTCPPort()` on a port that you have not exposed in your `Dockerfile` you will see the following error:
 
 ```text
 connect(): Connection refused: container port not found. Make sure you exposed the port in your container definition.