diff --git a/xml/ha_bootstrap_install.xml b/xml/ha_bootstrap_install.xml
index f409e7da..bb646ca9 100644
--- a/xml/ha_bootstrap_install.xml
+++ b/xml/ha_bootstrap_install.xml
@@ -368,6 +368,9 @@
     starts the cluster services to bring the cluster online and enables &hawk2;.
     The URL to use for &hawk2; is displayed on the screen.
     </para>
+    <para>
+      To log in to &hawk2;, see <xref linkend="sec-conf-hawk2-login"/>.
+    </para>
     <important>
       <title>Secure password for <systemitem class="username">hacluster</systemitem></title>
       <para>
@@ -380,69 +383,6 @@
     </important>
   </sect1>
 
-  <sect1 xml:id="sec-ha-bootstrap-install-hawk2-login">
-  <!-- Duplicated from xml/article_installation.xml -->
-    <title>Logging in to the &hawk2; web interface</title>
-    <para>
-      You now have a running one-node cluster. To view its status, proceed as follows:
-    </para>
-    <procedure xml:id="pro-ha-bootstrap-install-hawk2-login">
-      <title>Logging in to the &hawk2; Web interface</title>
-      <step>
-        <para>
-          On any machine, start a Web browser and make sure that JavaScript and cookies are enabled.
-        </para>
-      </step>
-      <step>
-        <para>
-          As URL, enter the virtual IP address that you configured with the bootstrap script:
-        </para>
-<screen>https://<replaceable>VIRTUAL_IP</replaceable>:7630/</screen>
-        <note>
-          <title>Certificate warning</title>
-          <para>
-            If a certificate warning appears when you try to access the URL for the first time,
-            a self-signed certificate is in use. Self-signed certificates are not considered
-            trustworthy by default.
-          </para>
-          <para>
-            Ask your cluster operator for the certificate details to verify the certificate.
-          </para>
-          <para>
-            To proceed anyway, you can add an exception in the browser to bypass the warning.
-          </para>
-        </note>
-      </step>
-      <step>
-        <para>
-          On the &hawk2; login screen, enter the <guimenu>Username</guimenu> of the user that was
-          created by the bootstrap script (<systemitem class="username">hacluster</systemitem>)
-          and the secure <guimenu>Password</guimenu> that you changed from the bootstrap script's
-          default password.
-        </para>
-        <important role="compact">
-          <para>
-            If you have not already changed the default password to a secure one, do so now.
-          </para>
-        </important>
-      </step>
-      <step>
-        <para>
-          Click <guimenu>Log In</guimenu>. The &hawk2; Web interface shows the
-          <guimenu>Status</guimenu> screen by default:
-        </para>
-        <figure xml:id="fig-ha-bootstrap-install-one-node-status">
-          <title>Status of the one-node cluster in &hawk2;</title>
-          <mediaobject>
-            <imageobject>
-            <imagedata width="80%" fileref="installquick-one-nodecluster.png"/>
-            </imageobject>
-          </mediaobject>
-        </figure>
-      </step>
-    </procedure>
-  </sect1>
-
   <sect1 xml:id="sec-ha-install-node-join-bootstrap">
   <!-- Duplicated from xml/article_installation.xml -->
     <title>Adding nodes with <command>crm cluster join</command></title>
@@ -520,4 +460,11 @@ crm cluster join --use-ssh-agent -c <replaceable>USER</replaceable>@<replaceable
       <menuchoice><guimenu>Status</guimenu><guimenu>Nodes</guimenu></menuchoice>.
     </para>
   </sect1>
+
+  <sect1 xml:id="sec-ha-install-cluster-init-stages">
+    <title>Modifying the cluster with <command>crm cluster init</command> stages</title>
+    <para>
+      TO DO
+    </para>
+  </sect1>
 </chapter>