From 42fa4b660143b66bea1fb90793ec90054e170c93 Mon Sep 17 00:00:00 2001
From: Andrew Dunstan
Date: Tue, 9 Apr 2024 15:30:48 -0400
Subject: Assorted minor cleanups in the test_json_parser module

Per gripes from Michael Paquier

Discussion: https://postgr.es/m/ZhTQ6_w1vwOhqTQI@paquier.xyz

Along the way, also clean up a handful of typos in 3311ea86ed and
ea7b4e9a2a, found by Alexander Lakhin, and a couple of stylistic
snafus noted by Daniel Westermann and Daniel Gustafsson.
---
 src/backend/backup/basebackup_incremental.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'src/backend/backup/basebackup_incremental.c')

diff --git a/src/backend/backup/basebackup_incremental.c b/src/backend/backup/basebackup_incremental.c
index 330a2294011..4ad9d7cad00 100644
--- a/src/backend/backup/basebackup_incremental.c
+++ b/src/backend/backup/basebackup_incremental.c
@@ -34,7 +34,7 @@
 #define	BLOCKS_PER_READ			512
 
 /*
- * we expect the find the last lines of the manifest, including the checksum,
+ * We expect to find the last lines of the manifest, including the checksum,
  * in the last MIN_CHUNK bytes of the manifest. We trigger an incremental
  * parse step if we are about to overflow MAX_CHUNK bytes.
  */
@@ -88,8 +88,8 @@ struct IncrementalBackupInfo
 	 * Files extracted from the backup manifest.
 	 *
 	 * We don't really need this information, because we use WAL summaries to
-	 * figure what's changed. It would be unsafe to just rely on the list of
-	 * files that existed before, because it's possible for a file to be
+	 * figure out what's changed. It would be unsafe to just rely on the list
+	 * of files that existed before, because it's possible for a file to be
 	 * removed and a new one created with the same name and different
 	 * contents. In such cases, the whole file must still be sent. We can tell
 	 * from the WAL summaries whether that happened, but not from the file
-- 
cgit v1.2.3