From a8afbc146571681df952cf2f316c245b9ffab67b Mon Sep 17 00:00:00 2001
From: Daryl White <53910321+djwfyi@users.noreply.github.com>
Date: Mon, 6 Nov 2023 10:47:05 -0500
Subject: [PATCH] [Community request] Clarify Operator upgrade (#1062)

Operator upgrade docs for 4.2.3 to 4.5.8 had an incorrect sentence
saying the procedure could upgrade directly to latest stable.
This updates the description to clarify that upgrade should first
upgrade to 4.5.8.

This was noted by a community Slack user.
---
 .../install-deploy-manage/upgrade-minio-operator.rst           | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/source/operations/install-deploy-manage/upgrade-minio-operator.rst b/source/operations/install-deploy-manage/upgrade-minio-operator.rst
index a82ebcb7..c0dc7889 100644
--- a/source/operations/install-deploy-manage/upgrade-minio-operator.rst
+++ b/source/operations/install-deploy-manage/upgrade-minio-operator.rst
@@ -203,7 +203,8 @@ This procedure requires the following:
 Procedure
 ~~~~~~~~~
 
-This procedure upgrades the MinIO Operator from any 4.2.3 or later release to |operator-version-stable|.
+This procedure upgrades MinIO Operator release 4.2.3 through 4.5.7 to release 4.5.8.
+You can then upgrade from release 4.5.8 to |operator-version-stable|.
 
 1. *(Optional)* Update each MinIO Tenant to the latest stable MinIO Version.