aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2020-11-12 23:29:51 +0100
committerGitHub <noreply@github.com>2020-11-12 23:29:51 +0100
commit2fc2d4643ee699b8efc97f23850d5a37c4a85b89 (patch)
treea46a03036da7eb12776c18632024d8a6efc81456 /docs
parenta65ecc70c21eb5eef7d7a6b70cc1f90e577bb72e (diff)
parenta7431003b8d53b3cc012a74c4015beac624f40f1 (diff)
downloadpodman-2fc2d4643ee699b8efc97f23850d5a37c4a85b89.tar.gz
podman-2fc2d4643ee699b8efc97f23850d5a37c4a85b89.tar.bz2
podman-2fc2d4643ee699b8efc97f23850d5a37c4a85b89.zip
Merge pull request #8316 from rhatdan/codespell
Fix issues found with codespell
Diffstat (limited to 'docs')
-rw-r--r--docs/Readme.md2
-rw-r--r--docs/source/markdown/podman-build.1.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/Readme.md b/docs/Readme.md
index c517052b3..ae0067be6 100644
--- a/docs/Readme.md
+++ b/docs/Readme.md
@@ -51,4 +51,4 @@ If reloading the page, or clearing your local cache does not fix the problem, it
likely caused by broken metadata needed to protect clients from cross-site-scripting
style attacks. Please [notify a maintainer](https://github.com/containers/podman#communications)
so they may investigate how/why the `swagger.yaml` file's CORS-metadata is
-incorrect, or the file isn't accessable for some other reason.
+incorrect, or the file isn't accessible for some other reason.
diff --git a/docs/source/markdown/podman-build.1.md b/docs/source/markdown/podman-build.1.md
index f9568b5d3..4f11fe08e 100644
--- a/docs/source/markdown/podman-build.1.md
+++ b/docs/source/markdown/podman-build.1.md
@@ -721,7 +721,7 @@ container. When the mount propagation policy is set to `slave`, one way mount
propagation is enabled and any mounts completed on the host for that volume will
be visible only inside of the container. To control the mount propagation
property of volume use the `:[r]shared`, `:[r]slave` or `:[r]private`
-propagation flag. The propagation property canbe specified only for bind mounted
+propagation flag. The propagation property can be specified only for bind mounted
volumes and not for internal volumes or named volumes. For mount propagation to
work on the source mount point (mount point where source dir is mounted on) has
to have the right propagation properties. For shared volumes, the source mount