From abe1bb9757932bed0c10cd74014cac6f67dab6d0 Mon Sep 17 00:00:00 2001 From: zhoulin xie Date: Sun, 20 Jan 2019 01:20:34 +0800 Subject: [PATCH] Fix some typos in manifest.md Signed-off-by: zhoulin xie --- docs/reference/commandline/manifest.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/commandline/manifest.md b/docs/reference/commandline/manifest.md index ce31a30d69..13beb9cdde 100644 --- a/docs/reference/commandline/manifest.md +++ b/docs/reference/commandline/manifest.md @@ -177,7 +177,7 @@ This is similar to tagging an image and pushing it to a foreign registry. After you have created your local copy of the manifest list, you may optionally `annotate` it. Annotations allowed are the architecture and operating system (overriding the image's current values), -os features, and an archictecure variant. +os features, and an architecture variant. Finally, you need to `push` your manifest list to the desired registry. Below are descriptions of these three commands, and an example putting them all together. @@ -270,5 +270,5 @@ $ docker manifest create --insecure myprivateregistry.mycompany.com/repo/image:1 $ docker manifest push --insecure myprivateregistry.mycompany.com/repo/image:tag ``` -Note that the `--insecure` flag is not required to annotate a manifest list, since annotations are to a locally-stored copy of a manifest list. You may also skip the `--insecure` flag if you are performaing a `docker manifest inspect` on a locally-stored manifest list. Be sure to keep in mind that locally-stored manifest lists are never used by the engine on a `docker pull`. +Note that the `--insecure` flag is not required to annotate a manifest list, since annotations are to a locally-stored copy of a manifest list. You may also skip the `--insecure` flag if you are performing a `docker manifest inspect` on a locally-stored manifest list. Be sure to keep in mind that locally-stored manifest lists are never used by the engine on a `docker pull`.