@@ -164,7 +164,7 @@ typedef struct TableAmRoutine
164164 * synchronized scans, or page mode may be used (although not every AM
165165 * will support those).
166166 *
167- * is_{bitmapscan, samplescan} specify whether the scan isinteded to
167+ * is_{bitmapscan, samplescan} specify whether the scan isintended to
168168 * support those types of scans.
169169 *
170170 * if temp_snap is true, the snapshot will need to be deallocated at
@@ -220,7 +220,7 @@ typedef struct TableAmRoutine
220220Size (* parallelscan_initialize ) (Relation rel ,ParallelTableScanDesc pscan );
221221
222222/*
223- *Reinitilize `pscan` for a new scan. `rel` will be the same relation as
223+ *Reinitialize `pscan` for a new scan. `rel` will be the same relation as
224224 * when `pscan` was initialized by parallelscan_initialize.
225225 */
226226void (* parallelscan_reinitialize ) (Relation rel ,ParallelTableScanDesc pscan );
@@ -913,7 +913,7 @@ table_delete(Relation rel, ItemPointer tid, CommandId cid,
913913 * Input parameters:
914914 *relation - table to be modified (caller must hold suitable lock)
915915 *otid - TID of old tuple to be replaced
916- *newtup - newly constructed tuple data to store
916+ *slot - newly constructed tuple data to store
917917 *cid - update command ID (used for visibility test, and stored into
918918 *cmax/cmin if successful)
919919 *crosscheck - if not InvalidSnapshot, also check old tuple against this
@@ -929,8 +929,8 @@ table_delete(Relation rel, ItemPointer tid, CommandId cid,
929929 * TM_SelfModified, TM_Updated, or TM_BeingModified
930930 * (the last only possible if wait == false).
931931 *
932- * On success, theheader fields of *newtup are updated to match the new
933- * stored tuple; in particular,newtup->t_self is set to the TID where the
932+ * On success, theslot's tts_tid and tts_tableOid are updated to match the new
933+ * stored tuple; in particular,slot->tts_tid is set to the TID where the
934934 * new tuple was inserted, and its HEAP_ONLY_TUPLE flag is set iff a HOT
935935 * update was done. However, any TOAST changes in the new tuple's
936936 * data are not reflected into *newtup.
@@ -965,7 +965,7 @@ table_update(Relation rel, ItemPointer otid, TupleTableSlot *slot,
965965 *flags:
966966 *If TUPLE_LOCK_FLAG_LOCK_UPDATE_IN_PROGRESS, follow the update chain to
967967 *also lock descendant tuples if lock modes don't conflict.
968- *If TUPLE_LOCK_FLAG_FIND_LAST_VERSION, update chain and locklastest
968+ *If TUPLE_LOCK_FLAG_FIND_LAST_VERSION, update chain and locklatest
969969 *version.
970970 *
971971 * Output parameters: