From: Alexander Korotkov <akorotkov@postgresql.org>
Date: Sun, 4 Aug 2024 17:26:48 +0000 (+0300)
Subject: pg_wal_replay_wait(): Fix typo in the doc
X-Git-Tag: REL_18_BETA1~2212
X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=8036d73ae3d4014a9dde21b0746dc1ac139d4dc1;p=postgresql.git

pg_wal_replay_wait(): Fix typo in the doc

Reported-by: Kevin Hale Boyes
Discussion: https://postgr.es/m/CADAecHWKpaPuPGXAMOH%3DwmhTpydHWGPOk9KWX97UYhp5GdqCWw%40mail.gmail.com
---

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 3cf896b22fa..0f7154b76ab 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -28990,7 +28990,7 @@ pg_current_wal_insert_lsn
 
    Then an application could run <function>pg_wal_replay_wait</function>
    with the <acronym>lsn</acronym> obtained from primary.  After that the
-   changes made of primary should be guaranteed to be visible on replica.
+   changes made on primary should be guaranteed to be visible on replica.
 
    <programlisting>
 postgres=# CALL pg_wal_replay_wait('0/306EE20');