@@ -927,7 +927,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
927927
928928 <para>
929929 All parameters have useful default values, so we can enable
930- synchronous replication easily just by setting this on the primary
930+ synchronous replication easily just by setting this on the primary:
931931
932932<programlisting>
933933synchronous_replication = on
@@ -938,7 +938,7 @@ synchronous_replication = on
938938 even if that takes a very long time.
939939 <varname>synchronous_replication</> can be set by individual
940940 users, so can be configured in the configuration file, for particular
941- users or databases, or dynamically by applications programs .
941+ users or databases, or dynamically by applications.
942942 </para>
943943
944944 <para>
@@ -1008,9 +1008,6 @@ synchronous_replication = on
10081008 <para>
10091009 You should consider that the network bandwidth must be higher than
10101010 the rate of generation of WAL data.
1011- 10% of changes are important customer details, while
1012- 90% of changes are less important data that the business can more
1013- easily survive if it is lost, such as chat messages between users.
10141011 </para>
10151012
10161013 </sect3>
@@ -1019,7 +1016,7 @@ synchronous_replication = on
10191016 <title>Planning for High Availability</title>
10201017
10211018 <para>
1022- Commits made when synchronous_replication is set will wait until at
1019+ Commits made when synchronous_replication is set will wait until
10231020 the sync standby responds. The response may never occur if the last,
10241021 or only, standby should crash.
10251022 </para>