Fix typos in comments.

Oversight in commit fd5a1a0c3e.

Author: Tender Wang <tndrwang@gmail.com>
Discussion: https://postgr.es/m/CAHewXNmTT3M_w4NngG=6G3mdT3iJ6DdncTqV9YnGXBPHW8XYtA@mail.gmail.com

src/backend/executor/execReplication.c

@@ -582,7 +582,7 @@ RelationFindDeletedTupleInfoSeq(Relation rel, TupleTableSlot *searchslot,
 	 * IsIndexUsableForFindingDeletedTuple), a full table scan becomes
 	 * necessary. In such cases, comparing the entire tuple is not required,
 	 * since the remote tuple might not include all column values. Instead,
-	 * the indexed columns alone are suffcient to identify the target tuple
+	 * the indexed columns alone are sufficient to identify the target tuple
 	 * (see logicalrep_rel_mark_updatable).
 	 */
 	indexbitmap = RelationGetIndexAttrBitmap(rel,

src/backend/replication/logical/worker.c

@@ -2923,7 +2923,7 @@ apply_handle_update_internal(ApplyExecutionData *edata,
 
 		/*
 		 * Detecting whether the tuple was recently deleted or never existed
-		 * is crucial to avoid misleading the user during confict handling.
+		 * is crucial to avoid misleading the user during conflict handling.
 		 */
 		if (FindDeletedTupleInLocalRel(localrel, localindexoid, remoteslot,
 									   &conflicttuple.xmin,
@@ -3392,7 +3392,7 @@ apply_handle_tuple_routing(ApplyExecutionData *edata,
 					/*
 					 * Detecting whether the tuple was recently deleted or
 					 * never existed is crucial to avoid misleading the user
-					 * during confict handling.
+					 * during conflict handling.
 					 */
 					if (FindDeletedTupleInLocalRel(partrel,
 												   part_entry->localindexoid,