Skip to content

Commit 594df37

Browse files
peterepetere
committed
doc: Spell checking
1 parent 313f87a commit 594df37

File tree

8 files changed

+32
-32
lines changed

8 files changed

+32
-32
lines changed

‎doc/src/sgml/btree.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -298,7 +298,7 @@ returns bool
298298

299299
<para>
300300
The essential semantics of an <function>in_range</function> function
301-
depend on the two boolean flag parameters. It should add or
301+
depend on the two Boolean flag parameters. It should add or
302302
subtract <replaceable>base</replaceable>
303303
and <replaceable>offset</replaceable>, then
304304
compare <replaceable>val</replaceable> to the result, as follows:

‎doc/src/sgml/client-auth.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1729,7 +1729,7 @@ ldap[s]://<replaceable>host</replaceable>[:<replaceable>port</replaceable>]/<rep
17291729
If <productname>PostgreSQL</productname> was compiled with
17301730
<productname>OpenLDAP</productname> as the LDAP client library, the
17311731
<literal>ldapserver</literal> setting may be omitted. In that case, a
1732-
list of hostnames and ports is looked up via RFC 2782 DNS SRV records.
1732+
list of host names and ports is looked up via RFC 2782 DNS SRV records.
17331733
The name <literal>_ldap._tcp.DOMAIN</literal> is looked up, where
17341734
<literal>DOMAIN</literal> is extracted from <literal>ldapbasedn</literal>.
17351735
</para>
@@ -1781,7 +1781,7 @@ host ... ldap ldapserver=ldap.example.net ldapbasedn="dc=example, dc=net" ldapse
17811781

17821782
<para>
17831783
Here is an example for a search+bind configuration that uses DNS SRV
1784-
discovery to find the hostname(s) and port(s) for the LDAP service for the
1784+
discovery to find the host name(s) and port(s) for the LDAP service for the
17851785
domain name <literal>example.net</literal>:
17861786
<programlisting>
17871787
host ... ldap ldapbasedn="dc=example,dc=net"

‎doc/src/sgml/config.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3624,9 +3624,9 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
36243624
<listitem>
36253625
<para>
36263626
If set to <literal>on</literal> (the default), this option causes new
3627-
WAL files to be filled with zeroes. On some filesystems, this ensures
3627+
WAL files to be filled with zeroes. On some file systems, this ensures
36283628
that space is allocated before we need to write WAL records. However,
3629-
<firstterm>Copy-On-Write</firstterm> (COW) filesystems may not benefit
3629+
<firstterm>Copy-On-Write</firstterm> (COW) file systems may not benefit
36303630
from this technique, so the option is given to skip the unnecessary
36313631
work. If set to <literal>off</literal>, only the final byte is written
36323632
when the file is created so that it has the expected size.
@@ -3644,7 +3644,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
36443644
<para>
36453645
If set to <literal>on</literal> (the default), this option causes WAL
36463646
files to be recycled by renaming them, avoiding the need to create new
3647-
ones. On COW filesystems, it may be faster to create new ones, so the
3647+
ones. On COW file systems, it may be faster to create new ones, so the
36483648
option is given to disable this behavior.
36493649
</para>
36503650
</listitem>
@@ -8930,7 +8930,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
89308930
<para>
89318931
When set to off, which is the default, <productname>PostgreSQL</productname>
89328932
will raise a PANIC-level error on failure to flush modified data files
8933-
to the filesystem. This causes the database server to crash. This
8933+
to the file system. This causes the database server to crash. This
89348934
parameter can only be set at server start.
89358935
</para>
89368936
<para>

‎doc/src/sgml/func.sgml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11624,7 +11624,7 @@ table2-mapping
1162411624
The result of each path evaluation step can be processed
1162511625
by one or more <type>jsonpath</type> operators and methods
1162611626
listed in <xref linkend="functions-sqljson-path-operators"/>.
11627-
Each method must be preceded by a dot, while arithmetic and boolean
11627+
Each method must be preceded by a dot, while arithmetic and Boolean
1162811628
operators are separated from the operands by spaces. For example,
1162911629
you can get an array size:
1163011630
<programlisting>
@@ -11719,7 +11719,7 @@ table2-mapping
1171911719

