summaryrefslogtreecommitdiff
path: root/docs/podman-image-sign.1.md
diff options
context:
space:
mode:
authorDaniel J Walsh <dwalsh@redhat.com>2019-07-11 17:56:54 -0400
committerDaniel J Walsh <dwalsh@redhat.com>2019-07-11 17:56:54 -0400
commit369f8b8862e8918a011290311e44c1691f699c58 (patch)
treec7d317eaeceb44139fa99813c2e4fa3efe2cb1c1 /docs/podman-image-sign.1.md
parentefe9c5b0e7968473b261eae4641e422e4a0f69a2 (diff)
downloadpodman-369f8b8862e8918a011290311e44c1691f699c58.tar.gz
podman-369f8b8862e8918a011290311e44c1691f699c58.tar.bz2
podman-369f8b8862e8918a011290311e44c1691f699c58.zip
Fix spelling mistakes in man pages and other docs
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'docs/podman-image-sign.1.md')
-rw-r--r--docs/podman-image-sign.1.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/podman-image-sign.1.md b/docs/podman-image-sign.1.md
index c425fcf2e..61df3b3bd 100644
--- a/docs/podman-image-sign.1.md
+++ b/docs/podman-image-sign.1.md
@@ -7,7 +7,7 @@ podman-image-sign - Create a signature for an image
**podman image sign** [*options*] *image* [*image* ...]
## DESCRIPTION
-**podmain image sign** will create a local signature for one or more local images that have
+**podman image sign** will create a local signature for one or more local images that have
been pulled from a registry. The signature will be written to a directory
derived from the registry configuration files in /etc/containers/registries.d. By default, the signature will be written into /var/lib/containers/sigstore directory.
@@ -39,8 +39,8 @@ docker:
privateregistry.example.com:
sigstore: file:///var/lib/containers/sigstore
-When signing an image preceeded with the registry name 'privateregistry.example.com',
-the signature will be written into subdirectories of
+When signing an image preceded with the registry name 'privateregistry.example.com',
+the signature will be written into sub-directories of
/var/lib/containers/sigstore/privateregistry.example.com. The use of 'sigstore' also means
the signature will be 'read' from that same location on a pull-related function.