From: Dylan Whyte <d.whyte@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 2/6] pvecm: replace {PVE} with {pve}
Date: Wed, 15 Sep 2021 15:36:14 +0200 [thread overview]
Message-ID: <20210915133618.143859-2-d.whyte@proxmox.com> (raw)
In-Reply-To: <20210915133618.143859-1-d.whyte@proxmox.com>
although they both act the same, {pve} is more common throughout the
docs, so this helps to keep things more consistent
Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
---
pvecm.adoc | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/pvecm.adoc b/pvecm.adoc
index 547a013..2d1c744 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -24,7 +24,7 @@ Cluster Manager
:pve-toplevel:
endif::manvolnum[]
-The {PVE} cluster manager `pvecm` is a tool to create a group of
+The {pve} cluster manager `pvecm` is a tool to create a group of
physical servers. Such a group is called a *cluster*. We use the
http://www.corosync.org[Corosync Cluster Engine] for reliable group
communication. There's no explicit limit for the number of nodes in a cluster.
@@ -90,7 +90,7 @@ upgrade procedure to {pve} 6.0.
Preparing Nodes
---------------
-First, install {PVE} on all nodes. Make sure that each node is
+First, install {pve} on all nodes. Make sure that each node is
installed with the final hostname and IP configuration. Changing the
hostname and IP is not possible after cluster creation.
@@ -871,10 +871,10 @@ pvecm status
If you see a healthy cluster state, it means that your new link is being used.
-Role of SSH in {PVE} Clusters
+Role of SSH in {pve} Clusters
-----------------------------
-{PVE} utilizes SSH tunnels for various features.
+{pve} utilizes SSH tunnels for various features.
* Proxying console/shell sessions (node and guests)
+
--
2.30.2
next prev parent reply other threads:[~2021-09-15 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 13:36 [pve-devel] [PATCH pve-docs 1/6] pvecm: language and format fixup Dylan Whyte
2021-09-15 13:36 ` Dylan Whyte [this message]
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 3/6] pvecm: fix command output formatting Dylan Whyte
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 4/6] pvecm: update instructions to add redundant links Dylan Whyte
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 5/6] pvecm: add note about corosync killnode error Dylan Whyte
2021-09-16 8:04 ` Fabian Ebner
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 6/6] fix 3375: warn user to remove replication jobs Dylan Whyte
2021-09-15 15:03 ` [pve-devel] applied-series: [PATCH pve-docs 1/6] pvecm: language and format fixup 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=20210915133618.143859-2-d.whyte@proxmox.com \
--to=d.whyte@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