From 8606e47e1120b891e9a539881c0aa2bb9b03ba62 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 24 Aug 2012 22:35:53 -0400 Subject: [PATCH] Normalize some British spellings --- doc/src/sgml/high-availability.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index f3816085b6..62f72b40ae 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -881,7 +881,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass' The cascading replication feature allows a standby server to accept replication connections and stream WAL records to other standbys, acting as a relay. This can be used to reduce the number of direct connections to the master - and also to minimise inter-site bandwidth overheads. + and also to minimize inter-site bandwidth overheads. @@ -1041,7 +1041,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass' Synchronous replication usually requires carefully planned and placed standby servers to ensure applications perform acceptably. Waiting - doesn't utilise system resources, but transaction locks continue to be + doesn't utilize system resources, but transaction locks continue to be held until the transfer is confirmed. As a result, incautious use of synchronous replication will reduce performance for database applications because of increased response times and higher contention. -- 2.40.0