Fix some typos and grammar issues from commit 87985cc92522
authorAlexander Korotkov <akorotkov@postgresql.org>
Wed, 27 Mar 2024 09:46:12 +0000 (11:46 +0200)
committerAlexander Korotkov <akorotkov@postgresql.org>
Wed, 27 Mar 2024 09:47:41 +0000 (11:47 +0200)
Reported-by: Alexander Lakhin
src/backend/access/heap/heapam.c
src/backend/commands/trigger.c

index 9a8c8e334875daa71678f9c534eb71040a8f6205..2f6527df0dc2d9c2b23320def2e8e8aaf81e7f45 100644 (file)
@@ -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 &&
index 3309b4ebd2da6cae879e4c8bab27a139836e9b5a..84494c4b81f21a7b71c25fdd6df6aa976654d819 100644 (file)
@@ -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);