1172011720
<listitem>
1172111721
<para>
11722-
A path expression can be a boolean predicate, although the SQL/JSON
11722+
A path expression can be a Boolean predicate, although the SQL/JSON
1172311723
standard allows predicates only in filters. This is necessary for
1172411724
implementation of the <literal>@@</literal> operator. For example,
1172511725
the following<type>jsonpath</type> expression is valid in
@@ -12073,7 +12073,7 @@ table2-mapping
1207312073
</row>
1207412074
<row>
1207512075
<entry><literal>is unknown</literal></entry>
12076-
<entry>Tests whether a boolean condition is <literal>unknown</literal></entry>
12076+
<entry>Tests whether a Boolean condition is <literal>unknown</literal></entry>
1207712077
<entry><literal>[-1, 2, 7, "infinity"]</literal></entry>
1207812078
<entry><literal>$[*] ? ((@ > 0) is unknown)</literal></entry>
1207912079
<entry><literal>"infinity"</literal></entry>
@@ -12292,8 +12292,8 @@ table2-mapping
1229212292
<entry><literal>@@</literal></entry>
1229312293
<entry><type>jsonpath</type></entry>
1229412294
<entry>JSON path predicate check result for the specified JSON value.
12295-
Only first result item is taken into account. If there is no results
12296-
or first result item is not bool, then <literal>NULL</literal>
12295+
Only first result item is taken into account. If there are no results
12296+
or the first result item is not Boolean, then null
1229712297
is returned.</entry>
1229812298
<entry><literal>'{"a":[1,2,3,4,5]}'::jsonb @@ '$.a[*] > 2'</literal></entry>
1229912299
</row>
@@ -12958,8 +12958,8 @@ table2-mapping
1295812958
<entry><type>boolean</type></entry>
1295912959
<entry>
1296012960
Returns JSON path predicate result for the specified JSON value.
12961-
Only first result item is taken into account. If there is no results
12962-
or first result item is not bool, then <literal>NULL</literal>
12961+
Only first result item is taken into account. If there are no results
12962+
or the first result item is not Boolean, then null
1296312963
is returned.
1296412964
</entry>
1296512965
<entry>

‎doc/src/sgml/gin.sgml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -227,7 +227,7 @@
227227
<para>
228228
<literal>pmatch</literal> is an output argument for use when partial match
229229
is supported. To use it, <function>extractQuery</function> must allocate
230-
an array of <literal>*nkeys</literal> bools and store its address at
230+
an array of <literal>*nkeys</literal> <type>bool</type>s and store its address at
231231
<literal>*pmatch</literal>. Each element of the array should be set to true
232232
if the corresponding key requires partial match, false if not.
233233
If <literal>*pmatch</literal> is set to <symbol>NULL</symbol> then GIN assumes partial match
@@ -255,12 +255,12 @@
255255
</variablelist>
256256

257257
An operator class must also provide a function to check if an indexed item
258-
matches the query. It comes in two flavors, a boolean <function>consistent</function>
258+
matches the query. It comes in two flavors, a Boolean <function>consistent</function>
259259
function, and a ternary <function>triConsistent</function> function.
260260
<function>triConsistent</function> covers the functionality of both, so providing
261-
<function>triConsistent</function> alone is sufficient. However, if the boolean
261+
<function>triConsistent</function> alone is sufficient. However, if the Boolean
262262
variant is significantly cheaper to calculate, it can be advantageous to
263-
provide both. If only the boolean variant is provided, some optimizations
263+
provide both. If only the Boolean variant is provided, some optimizations
264264
that depend on refuting index items before fetching all the keys are
265265
disabled.
266266

@@ -323,11 +323,11 @@
323323
<listitem>
324324
<para>
325325
<function>triConsistent</function> is similar to <function>consistent</function>,
326-
but instead of booleans in the <literal>check</literal> vector, there are
326+
but instead of Booleans in the <literal>check</literal> vector, there are
327327
three possible values for each
328328
key: <literal>GIN_TRUE</literal>, <literal>GIN_FALSE</literal> and
329329
<literal>GIN_MAYBE</literal>. <literal>GIN_FALSE</literal> and <literal>GIN_TRUE</literal>
330-
have the same meaning as regular boolean values, while
330+
have the same meaning as regular Boolean values, while
331331
<literal>GIN_MAYBE</literal> means that the presence of that key is not known.
332332
When <literal>GIN_MAYBE</literal> values are present, the function should only
333333
return <literal>GIN_TRUE</literal> if the item certainly matches whether or
@@ -342,7 +342,7 @@
342342
When there are no <literal>GIN_MAYBE</literal> values in the <literal>check</literal>
343343
vector, a <literal>GIN_MAYBE</literal> return value is the equivalent of
344344
setting the <literal>recheck</literal> flag in the
345-
boolean <function>consistent</function> function.
345+
Boolean <function>consistent</function> function.
346346
</para>
347347
</listitem>
348348
</varlistentry>

