Copyedit comments and documentation.

Author: nmisch

config/c-compiler.m4

@@ -335,7 +335,7 @@ if test x"$Ac_cachevar" = x"yes"; then
   $1="${$1} $2"
 fi
 undefine([Ac_cachevar])dnl
-])# PGAC_PROG_CC_CFLAGS_OPT
+])# PGAC_PROG_CC_VAR_OPT
 
 
 

contrib/pgstattuple/pgstatapprox.c

@@ -1,6 +1,6 @@
 /*-------------------------------------------------------------------------
  *
- * pgstatapproc.c
+ * pgstatapprox.c
  *		  Bloat estimation functions
  *
  * Copyright (c) 2014-2016, PostgreSQL Global Development Group

doc/src/sgml/install-windows.sgml

@@ -457,7 +457,7 @@ $ENV{CONFIG}="Debug";
   <para>
    Running the regression tests on client programs, with
    <command>vcregress bincheck</>, or on recovery tests, with
-   <command>vcregress recoverycheck</> requires an additional Perl module
+   <command>vcregress recoverycheck</>, requires an additional Perl module
    to be installed:
    <variablelist>
     <varlistentry>

doc/src/sgml/release-9.3.sgml

@@ -9689,7 +9689,7 @@ ALTER EXTENSION hstore UPDATE;
 
       <listitem>
        <para>
-        Remove <filename>src/tool/backend</>, now that the content is on
+        Remove <filename>src/tools/backend</>, now that the content is on
         the <productname>PostgreSQL</> wiki (Bruce Momjian)
        </para>
       </listitem>

doc/src/sgml/xml2.sgml

@@ -324,7 +324,7 @@ AS t(article_id integer, author text, page_count integer, title text);
   </para>
 
   <para>
-   The calling <command>SELECT</> statement doesn't necessarily have be
+   The calling <command>SELECT</> statement doesn't necessarily have to be
    just <literal>SELECT *</> &mdash; it can reference the output
    columns by name or join them to other tables. The function produces a
    virtual table with which you can perform any operation you wish (e.g.

src/backend/executor/execParallel.c

@@ -71,7 +71,7 @@ typedef struct ExecParallelEstimateContext
 	int nnodes;
 } ExecParallelEstimateContext;
 
-/* Context object for ExecParallelEstimate. */
+/* Context object for ExecParallelInitializeDSM. */
 typedef struct ExecParallelInitializeDSMContext
 {
 	ParallelContext *pcxt;

src/backend/storage/buffer/README

@@ -89,12 +89,12 @@ then returns false, while LockBufferForCleanup() releases the exclusive lock
 (but not the caller's pin) and waits until signaled by another backend,
 whereupon it tries again.  The signal will occur when UnpinBuffer decrements
 the shared pin count to 1.  As indicated above, this operation might have to
-wait a good while before it acquires lock, but that shouldn't matter much for
-concurrent VACUUM.  The current implementation only supports a single waiter
-for pin-count-1 on any particular shared buffer.  This is enough for VACUUM's
-use, since we don't allow multiple VACUUMs concurrently on a single relation
-anyway.  Anyone wishing to obtain a cleanup lock outside of recovery or a
-VACUUM must use the conditional variant of the function.
+wait a good while before it acquires the lock, but that shouldn't matter much
+for concurrent VACUUM.  The current implementation only supports a single
+waiter for pin-count-1 on any particular shared buffer.  This is enough for
+VACUUM's use, since we don't allow multiple VACUUMs concurrently on a single
+relation anyway.  Anyone wishing to obtain a cleanup lock outside of recovery
+or a VACUUM must use the conditional variant of the function.
 
 
 Buffer Manager's Internal Locking

src/backend/storage/buffer/bufmgr.c

@@ -921,7 +921,7 @@ ReadBuffer_common(SMgrRelation smgr, char relpersistence, ForkNumber forkNum,
 	 *
 	 * Since no-one else can be looking at the page contents yet, there is no
 	 * difference between an exclusive lock and a cleanup-strength lock. (Note
-	 * that we cannot use LockBuffer() of LockBufferForCleanup() here, because
+	 * that we cannot use LockBuffer() or LockBufferForCleanup() here, because
 	 * they assert that the buffer is already valid.)
 	 */
 	if ((mode == RBM_ZERO_AND_LOCK || mode == RBM_ZERO_AND_CLEANUP_LOCK) &&
@@ -1882,7 +1882,7 @@ BufferSync(int flags)
 		 * and clears the flag right after we check, but that doesn't matter
 		 * since SyncOneBuffer will then do nothing.  However, there is a
 		 * further race condition: it's conceivable that between the time we
-		 * examine the bit here and the time SyncOneBuffer acquires lock,
+		 * examine the bit here and the time SyncOneBuffer acquires the lock,
 		 * someone else not only wrote the buffer but replaced it with another
 		 * page and dirtied it.  In that improbable case, SyncOneBuffer will
 		 * write the buffer though we didn't need to.  It doesn't seem worth

src/backend/storage/freespace/freespace.c

@@ -393,7 +393,7 @@ fsm_space_needed_to_cat(Size needed)
 }
 
 /*
- * Returns the physical block number an FSM page
+ * Returns the physical block number of a FSM page
  */
 static BlockNumber
 fsm_logical_to_physical(FSMAddress addr)
@@ -472,7 +472,7 @@ fsm_get_parent(FSMAddress child, uint16 *slot)
 }
 
 /*
- * Given a logical address of a parent page, and a slot number get the
+ * Given a logical address of a parent page and a slot number, get the
  * logical address of the corresponding child page.
  */
 static FSMAddress

src/backend/storage/ipc/procarray.c

@@ -2673,7 +2673,7 @@ MinimumActiveBackends(int min)
 
 		/*
 		 * Since we're not holding a lock, need to be prepared to deal with
-		 * garbage, as someone could have incremented numPucs but not yet
+		 * garbage, as someone could have incremented numProcs but not yet
 		 * filled the structure.
 		 *
 		 * If someone just decremented numProcs, 'proc' could also point to a