Update docs/proxy.md

Co-authored-by: Mathias Fredriksson <[email protected]>

Author: SasSwart

docs/proxy.md

@@ -111,7 +111,7 @@ docker run -it --rm \
     ghcr.io/coder/envbuilder:latest
 ```
 
-As before, this command should yield a shell inside an Envbuilder built environment. Feel free to test it en then exit the container. Assuming this worked, Envbuilder will have cloned a repository and built the relevant container using a proxy that required a custom ca certificate.
+As before, this command should yield a shell inside an Envbuilder built environment. Feel free to test it and then exit the container. Assuming this worked, Envbuilder will have cloned a repository and built the relevant container using a proxy that required accepting a custom CA certificate.
 
 ### Bonus
 To prove that Envbuilder did in fact use the proxy, and also because it is interesting to observe, open `http://localhost:8081/` in your local browser and you should see the mitmproxy web interface. In the flow tab, there should be a list of all of the HTTP requests that were required to build the container. The first three will be the requests that were used by git to clone the repository. The rest will be the requests that were used to clone the devcontainer image.