diff options
author | David Rowley | 2022-04-13 21:16:05 +0000 |
---|---|---|
committer | David Rowley | 2022-04-13 21:16:05 +0000 |
commit | ac8be0cb957811d04d7564f4d710ceb3e5f2fb9f (patch) | |
tree | 29a3cfe3fe65906d212d91a68e1925d0e849cb62 | |
parent | b5607b0746f40b3f5b38004c64ccc9697ee1e222 (diff) |
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/[email protected]
-rw-r--r-- | doc/src/sgml/charset.sgml | 12 | ||||
-rw-r--r-- | doc/src/sgml/ref/initdb.sgml | 2 |
2 files changed, 7 insertions, 7 deletions
diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index d60d3207fd..b95303fb89 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -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. diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml index f5d633b0af..c9ffaaecfb 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -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 |