From 3fd12ad26ee27dd5ee27a156abc8c686c9b1d65c Mon Sep 17 00:00:00 2001
From: Daryl White <53910321+djwfyi@users.noreply.github.com>
Date: Thu, 30 Jan 2025 08:38:29 -0500
Subject: [PATCH] Correct upgrade command (#1401)

Per internal discussion, the command to update MinIO in an airgapped
environment should point to `minio.sha256sum`.
---
 source/includes/linux/steps-upgrade-minio-deployment.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/includes/linux/steps-upgrade-minio-deployment.rst b/source/includes/linux/steps-upgrade-minio-deployment.rst
index c0317174..b8d06e10 100644
--- a/source/includes/linux/steps-upgrade-minio-deployment.rst
+++ b/source/includes/linux/steps-upgrade-minio-deployment.rst
@@ -123,7 +123,7 @@ Airgapped or internet-isolated deployments may utilize this feature for updating
 .. code-block:: shell
    :class: copyable
 
-   mc admin update ALIAS https://minio-mirror.example.com/minio
+   mc admin update ALIAS https://minio-mirror.example.com/minio.sha256sum
 
 You should upgrade your :mc:`mc` binary to match or closely follow the MinIO server release. 
 You can use the :mc:`mc update` command to update the binary to the latest stable release: