From: Nicolas Frey <n.frey@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 1/1] pvecm: fix typos and add missing comma
Date: Wed, 28 Jan 2026 16:25:36 +0100 [thread overview]
Message-ID: <20260128152536.196453-1-n.frey@proxmox.com> (raw)
Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
---
pvecm.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pvecm.adoc b/pvecm.adoc
index 10b4b16..d12dde7 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -505,7 +505,7 @@ killall pmxcfs
systemctl start pve-cluster
----
-The node is now separated from the cluster. You can deleted it from any
+The node is now separated from the cluster. You can delete it from any
remaining node of the cluster with:
[source,bash]
----
@@ -582,7 +582,7 @@ is not guaranteed and gets rather unlikely with more than three nodes and
latencies above around 10 ms.
The network should not be used heavily by other members, as while corosync does
-not uses much bandwidth it is sensitive to latency jitters; ideally corosync
+not use much bandwidth, it is sensitive to latency jitters; ideally corosync
runs on its own physically separated network. Especially do not use a shared
network for corosync and storage (except as a potential low-priority fallback
in a xref:pvecm_redundancy[redundant] configuration).
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2026-01-28 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 15:25 Nicolas Frey [this message]
2026-01-29 9:37 ` applied: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260128152536.196453-1-n.frey@proxmox.com \
--to=n.frey@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox