From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 8DAE61FF141 for ; Mon, 30 Mar 2026 15:40:27 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1834E31CEF; Mon, 30 Mar 2026 15:40:54 +0200 (CEST) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Subject: [PATCH docs 1/4] ha-manager: fix enabled typo Date: Mon, 30 Mar 2026 15:40:15 +0200 Message-ID: <20260330134019.419391-2-m.sandoval@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260330134019.419391-1-m.sandoval@proxmox.com> References: <20260330134019.419391-1-m.sandoval@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1774877965592 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.126 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: OLPJZXWLL45YSAWPTHSYVZMCMYHPUWY3 X-Message-ID-Hash: OLPJZXWLL45YSAWPTHSYVZMCMYHPUWY3 X-MailFrom: m.sandoval@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Signed-off-by: Maximiliano Sandoval --- ha-manager.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index 4c318fb..859721d 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -1116,7 +1116,7 @@ During each migration, the original node will be recorded in the HA managers' state, so that the service can be moved back again automatically once the maintenance mode is disabled and the node is back online. -Currently you can enabled or disable the maintenance mode using the ha-manager +Currently you can enable or disable the maintenance mode using the ha-manager CLI tool. .Enabling maintenance mode for a node -- 2.47.3