DOC: min_recovery_lag fix, added arbiter port to the example in multimaster setup

Author: Liudmila Mantrova

doc/src/sgml/multimaster.sgml

@@ -305,7 +305,7 @@
           When the node gets synchronized up to the minimum recovery
           lag, all the cluster nodes get locked for write transactions to allow the
           recovery process to finish. By default, the minimum recovery
-          lag is 10MB. You can change this value in the
+          lag is 10KB. You can change this value in the
           <varname>multimaster.min_recovery_lag</varname> variable.
         </para>
       </listitem>
@@ -469,6 +469,7 @@ multimaster.conn_strings = 'dbname=mydb user=myuser host=node1 port=5432 arbiter
                            # comma-separated list 
                            # of connection strings 
                            # to neighbor nodes
+multimaster.arbiter_port = 5433
 </programlisting>
 <para>The <literal>multimaster.max_nodes</literal> variable defines the maximum cluster size. If you plan to add new nodes to your cluster, the <literal>multimaster.max_nodes</literal> value should exceed the initial number of nodes. In this case, you can add new nodes without restarting <productname>&productname;</productname> until the specified number of nodes is reached.
 </para>
@@ -604,7 +605,7 @@ SELECT mtm.get_cluster_state();
           <para>
             <varname>multimaster.min_recovery_lag</varname> &mdash; sets the
             minimal WAL lag between the node to be restored and the current cluster state. 
-            By default, <varname>multimaster.min_recovery_lag</varname> is set to 10MB.
+            By default, <varname>multimaster.min_recovery_lag</varname> is set to 10KB.
             When the disconnected node is fast-forwarded up to the
             <varname>multimaster.min_recovery_lag</varname> threshold,
             <filename>multimaster</filename> stops all new commits to the