X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=ha-manager.adoc;h=582dfcc91838efb249856775698de42f548997ef;hb=77d64ef718ef2898788d8b7e267104f0de1a6a9c;hp=a357d16c6592e70aed7d54ce1467e063f4b8469e;hpb=345f5fe0fcfb01f6bad73162c68b21b8c6427745;p=pve-docs.git

diff --git a/ha-manager.adoc b/ha-manager.adoc
index a357d16..582dfcc 100644
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -1,15 +1,16 @@
-[[chapter-ha-manager]]
+[[chapter_ha_manager]]
 ifdef::manvolnum[]
-PVE({manvolnum})
-================
+ha-manager(1)
+=============
 include::attributes.txt[]
+:pve-toplevel:
 
 NAME
 ----
 
 ha-manager - Proxmox VE HA Manager
 
-SYNOPSYS
+SYNOPSIS
 --------
 
 include::ha-manager.1-synopsis.adoc[]
@@ -17,14 +18,13 @@ include::ha-manager.1-synopsis.adoc[]
 DESCRIPTION
 -----------
 endif::manvolnum[]
-
 ifndef::manvolnum[]
 High Availability
 =================
 include::attributes.txt[]
+:pve-toplevel:
 endif::manvolnum[]
 
-
 Our modern society depends heavily on information provided by
 computers over the network. Mobile devices amplified that dependency,
 because people can access the network any time from anywhere. If you
@@ -122,6 +122,7 @@ Requirements
 * optional hardware fencing devices
 
 
+[[ha_manager_resources]]
 Resources
 ---------
 
@@ -311,6 +312,7 @@ the update process can be too long which, in the worst case, may result in
 a watchdog reset.
 
 
+[[ha_manager_fencing]]
 Fencing
 -------
 
@@ -380,6 +382,7 @@ That minimizes the possibility of an overload, which else could cause an
 unresponsive node and as a result a chain reaction of node failures in the
 cluster.
 
+[[ha_manager_groups]]
 Groups
 ------
 
@@ -422,7 +425,7 @@ The resource won't automatically fail back when a more preferred node
   Examples;;
   * You need to migrate a service to a node which hasn't the highest priority
   in the group at the moment, to tell the HA manager to not move this service
-  instantly back set the 'nofailnback' option and the service will stay on
+  instantly back set the 'nofailback' option and the service will stay on
   the current node.
 
   * A service was fenced and it got recovered to another node. The admin