From e006576babdb519fa5f87861f7dadce5f42d9692 Mon Sep 17 00:00:00 2001
From: Tahlia Richardson <3069029+tahliar@users.noreply.github.com>
Date: Fri, 20 Sep 2024 10:43:29 +1000
Subject: [PATCH] Apply suggestions from code review

Co-authored-by: Roger Zhou <zzhou@suse.com>
---
 xml/ha_fencing.xml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/ha_fencing.xml b/xml/ha_fencing.xml
index 306fdafb..3c50bce0 100644
--- a/xml/ha_fencing.xml
+++ b/xml/ha_fencing.xml
@@ -461,14 +461,14 @@ hostlist</screen>
    <procedure>
     <step>
     <para>
-     Use the <literal>stonith:fence_kdump</literal> resource agent
-     to monitor all nodes with the Kdump function enabled. A
-     configuration example is shown below. For more information,
+     Use the <literal>stonith:fence_kdump</literal> fence agent. 
+     A configuration example is shown below. For more information,
      see <command>crm ra info stonith:fence_kdump</command>.
     </para>
 <screen>&prompt.root;<command>crm configure</command>
 &prompt.crm.conf;<command>primitive st-kdump stonith:fence_kdump \
     params nodename="&node1; "\ </command><co xml:id="co-ha-fence-kdump-nodename"/>
+    pcmk_host_list="&node1;" \
     <command>pcmk_host_check="static-list" \
     pcmk_reboot_action="off" \
     pcmk_monitor_action="metadata" \
@@ -478,17 +478,17 @@ hostlist</screen>
     <calloutlist>
      <callout arearefs="co-ha-fence-kdump-nodename">
       <para>
-       Name of the node to be monitored. If you need to monitor more than one
-       node, configure more &stonith; resources. To prevent a specific node
-       from using a fencing device, add location constraints.
+       Name of the node to listen a message from <literal>fence_kdump_send</literal>. 
+       Configure more &stonith; resources for other nodes if need.
       </para>
      </callout>
      <callout arearefs="co-ha-fence-kdump-timeout">
        <para>
         Defines how long to wait for a message from <literal>fence_kdump_send</literal>.
         If a message is received, then a Kdump is in progress and the fencing mechanism
-        considers the node to be fenced. If no message is received during this timeout,
-        then no Kdump is in progress and the &stonith; device fences the node.
+        considers the node to be fenced. If no message is received, then fence_dump get 
+        timeout and that indicates the fence operation failed. The next &stonith;  
+        device in the fence_topology fences the node eventually.
        </para>
      </callout>
     </calloutlist>