rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Docs: fix some spelling mistakes and also do some wordsmithing 

All except one of these are new to v15.  Only one of the wordsmithing
changes appears in older versions. The wordsmithing improvement does not
seem significant enough to warrant backpatching.

Author: Justin Pryzby
Discussion: https://postgr.es/m/20220411020336.GB26620@telsasoft.com
This commit is contained in:
David Rowley 2022-04-14 09:16:05 +12:00
parent b5607b0746
commit ac8be0cb95
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/src/sgml/charset.sgml
View File

@ -314,7 +314,7 @@ initdb --locale=sv_SE
A locale can be selected separately for each database. The SQL command
<command>CREATE DATABASE</command> and its command-line equivalent
<command>createdb</command> have options for that. Use this for example
if a database cluster houses databases for multiple tennants with
if a database cluster houses databases for multiple tenants with
different requirements.
</para>
</listitem>
@ -346,7 +346,7 @@ initdb --locale=sv_SE
providers</firstterm>. This specifies which library supplies the locale
data. One standard provider name is <literal>libc</literal>, which uses
the locales provided by the operating system C library. These are the
locales that most tools provided by the operating system use. Another
locales used by most tools provided by the operating system. Another
provider is <literal>icu</literal>, which uses the external
ICU<indexterm><primary>ICU</primary></indexterm> library. ICU locales can
only be used if support for ICU was configured when PostgreSQL was built.
@ -361,8 +361,8 @@ initdb --locale=sv_SE
<programlisting>
initdb --locale-provider=icu --icu-locale=en
</programlisting>
See the description of the respective commands and programs for the
respective details. Note that you can mix locale providers on different
See the description of the respective commands and programs for
details. Note that you can mix locale providers at different
granularities, for example use <literal>libc</literal> by default for the
cluster but have one database that uses the <literal>icu</literal>
provider, and then have collation objects using either provider within
@ -610,8 +610,8 @@ SELECT * FROM test1 ORDER BY a || b COLLATE "fr_FR";
definition has a <firstterm>provider</firstterm> that specifies which
library supplies the locale data. One standard provider name
is <literal>libc</literal>, which uses the locales provided by the
operating system C library. These are the locales that most tools
provided by the operating system use. Another provider
operating system C library. These are the locales used by most tools
provided by the operating system. Another provider
is <literal>icu</literal>, which uses the external
ICU<indexterm><primary>ICU</primary></indexterm> library. ICU locales can only be
used if support for ICU was configured when PostgreSQL was built.

2
doc/src/sgml/ref/initdb.sgml
View File

@ -108,7 +108,7 @@ PostgreSQL documentation
Alternatively, the ICU library can be used to provide locale services.
(Again, this only sets the default for subsequently created databases.) To
select this option, specify <literal>--locale-provider=icu</literal>.
To chose the specific ICU locale ID to apply, use the option
To choose the specific ICU locale ID to apply, use the option
<option>--icu-locale</option>. Note that
for implementation reasons and to support legacy code,
<command>initdb</command> will still select and initialize libc locale