From 818861eb578663a0d4d8d7dc4e18c96a148b3c75 Mon Sep 17 00:00:00 2001 From: Alexander Korotkov Date: Wed, 27 Mar 2024 11:46:12 +0200 Subject: [PATCH] Fix some typos and grammar issues from commit 87985cc92522 Reported-by: Alexander Lakhin --- src/backend/access/heap/heapam.c | 2 +- src/backend/commands/trigger.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c index 9a8c8e3348..2f6527df0d 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -3412,7 +3412,7 @@ l2: /* * If we're asked to lock the updated tuple, we just fetch the - * existing tuple. That let's the caller save some resouces on + * existing tuple. That lets the caller save some resources on * placing the lock. */ if (result == TM_Updated && diff --git a/src/backend/commands/trigger.c b/src/backend/commands/trigger.c index 3309b4ebd2..84494c4b81 100644 --- a/src/backend/commands/trigger.c +++ b/src/backend/commands/trigger.c @@ -2784,8 +2784,8 @@ ExecARDeleteTriggers(EState *estate, (transition_capture && transition_capture->tcs_delete_old_table)) { /* - * Put the FDW old tuple to the slot. Otherwise, caller is expected - * to have old tuple alredy fetched to the slot. + * Put the FDW old tuple to the slot. Otherwise, the caller is + * expected to have an old tuple already fetched to the slot. */ if (fdw_trigtuple != NULL) ExecForceStoreHeapTuple(fdw_trigtuple, slot, false);