From e8185388581e4354847553b0ce0a06c1592cb77e Mon Sep 17 00:00:00 2001 From: Marty Hernandez Avedon Date: Mon, 29 Apr 2024 11:57:14 -0400 Subject: [PATCH] Update docs/getting-started/installation-and-upgrade/other-installation-methods/air-gapped-helm-cli-install/publish-images.md --- .../air-gapped-helm-cli-install/publish-images.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/getting-started/installation-and-upgrade/other-installation-methods/air-gapped-helm-cli-install/publish-images.md b/docs/getting-started/installation-and-upgrade/other-installation-methods/air-gapped-helm-cli-install/publish-images.md index afef034ad3a4..48a5a13453e7 100644 --- a/docs/getting-started/installation-and-upgrade/other-installation-methods/air-gapped-helm-cli-install/publish-images.md +++ b/docs/getting-started/installation-and-upgrade/other-installation-methods/air-gapped-helm-cli-install/publish-images.md @@ -283,8 +283,8 @@ Move the images in the `rancher-images.tar.gz` to your private registry using th The image list, `rancher-images.txt` or `rancher-windows-images.txt`, is expected to be on the workstation in the same directory that you are running the `rancher-load-images.sh` script. The `rancher-images.tar.gz` should also be in the same directory. -1. Ensure that the rancher project is created in your private registry. - Otherwise, an error will be reported like project rancher not found. +1. Ensure that the Rancher project is in your private registry. + If not, you'll see an error message, such as, "project rancher not found". 2. Log into your private registry if required: ```plain