diff --git a/xml/ha_fencing.xml b/xml/ha_fencing.xml
index edc7add1..6cb59fba 100644
--- a/xml/ha_fencing.xml
+++ b/xml/ha_fencing.xml
@@ -295,7 +295,7 @@
    resources means loading and unloading the &stonith; device driver on a
    node. Starting and stopping are thus only administrative operations and
    do not translate to any operation on the fencing device itself. However,
-   monitoring does translate to logging it to the device (to verify that the
+   monitoring does translate to logging in to the device (to verify that the
    device will work in case it is needed). When a &stonith; resource fails
    over to another node it enables the current node to talk to the &stonith;
    device by loading the respective driver.
@@ -536,17 +536,6 @@ hostlist</screen>
    monitoring operation for checking status.
   </para>
 
-<!--fate#310010-->
-
-  <note>
-   <title>Monitoring &stonith; resources</title>
-   <para>
-    Monitor &stonith; resources regularly, yet sparingly. For most devices a
-    monitoring interval of at least 1800 seconds (30 minutes) should
-    suffice.
-   </para>
-  </note>
-
   <para>
    Fencing devices are an indispensable part of an HA cluster, but the less
    you need to use them, the better. Power management equipment is often
@@ -557,9 +546,12 @@ hostlist</screen>
   </para>
 
   <para>
-   Checking the status of fencing devices once every few hours should
-   be enough. The probability that a fencing operation needs to be
-   performed and the power switch fails is low.
+   The probability that a fencing operation needs to be performed and the
+   fencing device fails is low. For most devices, a monitoring interval of
+   at least 1800 seconds (30 minutes) should suffice. The exact value depends
+   on the device and infrastructure. &stonith; SBD resources do not need a
+   monitor at all. See <xref linkend="sec-ha-fencing-special"/> and
+   <xref linkend="cha-ha-storage-protect"/>.
   </para>
 
   <para>