pvecm.adoc: small cleanups

diff --git a/pvecm.adoc b/pvecm.adoc
index 84eb411bde9ec50b2283d0c07bb2f9b7df08da1f..1a3a7e8f51b23890e3fadf0b8f0777faa596b34e 100644 (file)
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -113,10 +113,10 @@ Login via 'ssh' to the node you want to add.
 For `IP-ADDRESS-CLUSTER` use the IP from an existing cluster node.
 
 CAUTION: A new node cannot hold any VM´s, because you would get
 For `IP-ADDRESS-CLUSTER` use the IP from an existing cluster node.
 
 CAUTION: A new node cannot hold any VM´s, because you would get

-conflicts about identical VM IDs. Also, all existing configuration is
-overwritten when you join a new node to the cluster. To workaround,
-use vzdump to backup and restore to a different VMID after adding
-the node to the cluster.
+conflicts about identical VM IDs. Also, all existing configuration in
+'/etc/pve' is overwritten when you join a new node to the cluster. To
+workaround, use vzdump to backup and restore to a different VMID after
+adding the node to the cluster.

 
 To check the state of cluster:
 
 
 To check the state of cluster:
 


@@ -179,7 +179,7 @@ Move all virtual machines from the node. Make sure you have no local
 data or backups you want to keep, or save them accordingly.
 
 Log in to one remaining node via ssh. Issue a 'pvecm nodes' command to
 data or backups you want to keep, or save them accordingly.
 
 Log in to one remaining node via ssh. Issue a 'pvecm nodes' command to

-identify the nodeID:
+identify the node ID:

 
 ----
 hp1# pvecm status
 
 ----
 hp1# pvecm status