docs: fix minor grammar errors (#25372)

## Description

  Fix several small grammar errors across the docs:

- **GitHub Actions CI guides** (Python and Ruby): `This workflow is
runs` → `This workflow runs`; `tab of you GitHub repository` → `of your
GitHub repository`; `[Login to Docker Hub]` link text → `[Log in to
Docker Hub]`, matching the adjacent "Set up Docker Buildx" step
- **build/ci/github-actions/configure-builder**: `a node in an
underlying step of you workflow` → `of your workflow`
- **Bind mounts page** (get started): remove a stray article in image
alt text — `inside the a container` → `inside the container`
- **Database pre-seeding guide**: `let you access to the Postgres
database` → `letting you access the Postgres database`; `It also define`
→ `It also defines`

  ## Reviews

  - [ ] Technical review
  - [ ] Editorial review
  - [ ] Product review

Author: dvdksn

content/get-started/docker-concepts/running-containers/sharing-local-files.md

@@ -162,12 +162,12 @@ Using a bind mount, you can map the configuration file on your host computer to
 1. You can view the mounted files inside a container by selecting the container's **Files** tab and then selecting a file inside the `/usr/local/apache2/htdocs/` directory. Then, select **Open file editor**.
 
 
-   ![A screenshot of Docker Desktop Dashboard showing the mounted files inside the a container](images/mounted-files.webp?border=true)
+   ![A screenshot of Docker Desktop Dashboard showing the mounted files inside the container](images/mounted-files.webp?border=true)
 
 2. Delete the file on the host and verify the file is also deleted in the container. You will find that the files no longer exist under **Files** in the Docker Desktop Dashboard.
 
 
-   ![A screenshot of Docker Desktop Dashboard showing the deleted files inside the a container](images/deleted-files.webp?border=true)
+   ![A screenshot of Docker Desktop Dashboard showing the deleted files inside the container](images/deleted-files.webp?border=true)
 
 
 3. Recreate the HTML file on the host system and see that file re-appears under the **Files** tab under **Containers** on the Docker Desktop Dashboard. By now, you will be able to access the site too.

content/guides/pre-seeding.md

@@ -210,7 +210,7 @@ $ docker container stop postgres
      data_sql:
     ```
   
-    It maps port `5432` on the host to the container's `5432`, let you access to the Postgres database from outside the container. It also define `data_sql` for persisting the database data, ensuring that data is not lost when the container is stopped.
+    It maps port `5432` on the host to the container's `5432`, letting you access the Postgres database from outside the container. It also defines `data_sql` for persisting the database data, ensuring that data is not lost when the container is stopped.
 
     It is important to note that the port mapping to the host is only necessary if you want to connect to the database from non-containerized programs. If you containerize the service that connects to the DB, you should connect to the database over a custom bridge network.
 

content/manuals/build/ci/github-actions/configure-builder.md

@@ -140,7 +140,7 @@ fields:
 
 | Name              | Type   | Description                                                                                                                                                                                                                                                             |
 | ----------------- | ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `name`            | String | [Name of the node](/reference/cli/docker/buildx/create/#node). If empty, it's the name of the builder it belongs to, with an index number suffix. This is useful to set it if you want to modify/remove a node in an underlying step of you workflow. |
+| `name`            | String | [Name of the node](/reference/cli/docker/buildx/create/#node). If empty, it's the name of the builder it belongs to, with an index number suffix. This is useful to set it if you want to modify/remove a node in an underlying step of your workflow. |
 | `endpoint`        | String | [Docker context or endpoint](/reference/cli/docker/buildx/create/#description) of the node to add to the builder                                                                                                                                      |
 | `driver-opts`     | List   | List of additional [driver-specific options](/reference/cli/docker/buildx/create/#driver-opt)                                                                                                                                                         |
 | `buildkitd-flags` | String | [Flags for buildkitd](/reference/cli/docker/buildx/create/#buildkitd-flags) daemon                                                                                                                                                                    |