From 4760c11937a749d8b97a523616cae086c261a515 Mon Sep 17 00:00:00 2001 From: Josh Soref Date: Wed, 16 Dec 2020 19:14:28 -0500 Subject: [PATCH] doc: various spelling fixes Via GitHub #687. --- HISTORY | 2 +- TODO.md | 2 +- doc/appendix-faq.xml | 10 +++++----- doc/appendix-packages.xml | 4 ++-- doc/appendix-release-notes.xml | 2 +- doc/appendix-support.xml | 2 +- doc/cloning-standbys.xml | 4 ++-- doc/quickstart.xml | 2 +- doc/repmgr-daemon-start.xml | 2 +- doc/repmgr-daemon-stop.xml | 2 +- doc/repmgr-node-rejoin.xml | 2 +- doc/repmgr-standby-promote.xml | 4 ++-- doc/repmgrd-automatic-failover.xml | 2 +- doc/repmgrd-configuration.xml | 2 +- doc/upgrading-repmgr.xml | 2 +- repmgr.conf.sample | 2 +- 16 files changed, 23 insertions(+), 23 deletions(-) diff --git a/HISTORY b/HISTORY index 0e35c780..d95af708 100644 --- a/HISTORY +++ b/HISTORY @@ -43,7 +43,7 @@ repmgr: ensure postgresql.auto.conf is created with correct permissions (Ian) repmgr: minimize requirement to check upstream data directory location during "standby clone" (Ian) - repmgr: warn about missing pg_rewind prerequisites when excuting + repmgr: warn about missing pg_rewind prerequisites when executing "standby clone" (Ian) repmgr: add --upstream option to "node check" repmgr: report error code on follow/rejoin failure due to non-available diff --git a/TODO.md b/TODO.md index acbfd571..fd1ff7c3 100644 --- a/TODO.md +++ b/TODO.md @@ -1,7 +1,7 @@ TODO ==== -This file contains a list of improvements which are desireable and/or have +This file contains a list of improvements which are desirable and/or have been requested, and which we aim to address/implement when time and resources permit. diff --git a/doc/appendix-faq.xml b/doc/appendix-faq.xml index 49b96127..a13f8bdb 100644 --- a/doc/appendix-faq.xml +++ b/doc/appendix-faq.xml @@ -170,7 +170,7 @@ If different "minor" &repmgr; versions (e.g. 4.1.1 and 4.1.6) are installed, &repmgr; will function, but we strongly recommend always running the same version - to ensure there are no unexpected suprises, e.g. a newer version behaving slightly + to ensure there are no unexpected surprises, e.g. a newer version behaving slightly differently to the older version. @@ -212,7 +212,7 @@ - + Are &repmgr; packages compatible with <literal>$third_party_vendor</literal>'s packages? &repmgr; packages provided by 2ndQuadrant are compatible with the community-provided PostgreSQL @@ -311,7 +311,7 @@ - + Do I need to include <literal>shared_preload_libraries = 'repmgr'</literal> in <filename>postgresql.conf</filename> if I'm not using &repmgrd;? @@ -459,7 +459,7 @@ promote_command or follow_command can be user-defined scripts, - so &repmgr; will not apply even if excuting &repmgr;. Always provide the full + so &repmgr; will not apply even if executing &repmgr;. Always provide the full path; see for more details. @@ -479,7 +479,7 @@ is out-of-date, which may lead to incorrect failover behaviour. - The onus is therefore on the adminstrator to manually set the cluster to a stable, healthy state before + The onus is therefore on the administrator to manually set the cluster to a stable, healthy state before starting &repmgrd;. diff --git a/doc/appendix-packages.xml b/doc/appendix-packages.xml index 5b8f2e33..87f207d2 100644 --- a/doc/appendix-packages.xml +++ b/doc/appendix-packages.xml @@ -398,7 +398,7 @@ packages - snaphots + snapshots @@ -439,7 +439,7 @@ curl https://dl.2ndquadrant.com/default/snapshot/get/9.6/rpm | sudo bash repmgr96-4.1.1-0.0git320.g5113ab0.1.el7.x86_64.rpm - containg the snapshot build number (here: 320) and the hash + containing the snapshot build number (here: 320) and the hash of the git commit it was built from (here: g5113ab0). diff --git a/doc/appendix-release-notes.xml b/doc/appendix-release-notes.xml index 308481a7..5705b10c 100644 --- a/doc/appendix-release-notes.xml +++ b/doc/appendix-release-notes.xml @@ -1199,7 +1199,7 @@ REPMGRD_OPTS="--daemonize=false" Possible values are ping (default; uses PQping() to - determine server availability), connection (attempst to make a new connection to + determine server availability), connection (attempts to make a new connection to the upstream node), and query (determines server availability by executing an SQL statement on the node via the existing connection). diff --git a/doc/appendix-support.xml b/doc/appendix-support.xml index 121684a2..2ae0029a 100644 --- a/doc/appendix-support.xml +++ b/doc/appendix-support.xml @@ -64,7 +64,7 @@ - repmpgr.conf files (suitably anonymized if necessary) + repmgr.conf files (suitably anonymized if necessary) diff --git a/doc/cloning-standbys.xml b/doc/cloning-standbys.xml index 53fc283c..eca50fee 100644 --- a/doc/cloning-standbys.xml +++ b/doc/cloning-standbys.xml @@ -319,7 +319,7 @@ description = "Main cluster" Cascading replication, introduced with PostgreSQL 9.2, enables a standby server to replicate from another standby server rather than directly from the primary, meaning replication changes "cascade" down through a hierarchy of servers. This - can be used to reduce load on the primary and minimize bandwith usage between + can be used to reduce load on the primary and minimize bandwidth usage between sites. For more details, see the PostgreSQL cascading replication documentation. @@ -391,7 +391,7 @@ description = "Main cluster" cluster, you may wish to clone a downstream standby whose upstream node does not yet exist. In this case you can clone from the primary (or another upstream node); provide the parameter --upstream-conninfo - to explictly set the upstream's primary_conninfo string + to explicitly set the upstream's primary_conninfo string in recovery.conf. diff --git a/doc/quickstart.xml b/doc/quickstart.xml index b3d7bf46..93a6cbf2 100644 --- a/doc/quickstart.xml +++ b/doc/quickstart.xml @@ -284,7 +284,7 @@ - For Debian-based distributions we recommend explictly setting + For Debian-based distributions we recommend explicitly setting to the directory where pg_ctl and other binaries not in the standard path are located. For PostgreSQL 9.6 this would be /usr/lib/postgresql/9.6/bin/. diff --git a/doc/repmgr-daemon-start.xml b/doc/repmgr-daemon-start.xml index 54c7d97f..46401380 100644 --- a/doc/repmgr-daemon-start.xml +++ b/doc/repmgr-daemon-start.xml @@ -25,7 +25,7 @@ By default, &repmgr; will wait for up to 15 seconds to confirm that &repmgrd; - started. This behaviour can be overridden by specifying a diffent value using the + started. This behaviour can be overridden by specifying a different value using the option, or disabled altogether with the option. diff --git a/doc/repmgr-daemon-stop.xml b/doc/repmgr-daemon-stop.xml index 61881cc0..46ed1f5e 100644 --- a/doc/repmgr-daemon-stop.xml +++ b/doc/repmgr-daemon-stop.xml @@ -26,7 +26,7 @@ By default, &repmgr; will wait for up to 15 seconds to confirm that &repmgrd; - stopped. This behaviour can be overridden by specifying a diffent value using the + stopped. This behaviour can be overridden by specifying a different value using the option, or disabled altogether with the option. diff --git a/doc/repmgr-node-rejoin.xml b/doc/repmgr-node-rejoin.xml index ba19f85a..1347eb00 100644 --- a/doc/repmgr-node-rejoin.xml +++ b/doc/repmgr-node-rejoin.xml @@ -457,7 +457,7 @@ and ensure the standby can be attached to it. If pg_rewind was actually executed, it will have copied in the .history file from the target primary server; this must be removed. repmgr node rejoin can then be used to attach the standby to the original - primary. Ensure any changes pending on the primary have propogated to the standby. Then shut down the primary + primary. Ensure any changes pending on the primary have propagated to the standby. Then shut down the primary server first, before shutting down the standby. It should then be possible to use repmgr node rejoin to attach the standby to the new primary. diff --git a/doc/repmgr-standby-promote.xml b/doc/repmgr-standby-promote.xml index 68024aa4..1a1ccd95 100644 --- a/doc/repmgr-standby-promote.xml +++ b/doc/repmgr-standby-promote.xml @@ -189,14 +189,14 @@ - If the promotion candidate has insufficient free walsenders to accomodate the standbys which will + If the promotion candidate has insufficient free walsenders to accommodate the standbys which will be attached to it, the standby will be promoted anyway. If replication slots are in use but the promotion candidate has insufficient free replication slots - to accomodate the standbys which will be attached to it, the standby will be promoted anyway. + to accommodate the standbys which will be attached to it, the standby will be promoted anyway. diff --git a/doc/repmgrd-automatic-failover.xml b/doc/repmgrd-automatic-failover.xml index d8308e8e..795afc61 100644 --- a/doc/repmgrd-automatic-failover.xml +++ b/doc/repmgrd-automatic-failover.xml @@ -586,7 +586,7 @@ INFO: node 3 received notification to rerun promotion candidate election Standby disconnections monitoring caveats - The follwing caveats should be considered if you are intending to use this functionality. + The following caveats should be considered if you are intending to use this functionality. diff --git a/doc/repmgrd-configuration.xml b/doc/repmgrd-configuration.xml index fae0847a..65adb1b3 100644 --- a/doc/repmgrd-configuration.xml +++ b/doc/repmgrd-configuration.xml @@ -969,7 +969,7 @@ repmgrd_service_stop_command='sudo systemctl repmgr12 stop' If none of the above apply, &repmgrd; will create a PID file - in the operating system's temporary directory (as setermined by the environment variable + in the operating system's temporary directory (as determined by the environment variable TMPDIR, or if that is not set, will use /tmp). diff --git a/doc/upgrading-repmgr.xml b/doc/upgrading-repmgr.xml index 63811ace..947a72a7 100644 --- a/doc/upgrading-repmgr.xml +++ b/doc/upgrading-repmgr.xml @@ -482,7 +482,7 @@ ALTER EXTENSION repmgr UPDATE If you don't care about any data from the existing &repmgr; installation, (e.g. the contents of the events and monitoring - tables), the follwing steps can be skipped; proceed to . + tables), the following steps can be skipped; proceed to . diff --git a/repmgr.conf.sample b/repmgr.conf.sample index 80bb8635..f8702834 100644 --- a/repmgr.conf.sample +++ b/repmgr.conf.sample @@ -323,7 +323,7 @@ ssh_options='-q -o ConnectTimeout=10' # Options to append to "ssh" # for the the local node to restart and become ready to accept connections after # executing "follow_command" (defaults to the value set in "standby_reconnect_timeout") -#monitoring_history=no # Whether to write monitoring data to the "montoring_history" table +#monitoring_history=no # Whether to write monitoring data to the "monitoring_history" table #monitor_interval_secs=2 # Interval (in seconds) at which to write monitoring data #degraded_monitoring_timeout=-1 # Interval (in seconds) after which repmgrd will terminate if the # server(s) being monitored are no longer available. -1 (default)