diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 14aae736c3..7452d7cfa6 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -4361,7 +4361,7 @@ SELECT (regexp_match('foobarbequebaz', 'bar.*que'))[1];
Some examples:
- SELECT regexp_matches('foo', 'not there');
+SELECT regexp_matches('foo', 'not there');
regexp_matches
----------------
(0 rows)
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 92e3b454fb..ce67d4a5e3 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1175,7 +1175,7 @@ synchronous_standby_names = 'FIRST 2 (s1, s2, s3)'
An example of synchronous_standby_names for
a quorum-based multiple synchronous standbys is:
- synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
+synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
In this example, if four standby servers s1, s2,
s3 and s4 are running, transaction commits will
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 23e6f1c3dc..c3bd4f9b9b 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -5941,12 +5941,12 @@ char *PQencryptPasswordConn(PGconn *conn, const char *passwd, const char *user,
Prepares the md5-encrypted form of a PostgreSQL password.
-
+
char *PQencryptPassword(const char *passwd, const char *user);
-
- PQencryptPassword is an older, deprecated version of
+
+ PQencryptPassword is an older, deprecated version of
PQencryptPasswodConn. The difference is that
- PQencryptPassword does not
+ PQencryptPassword does not
require a connection object, and md5 is always used as the
encryption algorithm.
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 79ca45a156..9ff5eea038 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -802,7 +802,7 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
backend_type
text
- Type of current backend. Possible types are
+ Type of current backend. Possible types are
autovacuum launcher, autovacuum worker,
background worker, background writer,
client backend, checkpointer,
@@ -1827,7 +1827,7 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
the standby to catch up with the sending server assuming the current
rate of replay. Such a system would show similar times while new WAL is
being generated, but would differ when the sender becomes idle. In
- particular, when the standby has caught up completely,
+ particular, when the standby has caught up completely,
pg_stat_replication shows the time taken to
write, flush and replay the most recent reported WAL location rather than
zero as some users might expect. This is consistent with the goal of
diff --git a/doc/src/sgml/parallel.sgml b/doc/src/sgml/parallel.sgml
index a65129078c..ff31e7537e 100644
--- a/doc/src/sgml/parallel.sgml
+++ b/doc/src/sgml/parallel.sgml
@@ -275,7 +275,7 @@ EXPLAIN SELECT * FROM pgbench_accounts WHERE filler LIKE '%x%';
In a parallel sequential scan, the table's blocks will
be divided among the cooperating processes. Blocks are handed out one
- at a time, so that access to the table remains sequential.
+ at a time, so that access to the table remains sequential.
diff --git a/doc/src/sgml/pgstattuple.sgml b/doc/src/sgml/pgstattuple.sgml
index b6a5f19e70..e98e04fa2f 100644
--- a/doc/src/sgml/pgstattuple.sgml
+++ b/doc/src/sgml/pgstattuple.sgml
@@ -119,13 +119,13 @@ free_percent | 1.95
-
- The table_len will always be greater than the sum
- of the tuple_len, dead_tuple_len
- and free_space. The difference is accounted for by
- fixed page overhead, the per-page table of pointers to tuples, and
- padding to ensure that tuples are correctly aligned.
-
+
+ The table_len will always be greater than the sum
+ of the tuple_len, dead_tuple_len
+ and free_space. The difference is accounted for by
+ fixed page overhead, the per-page table of pointers to tuples, and
+ padding to ensure that tuples are correctly aligned.
+
diff --git a/doc/src/sgml/postgres-fdw.sgml b/doc/src/sgml/postgres-fdw.sgml
index 3dfc0f84ed..23558e7ec0 100644
--- a/doc/src/sgml/postgres-fdw.sgml
+++ b/doc/src/sgml/postgres-fdw.sgml
@@ -566,7 +566,7 @@
- These are less likely to be problematic than search_path, but
+ These are less likely to be problematic than search_path, but
can be handled with function SET options if the need arises.
diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index 4837be5016..a7a3d3b2f9 100644
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -1352,7 +1352,7 @@ general, while the next subsection gives more details on SCRAM-SHA-256.
SASL Authentication Message Flow
-
+
To begin a SASL authentication exchange, the server sends an
AuthenticationSASL message. It includes a list of SASL authentication
mechanisms that the server can accept, in the server's preferred order.
@@ -1401,7 +1401,7 @@ ErrorMessage.
SCRAM-SHA-256 (called just SCRAM from now on) is
the only implemented SASL mechanism, at the moment. It is described in detail
- in RFC 7677 and RFC 5802.
+ in RFC 7677 and RFC 5802.
diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 4c61c44265..69600321e6 100644
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -185,7 +185,7 @@ ALTER TABLE [ IF EXISTS ] name
table. Even if there is no NOT NULL constraint on the
parent, such a constraint can still be added to individual partitions,
if desired; that is, the children can disallow nulls even if the parent
- allows them, but not the other way around.
+ allows them, but not the other way around.
@@ -617,7 +617,7 @@ ALTER TABLE [ IF EXISTS ] name
- SHARE UPDATE EXCLUSIVE lock will be taken for
+ SHARE UPDATE EXCLUSIVE lock will be taken for
fillfactor and autovacuum storage parameters, as well as the
following planner related parameters:
effective_io_concurrency, parallel_workers, seq_page_cost
diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index 215efcd69d..8de1150dfb 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -425,7 +425,7 @@ COPY count
- If row-level security is enabled for the table, the relevant
+ If row-level security is enabled for the table, the relevant
SELECT policies will apply to COPY
table TO statements.
Currently, COPY FROM is not supported for tables