Fix few typos and minor word smithing in tableam comments.

Amit Kapila · Amit Kapila · commit e33a1435be55 · 2019-07-10T07:59:51.000+05:30
Reported-by: Ashwin Agrawal Author: Ashwin Agrawal Reviewed-by: Amit Kapila Backpatch-through: 12, where it was introduced Discussion: https://postgr.es/m/CALfoeisgdZhYDrJOukaBzvXfJOK2FQ0szVMK7dzmcy6w93iDUA@mail.gmail.com
diff --git a/src/include/access/tableam.h b/src/include/access/tableam.h
@@ -434,8 +434,8 @@ typedef struct TableAmRoutine
 	 *
 	 * Note that only the subset of the relcache filled by
 	 * RelationBuildLocalRelation() can be relied upon and that the relation's
-	 * catalog entries either will either not yet exist (new relation), or
-	 * will still reference the old relfilenode.
+	 * catalog entries will either not yet exist (new relation), or will still
+	 * reference the old relfilenode.
 	 *
 	 * As output *freezeXid, *minmulti must be set to the values appropriate
 	 * for pg_class.{relfrozenxid, relminmxid}. For AMs that don't need those
@@ -591,7 +591,7 @@ typedef struct TableAmRoutine
 	 * See table_relation_estimate_size().
 	 *
 	 * While block oriented, it shouldn't be too hard for an AM that doesn't
-	 * doesn't internally use blocks to convert into a usable representation.
+	 * internally use blocks to convert into a usable representation.
 	 *
 	 * This differs from the relation_size callback by returning size
 	 * estimates (both relation size and tuple count) for planning purposes,
@@ -967,7 +967,7 @@ table_index_fetch_end(struct IndexFetchTableData *scan)
  *
  * *all_dead, if all_dead is not NULL, will be set to true by
  * table_index_fetch_tuple() iff it is guaranteed that no backend needs to see
- * that tuple. Index AMs can use that do avoid returning that tid in future
+ * that tuple. Index AMs can use that to avoid returning that tid in future
  * searches.
  *
  * The difference between this function and table_fetch_row_version is that
@@ -1014,8 +1014,8 @@ extern bool table_index_fetch_tuple_check(Relation rel,
  * true, false otherwise.
  *
  * See table_index_fetch_tuple's comment about what the difference between
- * these functions is. This function is the correct to use outside of
- * index entry->table tuple lookups.
+ * these functions is. It is correct to use this function outside of index
+ * entry->table tuple lookups.
  */
 static inline bool
 table_tuple_fetch_row_version(Relation rel,

Original file line number	Diff line number	Diff line change
`@@ -434,8 +434,8 @@ typedef struct TableAmRoutine`
`434`	`434`	`*`
`435`	`435`	`* Note that only the subset of the relcache filled by`
`436`	`436`	`* RelationBuildLocalRelation() can be relied upon and that the relation's`
`437`		`- * catalog entries either will either not yet exist (new relation), or`
`438`		`- * will still reference the old relfilenode.`
	`437`	`+ * catalog entries will either not yet exist (new relation), or will still`
	`438`	`+ * reference the old relfilenode.`
`439`	`439`	`*`
`440`	`440`	`* As output freezeXid, minmulti must be set to the values appropriate`
`441`	`441`	`* for pg_class.{relfrozenxid, relminmxid}. For AMs that don't need those`
`@@ -591,7 +591,7 @@ typedef struct TableAmRoutine`
`591`	`591`	`* See table_relation_estimate_size().`
`592`	`592`	`*`
`593`	`593`	`* While block oriented, it shouldn't be too hard for an AM that doesn't`
`594`		`- * doesn't internally use blocks to convert into a usable representation.`
	`594`	`+ * internally use blocks to convert into a usable representation.`
`595`	`595`	`*`
`596`	`596`	`* This differs from the relation_size callback by returning size`
`597`	`597`	`* estimates (both relation size and tuple count) for planning purposes,`
`@@ -967,7 +967,7 @@ table_index_fetch_end(struct IndexFetchTableData *scan)`
`967`	`967`	`*`
`968`	`968`	`* *all_dead, if all_dead is not NULL, will be set to true by`
`969`	`969`	`* table_index_fetch_tuple() iff it is guaranteed that no backend needs to see`
`970`		`- * that tuple. Index AMs can use that do avoid returning that tid in future`
	`970`	`+ * that tuple. Index AMs can use that to avoid returning that tid in future`
`971`	`971`	`* searches.`
`972`	`972`	`*`
`973`	`973`	`* The difference between this function and table_fetch_row_version is that`
`@@ -1014,8 +1014,8 @@ extern bool table_index_fetch_tuple_check(Relation rel,`
`1014`	`1014`	`* true, false otherwise.`
`1015`	`1015`	`*`
`1016`	`1016`	`* See table_index_fetch_tuple's comment about what the difference between`
`1017`		`- * these functions is. This function is the correct to use outside of`
`1018`		`- * index entry->table tuple lookups.`
	`1017`	`+ * these functions is. It is correct to use this function outside of index`
	`1018`	`+ * entry->table tuple lookups.`
`1019`	`1019`	`*/`
`1020`	`1020`	`static inline bool`
`1021`	`1021`	`table_tuple_fetch_row_version(Relation rel,`