Fix few typos and minor wordsmithing in tableam comments.

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
index 7edfcf3ef9cd3c4ca42d077ec941d5474ba2bcbc..c2b0481e7e541bfb655e0803889f4cd66b9256e7 100644 (file)
--- 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,