pvecm: fix corosync link priority description

The official man page fixed this in commit 0a323ff [0] to describe the
actual behaviour: higher knet_link_priority number equals to higher
priority

[0] https://github.com/corosync/corosync/commit/0a323ff2ed0f2aff9cb691072906e69cb96ed662

Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>

diff --git a/pvecm.adoc b/pvecm.adoc
index 5a73c1e03bf7e41a9917d7446957b79c6ef7d69c..72e7c024c954ecc93ddf9b39f4f73aba724ffbcc 100644 (file)
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -762,10 +762,10 @@ by setting 'knet_link_priority' in the corresponding interface section in
 your cluster with `pvecm`:
 
 ----
- # pvecm create CLUSTERNAME --link0 10.10.10.1,priority=20 --link1 10.20.20.1,priority=15
+ # pvecm create CLUSTERNAME --link0 10.10.10.1,priority=15 --link1 10.20.20.1,priority=20
 ----
 
-This would cause 'link1' to be used first, since it has the lower priority.
+This would cause 'link1' to be used first, since it has the higher priority.
 
 If no priorities are configured manually (or two links have the same priority),
 links will be used in order of their number, with the lower number having higher