fix walkthrough typos and feedback (#18728)

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

content/guides/walkthroughs/access-local-folder.md

@@ -58,12 +58,12 @@ The `volumes` element tells Compose to mount the local folder `./app` to `/usr/s
 
 ## Step 3: Run the application
 
-In a terminal, run the follow commands to bring up your application. Replace `/path/to/multi-container-app/` with the path to your applications directory.
+In a terminal, run the follow commands to bring up your application. Replace `/path/to/bindmount-apps/` with the path to your application's directory.
 
 {{< include "open-terminal.md" >}}
 
 ```console
-$ cd /path/to/multi-container-app/
+$ cd /path/to/bindmount-apps/
 ```
 ```console
 $ docker compose up -d

content/guides/walkthroughs/multi-container-apps.md

@@ -43,7 +43,7 @@ View the files of the sample application. Notice that it has a `compose.yaml` fi
 
 ## Step 3: Run the application
 
-To run the multi-container application, open a terminal and run the following commands. Replace `/path/to/multi-container-app/` with the path to your applications directory.
+To run the multi-container application, open a terminal and run the following commands. Replace `/path/to/multi-container-app/` with the path to your application's directory.
 
 {{< include "open-terminal.md" >}}
 
@@ -54,6 +54,8 @@ $ cd /path/to/multi-container-app/
 $ docker compose up -d
 ```
 
+In the previous command, the `-d` flag tells Docker Compose to run in detached mode.
+
 ## Step 4: View the frontend and add todos
 
 In the **Containers** tab of Docker Desktop, you should now have an application stack with two containers running (the todo-app, and todo-database).
@@ -71,7 +73,7 @@ When developing with Docker, you may need to automatically update and preview yo
 
 To run Compose Watch and see the real-time changes:
 
-1. Open a terminal and run the following commands. Replace `/path/to/multi-container-app/` with the path to your applications directory.
+1. Open a terminal and run the following commands. Replace `/path/to/multi-container-app/` with the path to your application's directory.
    ```console
    $ cd /path/to/multi-container-app/
    ```

content/guides/walkthroughs/persist-data.md

@@ -62,7 +62,7 @@ The top-level `volumes` element defines and configures a volume named `database`
 
 ## Step 3: Run the application
 
-To run the multi-container application, open a terminal and run the following commands. Replace `/path/to/multi-container-app/` with the path to your applications directory.
+To run the multi-container application, open a terminal and run the following commands. Replace `/path/to/multi-container-app/` with the path to your application's directory.
 
 {{< include "open-terminal.md" >}}
 

content/guides/walkthroughs/publish-your-image.md

@@ -46,7 +46,7 @@ To push your image to Docker Hub:
 
 ![Pushing an image to Docker Hub](images/getting-started-push.webp?w=200&border=true)
 
-Go to [Docker Hub](https://hub.docker.com)⁠ and verify that the list of your repositories now contains `YOU-USERNAME/welcome-to-docker`.
+Go to [Docker Hub](https://hub.docker.com)⁠ and verify that the list of your repositories now contains `YOUR-USERNAME/welcome-to-docker`.
 
 ## Summary
 

content/guides/walkthroughs/run-a-container.md

@@ -55,6 +55,10 @@ $ cd /path/to/welcome-to-docker/
 $ docker build -t welcome-to-docker .
 ```
 
+In the previous command, the `-t` flag tags your image with a name,
+`welcome-to-docker` in this case. And the `.` lets Docker know where it can find
+the Dockerfile.
+
 Building the image may take some time. After your image is built, you can view your image in the **Images** tab in Docker Desktop.
 
 ## Step 4: Run your container