summaryrefslogtreecommitdiff
path: root/doc/src/sgml/amcheck.sgml
diff options
context:
space:
mode:
authorAndres Freund2020-06-15 17:12:58 +0000
committerAndres Freund2020-07-08 20:03:32 +0000
commit9e101cf60612f4be4f855d7393531900c2986a55 (patch)
tree098e2f7d753441658fe86446750126bbb5c4a52e /doc/src/sgml/amcheck.sgml
parente07633646a22734e85d7fc58a66855f747128e6b (diff)
docs: replace 'master' with 'primary' where appropriate.
Also changed "in the primary" to "on the primary", and added a few "the" before "primary". Author: Andres Freund Reviewed-By: David Steele Discussion: https://postgr.es/m/[email protected]
Diffstat (limited to 'doc/src/sgml/amcheck.sgml')
-rw-r--r--doc/src/sgml/amcheck.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/amcheck.sgml b/doc/src/sgml/amcheck.sgml
index 75518a7820a..a9df2c1a9d2 100644
--- a/doc/src/sgml/amcheck.sgml
+++ b/doc/src/sgml/amcheck.sgml
@@ -253,7 +253,7 @@ SET client_min_messages = DEBUG1;
implies that operating system collation rules must never change.
Though rare, updates to operating system collation rules can
cause these issues. More commonly, an inconsistency in the
- collation order between a master server and a standby server is
+ collation order between a primary server and a standby server is
implicated, possibly because the <emphasis>major</emphasis> operating
system version in use is inconsistent. Such inconsistencies will
generally only arise on standby servers, and so can generally