‎doc/src/sgml/json.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -849,8 +849,8 @@ SELECT jdoc-&gt;'guid', jdoc-&gt;'name' FROM api WHERE jdoc @&gt; '{"tags": ["qu
849849
corresponds to the first array element.
850850
</para>
851851
<para>
852-
Expression inside subscript may consititue an integer,
853-
numeric expression or any other <literal>jsonpath</literal> expression
852+
An expression in the subscript may be an integer,
853+
numeric expression, or any other <literal>jsonpath</literal> expression
854854
returning single numeric value. The <literal>last</literal> keyword
855855
can be used in the expression denoting the last subscript in an array.
856856
That's helpful for handling arrays of unknown length.

‎doc/src/sgml/spgist.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -213,7 +213,7 @@
213213
The <literal>quad_point_ops</literal>, <literal>kd_point_ops</literal> and
214214
<literal>poly_ops</literal> operator classes support the <literal>&lt;-&gt;</literal>
215215
ordering operator, which enables the k-nearest neighbor (<literal>k-NN</literal>)
216-
search over indexed point or polygon datasets.
216+
search over indexed point or polygon data sets.
217217
</para>
218218

219219
</sect1>

‎doc/src/sgml/xfunc.sgml

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1083,10 +1083,10 @@ SELECT x, g FROM tab, LATERAL generate_series(1,5) AS g;
10831083
</programlisting>
10841084
It would be exactly the same, except that in this specific example,
10851085
the planner could choose to put <structname>g</structname> on the outside of the
1086-
nestloop join, since <structname>g</structname> has no actual lateral dependency
1086+
nested-loop join, since <structname>g</structname> has no actual lateral dependency
10871087
on <structname>tab</structname>. That would result in a different output row
10881088
order. Set-returning functions in the select list are always evaluated
1089-
as though they are on the inside of a nestloop join with the rest of
1089+
as though they are on the inside of a nested-loop join with the rest of
10901090
the <literal>FROM</literal> clause, so that the function(s) are run to
10911091
completion before the next row from the <literal>FROM</literal> clause is
10921092
considered.
@@ -3441,14 +3441,14 @@ supportfn(internal) returns internal
34413441
</para>
34423442

34433443
<para>
3444-
For target functions that return boolean, it is often useful to estimate
3445-
the fraction of rows that will be selected by a WHERE clause using that
3444+
For target functions that return <type>boolean</type>, it is often useful to estimate
3445+
the fraction of rows that will be selected by a <literal>WHERE</literal> clause using that
34463446
function. This can be done by a support function that implements
34473447
the <literal>SupportRequestSelectivity</literal> request type.
34483448
</para>
34493449

34503450
<para>
3451-
If the target function's runtime is highly dependent on its inputs,
3451+
If the target function's run time is highly dependent on its inputs,
34523452
it may be useful to provide a non-constant cost estimate for it.
34533453
This can be done by a support function that implements
34543454
the <literal>SupportRequestCost</literal> request type.
@@ -3462,15 +3462,15 @@ supportfn(internal) returns internal
34623462
</para>
34633463

34643464
<para>
3465-
For target functions that return boolean, it may be possible to
3466-
convert a function call appearing in WHERE into an indexable operator
3465+
For target functions that return <type>boolean</type>, it may be possible to
3466+
convert a function call appearing in <literal>WHERE</literal> into an indexable operator
34673467
clause or clauses. The converted clauses might be exactly equivalent
34683468
to the function's condition, or they could be somewhat weaker (that is,
34693469
they might accept some values that the function condition does not).
34703470
In the latter case the index condition is said to
34713471
be <firstterm>lossy</firstterm>; it can still be used to scan an index,
34723472
but the function call will have to be executed for each row returned by
3473-
the index to see if it really passes the WHERE condition or not.
3473+
the index to see if it really passes the <literal>WHERE</literal> condition or not.
34743474
To create such conditions, the support function must implement
34753475
the <literal>SupportRequestIndexCondition</literal> request type.
34763476
</para>

0 commit comments

Comments
 (0)