diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
new file mode 100644
index 43bcb2a..a42541f
*** a/doc/src/sgml/high-availability.sgml
--- b/doc/src/sgml/high-availability.sgml
*************** protocol to make nodes agree on a serial
*** 237,243 ****
     <listitem>
  
      <para>
!      For servers that are not regularly connected, like laptops or
       remote servers, keeping data consistent among servers is a
       challenge.  Using asynchronous multimaster replication, each
       server works independently, and periodically communicates with
--- 237,244 ----
     <listitem>
  
      <para>
!      For servers that are not regularly connected or have slow
!      communication links, like laptops or
       remote servers, keeping data consistent among servers is a
       challenge.  Using asynchronous multimaster replication, each
       server works independently, and periodically communicates with
*************** protocol to make nodes agree on a serial
*** 256,264 ****
       In synchronous multimaster replication, each server can accept
       write requests, and modified data is transmitted from the
       original server to every other server before each transaction
!      commits.  Heavy write activity can cause excessive locking,
!      leading to poor performance.  In fact, write performance is
!      often worse than that of a single server.  Read requests can
       be sent to any server.  Some implementations use shared disk
       to reduce the communication overhead.  Synchronous multimaster
       replication is best for mostly read workloads, though its big
--- 257,264 ----
       In synchronous multimaster replication, each server can accept
       write requests, and modified data is transmitted from the
       original server to every other server before each transaction
!      commits.  Heavy write activity can cause excessive locking and
!      commit delays, leading to poor performance.  Read requests can
       be sent to any server.  Some implementations use shared disk
       to reduce the communication overhead.  Synchronous multimaster
       replication is best for mostly read workloads, though its big