diff --git a/xml/ha_bootstrap_install.xml b/xml/ha_bootstrap_install.xml
index bb646ca9..ef18926b 100644
--- a/xml/ha_bootstrap_install.xml
+++ b/xml/ha_bootstrap_install.xml
@@ -12,7 +12,7 @@
  xmlns="http://docbook.org/ns/docbook" version="5.1"
  xmlns:xi="http://www.w3.org/2001/XInclude"
  xmlns:xlink="http://www.w3.org/1999/xlink">
-  <title>Using the bootstrap script</title>
+  <title>Using the bootstrap scripts</title>
   <info>
     <abstract>
       <para>
@@ -158,7 +158,7 @@
       </para>
       <para>
         You can start the script without specifying any options. This prompts you for input for
-        some settings, as described in the next steps, and uses &crmsh;'s default values for
+        certain settings as described in later steps, and uses &crmsh;'s default values for
         other settings.
       </para>
       <itemizedlist>
@@ -225,6 +225,11 @@
               <option>--sbd-device</option> (or <option>-s</option>) multiple times. For example:
             </para>
 <screen>&prompt.root;<command>crm cluster init --sbd-device /dev/disk/by-id/<replaceable>ID1</replaceable> --sbd-device /dev/disk/by-id/<replaceable>ID2</replaceable></command></screen>
+            <para>
+              This option is also useful because you can use tab completion for the device ID,
+              which is not available later when the script prompts you for the path.
+            </para>
+            <!-- Add more info about using multiple SBD disks, like for SAP -->
           </listitem>
         </varlistentry>
         <varlistentry>
@@ -352,7 +357,7 @@
             Choose whether to enable TLS.
           </para>
         </step>
-        <step performance="optional">
+        <step>
           <para>
             Enter heuristics commands to affect how votes are determined. To skip this step, leave
             the field blank.
@@ -430,27 +435,25 @@ crm cluster join --use-ssh-agent -c <replaceable>USER</replaceable>@<replaceable
         </listitem>
       </itemizedlist>
       <para>
-        If NTP is not configured to start at boot time, a message
-        appears. The script also checks for a hardware watchdog device.
-        You are warned if none is present.
+        If NTP is not configured to start at boot time, a message appears. The script also checks
+        for a hardware watchdog device. You are warned if none is present.
       </para>
     </step>
     <step>
       <para>
-      If you did not already specify the first cluster node
-      with <option>-c</option>, you will be prompted for its IP address.
+        If you did not already specify the first cluster node with <option>-c</option>,
+        you are prompted for its IP address.
       </para>
     </step>
     <step>
       <para>
         If you did not already configure passwordless SSH access between the cluster nodes,
-        you will be prompted for the password of the first node.
+        you are prompted for the password of the first node.
       </para>
       <para>
-        After logging in to the specified node, the script copies the
-        &corosync; configuration, configures SSH and &csync;,
-        brings the current machine online as a new cluster node, and
-        starts the service needed for &hawk2;.
+        After logging in to the specified node, the script copies the &corosync; configuration,
+        configures SSH and &csync;, brings the current machine online as a new cluster node,
+        and starts the service needed for &hawk2;.
       </para>
     </step>
     </procedure>
@@ -467,4 +470,32 @@ crm cluster join --use-ssh-agent -c <replaceable>USER</replaceable>@<replaceable
       TO DO
     </para>
   </sect1>
+
+  <sect1 xml:id="sec-ha-install-cluster-remove">
+    <title>Removing nodes with <command>crm cluster remove</command></title>
+    <para>
+      You can remove nodes from the cluster with the <command>crm cluster remove</command>
+      bootstrap script.
+    </para>
+    <para>
+      If you run <command>crm cluster remove</command> with no additional parameters, you are
+      prompted for the IP address or host name of the node to remove. Alternatively, you can
+      specify the node when you run the command:
+    </para>
+<screen>&prompt.root;<command>crm cluster remove <replaceable>NODE</replaceable></command></screen>
+    <para>
+       On the specified node, this stops all cluster services and removes the local cluster
+       configuration files. On the rest of the cluster nodes, the specified node is removed
+       from the cluster configuration.
+    </para>
+    <para>
+      In most cases, you must run <command>crm cluster remove</command> from a different node,
+      <emphasis>not</emphasis> from the node you want to remove. However, to remove the last node
+      and delete the cluster, you can use <option>--force</option> (or <option>-F</option>):
+    </para>
+<screen>&prompt.root;<command>crm cluster remove --force <replaceable>LASTNODE</replaceable></command></screen>
+    <para>
+      For more information, run <command>crm cluster help remove</command>.
+    </para>
+  </sect1>
 </chapter>