diff options
| author | Daniel J Walsh <dwalsh@redhat.com> | 2018-02-19 12:51:25 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-02-19 12:51:25 -0500 |
| commit | 32efbbdf8a2a3caf628adeef7c0ad49ad8de2c88 (patch) | |
| tree | 64917bb417cd5263fe47ffe4b19efbbed984a311 | |
| parent | 07f15c26945eada770a30655b43cadcbb62bf2ae (diff) | |
| parent | 2cfe9cbf38db6cf9e2cc68e634e731c0299f869d (diff) | |
| download | podman-32efbbdf8a2a3caf628adeef7c0ad49ad8de2c88.tar.gz podman-32efbbdf8a2a3caf628adeef7c0ad49ad8de2c88.tar.bz2 podman-32efbbdf8a2a3caf628adeef7c0ad49ad8de2c88.zip | |
Merge pull request #357 from edsantiago/vice-versa
language: correct 'vice versa' in docs
| -rw-r--r-- | docs/podman-create.1.md | 4 | ||||
| -rw-r--r-- | docs/podman-run.1.md | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/docs/podman-create.1.md b/docs/podman-create.1.md index f40b73317..7d2b62fb0 100644 --- a/docs/podman-create.1.md +++ b/docs/podman-create.1.md @@ -512,10 +512,10 @@ The `Z` option tells podman to label the content with a private unshared label. Only the current container can use a private volume. By default bind mounted volumes are `private`. That means any mounts done -inside container will not be visible on host and vice-a-versa. One can change +inside container will not be visible on host and vice versa. One can change this behavior by specifying a volume mount propagation property. Making a volume `shared` mounts done under that volume inside container will be -visible on host and vice-a-versa. Making a volume `slave` enables only one +visible on host and vice versa. Making a volume `slave` enables only one way mount propagation and that is mounts done on host under that volume will be visible inside container but not the other way around. diff --git a/docs/podman-run.1.md b/docs/podman-run.1.md index 3cb25cdae..53239422d 100644 --- a/docs/podman-run.1.md +++ b/docs/podman-run.1.md @@ -512,10 +512,10 @@ The `Z` option tells podman to label the content with a private unshared label. Only the current container can use a private volume. By default bind mounted volumes are `private`. That means any mounts done -inside container will not be visible on host and vice-a-versa. One can change +inside container will not be visible on host and vice versa. One can change this behavior by specifying a volume mount propagation property. Making a volume `shared` mounts done under that volume inside container will be -visible on host and vice-a-versa. Making a volume `slave` enables only one +visible on host and vice versa. Making a volume `slave` enables only one way mount propagation and that is mounts done on host under that volume will be visible inside container but not the other way around. |