More fixes like the one Peter committed as 9bd563aa9.
I eyeballed the HTML to make sure this looks right.
From a8b782cde7c5d6eef1e3876636feb652bc5f3711 Mon Sep 17 00:00:00 2001
From: Justin Pryzby <pryzbyj@telsasoft.com>
Date: Thu, 22 Apr 2021 21:10:49 -0500
Subject: [PATCH] Remove extraneous whitespace in tags
git grep -E '<([^>]*)>[^<]* </\1>' doc/src/sgml |grep -Evw 'optional|xsl|lineannotation|entry|prompt|computeroutput'
---
doc/src/sgml/maintenance.sgml | 2 +-
doc/src/sgml/mvcc.sgml | 2 +-
doc/src/sgml/pgcrypto.sgml | 2 +-
doc/src/sgml/ref/pg_rewind.sgml | 2 +-
doc/src/sgml/runtime.sgml | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 4adb34a21b..ee6113926a 100644
--- 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 b46cba8158..6cb9c63161 100644
--- 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 b6bb23de0f..13770dfc6f 100644
--- 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 07aae75d8b..33e6bb64ad 100644
--- 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 001d195b8e..f1cbc1d9e9 100644
--- 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.
--
2.17.0
