From 4f927ed277931d8ba0502a60ee4b8149fa28d9bf Mon Sep 17 00:00:00 2001 From: Keagan Roos Date: Fri, 23 Sep 2022 16:44:59 +0200 Subject: [PATCH] Fix typos, tone and brevity --- language/golang/run-containers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/language/golang/run-containers.md b/language/golang/run-containers.md index 923eac4246..a8f9809928 100644 --- a/language/golang/run-containers.md +++ b/language/golang/run-containers.md @@ -97,9 +97,9 @@ CONTAINER ID IMAGE COMMAND CREATED STATUS d75e61fcad1e docker-gs-ping "/docker-gs-ping" 41 seconds ago Up 40 seconds 0.0.0.0:8080->8080/tcp inspiring_ishizaka ``` -The `ps` command tells a bunch of stuff about our running containers. We can see the container ID, the image running inside the container, the command that was used to start the container, when it was created, the status, ports that are exposed, and the name of the container. +The `ps` command tells us a bunch of stuff about our running containers. We can see the container ID, the image running inside the container, the command that was used to start the container, when it was created, the status, ports that are exposed, and the names of the container. -You are probably wondering where the name of our container is coming from. Since we didn’t provide a name for the container when we started it, Docker generated a random name. We’ll fix this in a minute but first we need to stop the container. To stop the container, run the `docker stop` command which does just that, stops the container. You will need to pass the name of the container or you can use the container ID. +You are probably wondering where the name of our container is coming from. Since we didn’t provide a name for the container when we started it, Docker generated a random name. We’ll fix this in a minute but first we need to stop the container. To stop the container, run the `docker stop` command, passing the container's name or ID. ```console $ docker stop inspiring_ishizaka