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 573941FF141 for ; Fri, 13 Feb 2026 17:09:18 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A9820B450; Fri, 13 Feb 2026 17:10:01 +0100 (CET) From: Nicolas Frey To: pve-devel@lists.proxmox.com Subject: [PATCH pve-docs 1/3] pveceph: fix typo Date: Fri, 13 Feb 2026 17:09:54 +0100 Message-ID: <20260213160956.224162-2-n.frey@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260213160956.224162-1-n.frey@proxmox.com> References: <20260213160956.224162-1-n.frey@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.123 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 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Message-ID-Hash: 26N25ZPVBWPCBCOPQBZFEPGF4D7MWZX6 X-Message-ID-Hash: 26N25ZPVBWPCBCOPQBZFEPGF4D7MWZX6 X-MailFrom: nfrey@miso.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: Nicolas Frey --- pveceph.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pveceph.adoc b/pveceph.adoc index 2ddddf1..f6ca5f0 100644 --- a/pveceph.adoc +++ b/pveceph.adoc @@ -258,7 +258,7 @@ The configuration step includes the following settings: required. + Separating your Ceph traffic from the {pve} cluster communication (corosync), - and possible the front-facing (public) networks of your virtual guests, is + and possibly the front-facing (public) networks of your virtual guests, is highly recommended. Otherwise, Ceph's high-bandwidth IO-traffic could cause interference with other low-latency dependent services. -- 2.47.3