docs: minor grammar fixes

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

Author: thaJeztah

docs/reference/commandline/image_build.md

@@ -113,7 +113,7 @@ COPY failed: forbidden path outside the build context: ../../some-dir ()
 ```
 
 BuildKit on the other hand strips leading relative paths that traverse outside
-of the build context. Re-using the previous example, the path `COPY
+of the build context. Reusing the previous example, the path `COPY
 ../../some-dir .` evaluates to `COPY some-dir .` with BuildKit.
 
 ## Examples

man/docker-run.1.md

@@ -734,7 +734,7 @@ any options, the systems uses the following options:
 **-u**, **--user**=""
    Sets the username or UID used and optionally the groupname or GID for the specified command.
 
-   The followings examples are all valid:
+   The following examples are all valid:
    --user [user | user:group | uid | uid:gid | user:gid | uid:group ]
 
    Without this argument the command will be run as root in the container.

man/src/container/exec.md

@@ -19,7 +19,7 @@ the same capabilities as the container, which may be limited. Set
 # USER
 `user` sets the username or UID used and optionally the groupname or GID for the specified command.
 
-   The followings examples are all valid:
+   The following examples are all valid:
    --user [user | user:group | uid | uid:gid | user:gid | uid:group ]
 
    Without this argument the command will be run as root in the container.

man/src/volume.md

@@ -1,5 +1,5 @@
 The `docker volume` command has subcommands for managing data volumes. A data
-volume is a specially-designated directory that by-passes storage driver
+volume is a specially-designated directory that bypasses storage driver
 management.
 
 Data volumes persist data independent of a container's life cycle. When you