Commit 9ffe128a authored by Daniel Gustafsson's avatar Daniel Gustafsson

docs: fix inconsistencies in markup and case

Ensure to properly mark up function parameters in text with <parameter>,
avoid using <acronym> for terms which aren't acronyms and properly place
the ", and" in a value list. The acronym removal is a follow-up to commit
fb72a7b8 which removed it for minmax-multi.  In passing, also fix an
incorrectly cased word.

Author: Ekaterina Kiryanova <e.kiryanova@postgrespro.ru>
Reviewed-by: default avatarLaurenz Albe <laurenz.albe@cybertec.at>
Discussion: https://postgr.es/m/c050ecbc-80b2-b360-3c1d-9fe6a6a11bb5@postgrespro.ru
Backpatch-through: v14
parent 081e86bd
...@@ -279,7 +279,7 @@ SET client_min_messages = DEBUG1; ...@@ -279,7 +279,7 @@ SET client_min_messages = DEBUG1;
<para> <para>
If specified, corruption checking begins at the specified block, If specified, corruption checking begins at the specified block,
skipping all previous blocks. It is an error to specify a skipping all previous blocks. It is an error to specify a
<literal>startblock</literal> outside the range of blocks in the <parameter>startblock</parameter> outside the range of blocks in the
target table. target table.
</para> </para>
<para> <para>
...@@ -293,7 +293,7 @@ SET client_min_messages = DEBUG1; ...@@ -293,7 +293,7 @@ SET client_min_messages = DEBUG1;
<para> <para>
If specified, corruption checking ends at the specified block, If specified, corruption checking ends at the specified block,
skipping all remaining blocks. It is an error to specify an skipping all remaining blocks. It is an error to specify an
<literal>endblock</literal> outside the range of blocks in the target <parameter>endblock</parameter> outside the range of blocks in the target
table. table.
</para> </para>
<para> <para>
......
...@@ -716,7 +716,7 @@ LOG: request for BRIN range summarization for index "brin_wi_idx" page 128 was ...@@ -716,7 +716,7 @@ LOG: request for BRIN range summarization for index "brin_wi_idx" page 128 was
</para> </para>
<para> <para>
<acronym>bloom</acronym> operator classes accept these parameters: bloom operator classes accept these parameters:
</para> </para>
<variablelist> <variablelist>
......
...@@ -7403,8 +7403,8 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l ...@@ -7403,8 +7403,8 @@ SCRAM-SHA-256$<replaceable>&lt;iteration count&gt;</replaceable>:<replaceable>&l
An array containing codes for the enabled statistics kinds; An array containing codes for the enabled statistics kinds;
valid values are: valid values are:
<literal>d</literal> for n-distinct statistics, <literal>d</literal> for n-distinct statistics,
<literal>f</literal> for functional dependency statistics, and <literal>f</literal> for functional dependency statistics,
<literal>m</literal> for most common values (MCV) list statistics <literal>m</literal> for most common values (MCV) list statistics, and
<literal>e</literal> for expression statistics <literal>e</literal> for expression statistics
</para></entry> </para></entry>
</row> </row>
......
...@@ -7013,7 +7013,7 @@ local0.* /var/log/postgresql ...@@ -7013,7 +7013,7 @@ local0.* /var/log/postgresql
</row> </row>
<row> <row>
<entry><literal>%Q</literal></entry> <entry><literal>%Q</literal></entry>
<entry>query identifier of the current query. Query <entry>Query identifier of the current query. Query
identifiers are not computed by default, so this field identifiers are not computed by default, so this field
will be zero unless <xref linkend="guc-compute-query-id"/> will be zero unless <xref linkend="guc-compute-query-id"/>
parameter is enabled or a third-party module that computes parameter is enabled or a third-party module that computes
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment