@@ -36,7 +36,7 @@ Disconnect.
3636
3737This API should be considered internal at the moment, but we could open it
3838up for 3rd party replacements of libpqwalreceiver in the future, allowing
39- pluggable methods forreceiveing WAL.
39+ pluggable methods forreceiving WAL.
4040
4141Walreceiver IPC
4242---------------
@@ -55,7 +55,7 @@ it to disk (in pg_xlog), it updates WalRcvData->receivedUpto and signals
5555the startup process to know how far WAL replay can advance.
5656
5757Walreceiver sends information about replication progress to the master server
58- whenevereither it writes or flushes new WAL, or the specified interval elapses.
58+ wheneverit either writes or flushes new WAL, or the specified interval elapses.
5959This is used for reporting purpose.
6060
6161Walsender IPC
@@ -83,7 +83,7 @@ backends.
8383
8484Note that no big harm is done if postmaster thinks that a walsender is a
8585regular backend; it will just terminate the walsender earlier in the shutdown
86- phase. Awalsenders will look like a regularbackends until it's done with the
86+ phase. Awalsender will look like a regularbackend until it's done with the
8787initialization and has marked itself in PMSignal array, and at process
8888termination, after unmarking the PMSignal slot.
8989