Lots of doc corrections.

Josh Kupershmidt

contrib/pg_upgrade/info.c

@@ -234,7 +234,7 @@ get_db_infos(ClusterInfo *cluster)
 /*
  * get_rel_infos()
  *
- * gets the relinfos for all the user tables of the database refered
+ * gets the relinfos for all the user tables of the database referred
  * by "db".
  *
  * NOTE: we assume that relations/entities with oids greater than

contrib/pg_upgrade/pg_upgrade.c

@@ -15,7 +15,7 @@
  *	oids are the same between old and new clusters.  This is important
  *	because toast oids are stored as toast pointers in user tables.
  *
- *	FYI, while pg_class.oid and pg_class.relfilenode are intially the same
+ *	FYI, while pg_class.oid and pg_class.relfilenode are initially the same
  *	in a cluster, but they can diverge due to CLUSTER, REINDEX, or VACUUM
  *	FULL.  The new cluster will have matching pg_class.oid and
  *	pg_class.relfilenode values and be based on the old oid value.	This can

contrib/pg_upgrade/version_old_8_3.c

@@ -396,7 +396,7 @@ old_8_3_rebuild_tsvector_tables(ClusterInfo *cluster, bool check_mode)
 
 		PQclear(res);
 
-		/* XXX Mark tables as not accessable somehow */
+		/* XXX Mark tables as not accessible somehow */
 
 		PQfinish(conn);
 	}
@@ -666,7 +666,7 @@ old_8_3_invalidate_bpchar_pattern_ops_indexes(ClusterInfo *cluster,
  *	we don't transfer sequence files but instead use the CREATE SEQUENCE
  *	command from the schema dump, and use setval() to restore the sequence
  *	value and 'is_called' from the old database.  This is safe to run
- *	by pg_upgrade because sequence files are not transfered from the old
+ *	by pg_upgrade because sequence files are not transferred from the old
  *	server, even in link mode.
  */
 char *