X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=pvecm.adoc;h=8db8e473202f7921456b6cdd40c81e3619bce725;hb=aa56b7e0f6515ed141d5936969e7951326019745;hp=ed468f54e2014d36773a6e98ca6c5d7c25a41800;hpb=b2f242abe4c50227f5610767e6fcaa40654c2b88;p=pve-docs.git

diff --git a/pvecm.adoc b/pvecm.adoc
index ed468f5..8db8e47 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -1,7 +1,6 @@
 ifdef::manvolnum[]
 pvecm(1)
 ========
-include::attributes.txt[]
 :pve-toplevel:
 
 NAME
@@ -21,11 +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
@@ -297,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
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -667,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
@@ -723,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.