From 88b25bc20cbec70681d13f02cd2e30d9a68a94bd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Luc=C3=ADa=20M=2E=20Polis?=
 <mig281@users.noreply.github.com>
Date: Thu, 28 Nov 2024 22:54:25 -0800
Subject: [PATCH] Update performing-upgrades.md

---
 .../admin-guides/upgrading-qumulo-core/performing-upgrades.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/_includes/content-reuse/admin-guides/upgrading-qumulo-core/performing-upgrades.md b/_includes/content-reuse/admin-guides/upgrading-qumulo-core/performing-upgrades.md
index 2b8d510d..2741cab8 100644
--- a/_includes/content-reuse/admin-guides/upgrading-qumulo-core/performing-upgrades.md
+++ b/_includes/content-reuse/admin-guides/upgrading-qumulo-core/performing-upgrades.md
@@ -8,7 +8,7 @@
 
 {{site.nexusDownloads}} {{site.loginRequired}}.
 
-{% if page.platform == 'cnq-aws' %}
+{% if page.platform != 'cnq-aws' %}
 ## Understanding the Differences Between Upgrade Modes
 For information about which upgrade modes different Qumulo Core releases use, see [Qumulo Core Upgrade Mode Reference](mode-reference.html).
 
@@ -68,7 +68,7 @@ Every Qumulo Core upgrade has two phases, _preparation_ and _commit_.
 ## Upgrading Your Qumulo Cluster
 {{site.data.alerts.important}}
 <ul>
-  <li>Before beginning the upgrade process, make sure that you have the {% if page.platform == 'cnq-aws' %}correct <a href="https://nexus.qumulo.com/downloads?platform=cloud">cloud upgrade image</a>{{site.loginRequired}} or{% endif %} <a href="https://nexus.qumulo.com/downloads?platform=onprem">on-premises upgrade image</a>{{site.loginRequired}}. {% if page.platform == 'cnq-aws' %}{{site.cnqShort}} uses the <a href="https://docs.qumulo.com/administrator-guide/getting-started/installing-product-package.html">Qumulo Core Product Package</a> (which doesn't have separate versions for on-premises and cloud platforms) as a deployment artifact. For this reason, you must use the on-premises upgrade image to upgrade a {{site.cnqShort}} cluster.{% endif %}</li>
+  <li>Before beginning the upgrade process, make sure that you have the {% if page.platform != 'cnq-aws' %}correct <a href="https://nexus.qumulo.com/downloads?platform=cloud">cloud upgrade image</a>{{site.loginRequired}} or{% endif %} <a href="https://nexus.qumulo.com/downloads?platform=onprem">on-premises upgrade image</a>{{site.loginRequired}}. {% if page.platform != 'cnq-aws' %}{{site.cnqShort}} uses the <a href="https://docs.qumulo.com/administrator-guide/getting-started/installing-product-package.html">Qumulo Core Product Package</a> (which doesn't have separate versions for on-premises and cloud platforms) as a deployment artifact. For this reason, you must use the on-premises upgrade image to upgrade a {{site.cnqShort}} cluster.{% endif %}</li>
   <li>To allow certain background processes to run, multiple sequential Qumulo Core upgrades might require a waiting period between specific releases. Before installing multiple Qumulo Core releases within an extended maintenance window, {{site.contactQumuloCare}}.</li>
   <li>When the node to which you are connected reboots, the Qumulo Core Web UI might redirect you to the <strong>Cluster is booting...</strong> page. To view the reboot status, you can connect to a different node or wait until the current node goes online and then click <strong>Support > Software Upgrade</strong>.</li>
   <li>During rolling reboots, the system reboots one or more nodes (depending on the configured protection level) in the cluster in succession. If your cluster is under heavy load due to write or delete operations, this process can take a long time.</li>