doc: Spell checking

contrib/pg_stat_statements/pg_stat_statements.c

@@ -4,7 +4,7 @@
  *		Track statement planning and execution times as well as resource
  *		usage across a whole database cluster.
  *
- * Execution costs are totalled for each distinct source query, and kept in
+ * Execution costs are totaled for each distinct source query, and kept in
  * a shared hashtable.  (We track only as many distinct queries as will fit
  * in the designated amount of shared memory.)
  *

doc/src/sgml/backup-manifest.sgml

@@ -26,7 +26,7 @@
   </para>
 
  <sect1 id="backup-manifest-toplevel">
-  <title>Backup Manifest Toplevel Object</title>
+  <title>Backup Manifest Top-level Object</title>
 
   <para>
    The backup manifest JSON document contains the following keys.
@@ -93,7 +93,7 @@
    Normally, the <literal>Path</literal> key will be present. The
    associated string value is the path of the file relative to the root
    of the backup directory. Files located in a user-defined tablespace
-   will have paths whose first two components are pg_tblspc and the OID
+   will have paths whose first two components are <filename>pg_tblspc</filename> and the OID
    of the tablespace. If the path is not a string that is legal in UTF-8,
    or if the user requests that encoded paths be used for all files, then
    the <literal>Encoded-Path</literal> key will be present instead.  This

doc/src/sgml/extend.sgml

@@ -767,7 +767,7 @@ RETURNS anycompatible AS ...
         <literal>false</literal>.
         Generally, this should not be set true for extensions that could
         allow access to otherwise-superuser-only abilities, such as
-        filesystem access.
+        file system access.
        </para>
       </listitem>
      </varlistentry>

doc/src/sgml/fdwhandler.sgml

@@ -450,7 +450,7 @@ AddForeignUpdateTargets(Query *parsetree,
      generate junk columns of these names.
      If the extra expressions are more complex than simple Vars, they
      must be run through <function>eval_const_expressions</function>
-     before adding them to the targetlist.
+     before adding them to the target list.
     </para>
 
     <para>

doc/src/sgml/glossary.sgml

@@ -432,7 +432,7 @@
    <glossterm>Data directory</glossterm>
    <glossdef>
     <para>
-     The base directory on the filesystem of a
+     The base directory on the file system of a
      <glossterm linkend="glossary-server">server</glossterm> that contains all
      data files and subdirectories associated with a
      <glossterm linkend="glossary-db-cluster">database cluster</glossterm>
@@ -1548,7 +1548,7 @@
    <glossterm>Tablespace</glossterm>
    <glossdef>
     <para>
-     A named location on the server filesystem.
+     A named location on the server file system.
      All <glossterm linkend="glossary-sql-object">SQL objects</glossterm>
      which require storage beyond their definition in the
      <glossterm linkend="glossary-system-catalog">system catalog</glossterm>
@@ -1646,7 +1646,7 @@
    <glossdef>
     <para>
      Average number of transactions that are executed per second,
-     totalled across all sessions active for a measured run.
+     totaled across all sessions active for a measured run.
      This is used as a measure of the performance characteristics of
      an instance.
     </para>

doc/src/sgml/maintenance.sgml

@@ -998,7 +998,7 @@ pg_ctl start | rotatelogs /var/log/pgsql_log 86400
     In this case, log messages are sent to the old log file until a
     successful log rotation. If <application>logrotate</application> is
     configured to compress the log file and delete it, the server may lose
-    the messages logged in this timeframe. To avoid this issue, you can
+    the messages logged in this time frame. To avoid this issue, you can
     configure the logging collector to dynamically assign log file names
     and use a <literal>prerotate</literal> script to ignore open log files.
     </para>

doc/src/sgml/monitoring.sgml

@@ -2474,7 +2474,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
       <para>
        Number of transactions spilled to disk after the memory used by
        logical decoding exceeds <literal>logical_decoding_work_mem</literal>. The
-       counter gets incremented both for toplevel transactions and
+       counter gets incremented both for top-level transactions and
        subtransactions.
       </para></entry>
      </row>

doc/src/sgml/ref/create_table.sgml

@@ -1364,8 +1364,8 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
       This only affects columns marked as either External or Extended
       and applies only to new tuples; there is no effect on existing rows.
       By default this parameter is set to allow at least 4 tuples per block,
-      which with the default blocksize will be 2040 bytes. Valid values are
-      between 128 bytes and the (blocksize - header), by default 8160 bytes.
+      which with the default block size will be 2040 bytes. Valid values are
+      between 128 bytes and the (block size - header), by default 8160 bytes.
       Changing this value may not be useful for very short or very long rows.
       Note that the default setting is often close to optimal, and
       it is possible that setting this parameter could have negative

doc/src/sgml/ref/pg_dump.sgml

@@ -788,7 +788,7 @@ PostgreSQL documentation
         <para>
          When <option>--include-foreign-data</option> is specified,
          <application>pg_dump</application> does not check that the foreign
-         table is writeable.  Therefore, there is no guarantee that the
+         table is writable.  Therefore, there is no guarantee that the
          results of a foreign table dump can be successfully restored.
         </para>
        </note>

doc/src/sgml/ref/pg_verifybackup.sgml

@@ -93,7 +93,7 @@ PostgreSQL documentation
    <literal>backup_manifest</literal> contains information about which
    write-ahead log records will be needed, and
    <literal>pg_verifybackup</literal> will use that information to
-   invoke <literal>pg_waldump</literal> to parse those write-ahed log
+   invoke <literal>pg_waldump</literal> to parse those write-ahead log
    records. The <literal>--quiet</literal> flag will be used, so that
    <literal>pg_waldump</literal> will only report errors, without producing
    any other output. While this level of verification is sufficient to
@@ -143,13 +143,13 @@ PostgreSQL documentation
       <listitem>
        <para>
         Ignore the specified file or directory, which should be expressed
-        as a relative pathname, when comparing the list of data files
+        as a relative path name, when comparing the list of data files
         actually present in the backup to those listed in the
         <literal>backup_manifest</literal> file.  If a directory is
         specified, this option affects the entire subtree rooted at that
         location. Complaints about extra files, missing files, file size
         differences, or checksum mismatches will be suppressed if the
-        relative pathname matches the specified pathname. This option
+        relative path name matches the specified path name. This option
         can be specified multiple times.
        </para>
       </listitem>

doc/src/sgml/ref/pgbench.sgml

@@ -1886,7 +1886,7 @@ SELECT 4 AS four \; SELECT 5 AS five \aset
         <returnvalue>integer</returnvalue>
        </para>
        <para>
-        Computes a gaussian-distributed random integer in <literal>[lb,
+        Computes a Gaussian-distributed random integer in <literal>[lb,
         ub]</literal>, see below.
        </para>
        <para>