From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 9 Nov 2023 22:51:19 +0000 (-0500)
Subject: doc: fix wording describing the checkpoint_flush_after GUC
X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=5ba1ac99a8d8623604d3152be8fd9a201ba5240b;p=users%2Frhaas%2Fpostgres.git

doc: fix wording describing the checkpoint_flush_after GUC

Reported-by: Evan Macbeth

Discussion: https://postgr.es/m/155208475619.1380.12815553062985622271@wrigleys.postgresql.org

Backpatch-through: master
---

diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 4aad0e1a07..184404c6c5 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -602,7 +602,7 @@
 
   <para>
    On Linux and POSIX platforms <xref linkend="guc-checkpoint-flush-after"/>
-   allows to force the OS that pages written by the checkpoint should be
+   allows you to force OS pages written by the checkpoint to be
    flushed to disk after a configurable number of bytes.  Otherwise, these
    pages may be kept in the OS's page cache, inducing a stall when
    <literal>fsync</literal> is issued at the end of a checkpoint.  This setting will