Doc: Remove extraneous whitespaces with some tags

Author: Justin Pryzby
Discussion: https://postgr.es/m/20210423184338.GL7256@telsasoft.com

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 4adb34a21b145338e45d440c10a758a18115ebee..ee6113926ac8c5756aa9a595a6acf72634d94eeb 100644 (file)
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -719,7 +719,7 @@ HINT:  Stop the postmaster and vacuum that database in single-user mode.
     <productname>PostgreSQL</productname> has an optional but highly
     recommended feature called <firstterm>autovacuum</firstterm>,
     whose purpose is to automate the execution of
-    <command>VACUUM</command> and <command>ANALYZE </command> commands.
+    <command>VACUUM</command> and <command>ANALYZE</command> commands.
     When enabled, autovacuum checks for
     tables that have had a large number of inserted, updated or deleted
     tuples.  These checks use the statistics collection facility;

diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index b46cba8158285fe348246421c801a16ffe07dc11..6cb9c631613d8914c7a2e7b91c4a6500383ffa06 100644 (file)
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -1074,7 +1074,7 @@ ERROR:  could not serialize access due to read/write dependencies among transact
 
 
     <table tocentry="1" id="table-lock-compatibility">
-     <title> Conflicting Lock Modes</title>
+     <title>Conflicting Lock Modes</title>
      <tgroup cols="9">
       <colspec colnum="1" colwidth="1.25*"/>
       <colspec colnum="2" colwidth="1*" colname="lockst"/>

diff --git a/doc/src/sgml/pgcrypto.sgml b/doc/src/sgml/pgcrypto.sgml
index b6bb23de0f91dec685048fb97fdfa936a9c22c47..13770dfc6f66cecfde5dbef24a94e0de2ed85c91 100644 (file)
--- a/doc/src/sgml/pgcrypto.sgml
+++ b/doc/src/sgml/pgcrypto.sgml
@@ -1410,7 +1410,7 @@ gen_random_uuid() returns uuid
       <entry>KAME kame/sys/crypto</entry>
      </row>
      <row>
-      <entry>SHA256/384/512 </entry>
+      <entry>SHA256/384/512</entry>
       <entry>Aaron D. Gifford</entry>
       <entry>OpenBSD sys/crypto</entry>
      </row>

diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml
index 07aae75d8b7972b18b3d4f8f85924f641cbc03d4..33e6bb64ad61c5830d323e47f499d9828ebecaa0 100644 (file)
--- a/doc/src/sgml/ref/pg_rewind.sgml
+++ b/doc/src/sgml/ref/pg_rewind.sgml
@@ -25,7 +25,7 @@ PostgreSQL documentation
    <arg rep="repeat"><replaceable>option</replaceable></arg>
    <group choice="plain">
     <group choice="req">
-     <arg choice="plain"><option>-D </option></arg>
+     <arg choice="plain"><option>-D</option></arg>
      <arg choice="plain"><option>--target-pgdata</option></arg>
     </group>
     <replaceable> directory</replaceable>

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 001d195b8e31607a49ccef51b6bfdde4db146217..f1cbc1d9e922b43b7d674d25c4e49f20d16f15d5 100644 (file)
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -2258,7 +2258,7 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
    The certificates of <quote>intermediate</quote> certificate authorities
    can also be appended to the file.  Doing this avoids the necessity of
    storing intermediate certificates on clients, assuming the root and
-   intermediate certificates were created with <literal>v3_ca </literal>
+   intermediate certificates were created with <literal>v3_ca</literal>
    extensions.  (This sets the certificate's basic constraint of
    <literal>CA</literal> to <literal>true</literal>.)
    This allows easier expiration of intermediate certificates.