postgres
diff --git a/‎src/backend/access/heap/heapam.c
Copy file name to clipboardExpand all lines: src/backend/access/heap/heapam.c
+1-1Lines changed: 1 addition & 1 deletion b/‎src/backend/access/heap/heapam.c
Copy file name to clipboardExpand all lines: src/backend/access/heap/heapam.c
+1-1Lines changed: 1 addition & 1 deletion
diff --git a/‎src/backend/commands/trigger.c
Copy file name to clipboardExpand all lines: src/backend/commands/trigger.c
+2-2Lines changed: 2 additions & 2 deletions b/‎src/backend/commands/trigger.c
Copy file name to clipboardExpand all lines: src/backend/commands/trigger.c
+2-2Lines changed: 2 additions & 2 deletions
@@ -3412,7 +3412,7 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,
 
 		/*
 		 * 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 &&
 
@@ -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);