X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=pvecm.adoc;h=8db8e473202f7921456b6cdd40c81e3619bce725;hp=00d558dc0c74431d00a6feb7fcc97c116be393bc;hb=863a8f3a781d4c7493dcac0175abc0f52c37a046;hpb=404a158e1b79f205df7f5cf1827dde32ef9a8ea2

diff --git a/pvecm.adoc b/pvecm.adoc
index 00d558d..8db8e47 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -1,7 +1,6 @@
 ifdef::manvolnum[]
-PVE(1)
-======
-include::attributes.txt[]
+pvecm(1)
+========
 :pve-toplevel:
 
 NAME
@@ -21,12 +20,8 @@ endif::manvolnum[]
 ifndef::manvolnum[]
 Cluster Manager
 ===============
-include::attributes.txt[]
-endif::manvolnum[]
-
-ifdef::wiki[]
 :pve-toplevel:
-endif::wiki[]
+endif::manvolnum[]
 
 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
@@ -298,6 +293,7 @@ cluster again, you have to
 
 * then join it, as explained in the previous section.
 
+[[pvecm_separate_node_without_reinstall]]
 Separate A Node Without Reinstalling
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -668,8 +664,9 @@ RRP On A Created Cluster
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
 When enabling an already running cluster to use RRP you will take similar steps
-as describe in <<separate-cluster-net-after-creation,separating the cluster
-network>>. You just do it on another ring.
+as describe in
+<<separate-cluster-net-after-creation,separating the cluster network>>. You
+just do it on another ring.
 
 First add a new `interface` subsection in the `totem` section, set its
 `ringnumber` property to `1`. Set the interfaces `bindnetaddr` property to an
@@ -724,8 +721,8 @@ nodelist {
 
 ----
 
-Bring it in effect like described in the <<edit-corosync-conf,edit the
-corosync.conf file>> section.
+Bring it in effect like described in the
+<<edit-corosync-conf,edit the corosync.conf file>> section.
 
 This is a change which cannot take live in effect and needs at least a restart
 of corosync. Recommended is a restart of the whole cluster.