From 97297af5efe1a7a04a98aadf6bdf206afa71b9bf Mon Sep 17 00:00:00 2001 From: Kobayashi Daisuke Date: Tue, 6 Aug 2019 09:25:54 +0900 Subject: [PATCH] Only one word typo fix (#15617) * Fix typo * Fix typo * Cange back to "will" --- content/en/docs/concepts/containers/images.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/containers/images.md b/content/en/docs/concepts/containers/images.md index b2f374ea06..c408cc1e6b 100644 --- a/content/en/docs/concepts/containers/images.md +++ b/content/en/docs/concepts/containers/images.md @@ -70,7 +70,7 @@ Credentials can be provided in several ways: - Configuring Nodes to Authenticate to a Private Registry - all pods can read any configured private registries - requires node configuration by cluster administrator - - Pre-pulling Images + - Pre-pulled Images - all pods can use any images cached on a node - requires root access to all nodes to setup - Specifying ImagePullSecrets on a Pod @@ -243,7 +243,7 @@ template needs to include the `.docker/config.json` or mount a drive that contai All pods will have read access to images in any private registry once private registry keys are added to the `.docker/config.json`. -### Pre-pulling Images +### Pre-pulled Images {{< note >}} If you are running on Google Kubernetes Engine, there will already be a `.dockercfg` on each node with credentials for Google Container Registry. You cannot use this approach.