diff --git a/doc/manual-conflicts.sgml b/doc/manual-conflicts.sgml
index 16c808f238..0bdc1d8278 100644
--- a/doc/manual-conflicts.sgml
+++ b/doc/manual-conflicts.sgml
@@ -68,7 +68,12 @@
     The most common conflicts are row conflicts where two operations affect a
     row with the same key in ways they could not do on a single node. &bdr; can
     detect most of those and apply last-update-wins conflict handling or invoke
-    a user-defined conflict handler.
+    a user-defined conflict handler. For the time based conflict handlers to
+    function correctly all nodes in the cluster must share the same time source.
+    If you have a conflict when the time on two nodes is out of sync the conflict
+    may never be able to resolved because the last update time will never match
+    even after the handler has run. This will manifest itself as row updates only
+    syncing in one direction.
    </para>
 
    <para>
diff --git a/doc/manual-node-management.sgml b/doc/manual-node-management.sgml
index 83d1b39351..b19cb66086 100644
--- a/doc/manual-node-management.sgml
+++ b/doc/manual-node-management.sgml
@@ -104,6 +104,12 @@
    <para>
     See also: <xref linkend="functions-node-mgmt">, <xref linkend="command-bdr-init-copy">.
    </para>
+
+   <para>
+    To view the status of the cluster then interrogate this table:- <xref linkend="bdr.bdr_nodes">.
+   </para>
+
+
   </sect2>
 
   <sect2 id="node-management-joining-bdr" xreflabel="Joining or creating a BDR node">