Merge pull request #29696 from zhenghenghuo/branch-two

fix some typos

contrib/vagrant-docker/README.md

@@ -35,7 +35,7 @@ script
 end script
 ```
 
-Once that's done, you need to set up a SSH tunnel between your host machine and the vagrant machine that's running Docker. This can be done by running the following command in a host terminal:
+Once that's done, you need to set up an SSH tunnel between your host machine and the vagrant machine that's running Docker. This can be done by running the following command in a host terminal:
 
 ```
 ssh -L 2375:localhost:2375 -p 2222 vagrant@localhost

docs/extend/plugins_volume.md

@@ -169,7 +169,7 @@ Docker needs reminding of the path to the volume on the host.
 
 Respond with the path on the host filesystem where the volume has been made
 available, and/or a string error if an error occurred. `Mountpoint` is optional,
-however the plugin may be queried again later if one is not provided.
+however, the plugin may be queried again later if one is not provided.
 
 ### /VolumeDriver.Unmount
 
@@ -257,7 +257,7 @@ Respond with a string error if an error occurred. `Mountpoint` is optional.
 ```
 
 Get the list of capabilities the driver supports.
-The driver is not required to implement this endpoint, however in such cases
+The driver is not required to implement this endpoint, however, in such cases
 the default values will be taken.
 
 **Response**:

docs/reference/commandline/dockerd.md

@@ -237,7 +237,7 @@ drivers: `aufs`, `devicemapper`, `btrfs`, `zfs`, `overlay` and `overlay2`.
 
 The `aufs` driver is the oldest, but is based on a Linux kernel patch-set that
 is unlikely to be merged into the main kernel. These are also known to cause
-some serious kernel crashes. However, `aufs` allows containers to share
+some serious kernel crashes. However `aufs` allows containers to share
 executable and shared library memory, so is a useful choice when running
 thousands of containers with the same program or libraries.
 
@@ -658,7 +658,7 @@ options for `zfs` start with `zfs` and options for `btrfs` start with `btrfs`.
 
     Overrides the Linux kernel version check allowing overlay2. Support for
     specifying multiple lower directories needed by overlay2 was added to the
-    Linux kernel in 4.0.0. However some older kernel versions may be patched
+    Linux kernel in 4.0.0. However, some older kernel versions may be patched
     to add multiple lower directory support for OverlayFS. This option should
     only be used after verifying this support exists in the kernel. Applying
     this option on a kernel without this support will cause failures on mount.

experimental/vlan-networks.md

@@ -166,7 +166,7 @@ $ ip route
 
 Example: Multi-Subnet Ipvlan L2 Mode starting two containers on the same subnet and pinging one another. In order for the `192.168.114.0/24` to reach `192.168.116.0/24` it requires an external router in L2 mode. L3 mode can route between subnets that share a common `-o parent=`. 
 
-Secondary addresses on network routers are common as an address space becomes exhausted to add another secondary to a L3 vlan interface or commonly referred to as a "switched virtual interface" (SVI).
+Secondary addresses on network routers are common as an address space becomes exhausted to add another secondary to an L3 vlan interface or commonly referred to as a "switched virtual interface" (SVI).
 
 ```
 docker network  create  -d ipvlan \

pkg/locker/README.md

@@ -4,7 +4,7 @@ Locker
 locker provides a mechanism for creating finer-grained locking to help
 free up more global locks to handle other tasks.
 
-The implementation looks close to a sync.Mutex, however the user must provide a
+The implementation looks close to a sync.Mutex, however, the user must provide a
 reference to use to refer to the underlying lock when locking and unlocking,
 and unlock may generate an error.