From 1d96cf94049d8df2197d040a395fb46926ea9f2a Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 14 Aug 2012 12:36:35 -0400
Subject: [PATCH] In documentation, change "recommendable" to "recommended",
per consultation with word definitions.
Backpatch to 9.2.
---
doc/src/sgml/charset.sgml | 2 +-
doc/src/sgml/installation.sgml | 2 +-
doc/src/sgml/manage-ag.sgml | 2 +-
doc/src/sgml/passwordcheck.sgml | 2 +-
doc/src/sgml/queries.sgml | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml
index 6b0793e2197..67e39b2564d 100644
--- a/doc/src/sgml/charset.sgml
+++ b/doc/src/sgml/charset.sgml
@@ -563,7 +563,7 @@ SELECT * FROM test1 ORDER BY a || b COLLATE "fr_FR";
<literal>pg_collation</literal> are ignored. Thus, a stripped collation
name such as <literal>de_DE</literal> can be considered unique
within a given database even though it would not be unique globally.
- Use of the stripped collation names is recommendable, since it will
+ Use of the stripped collation names is recommended, since it will
make one less thing you need to change if you decide to change to
another database encoding. Note however that the <literal>default</>,
<literal>C</>, and <literal>POSIX</> collations can be used
diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
index 056e802b405..c02ed87c41a 100644
--- a/doc/src/sgml/installation.sgml
+++ b/doc/src/sgml/installation.sgml
@@ -92,7 +92,7 @@ su - postgres
<para>
You need an <acronym>ISO</>/<acronym>ANSI</> C compiler (at least
C89-compliant). Recent
- versions of <productname>GCC</> are recommendable, but
+ versions of <productname>GCC</> are recommended, but
<productname>PostgreSQL</> is known to build using a wide variety
of compilers from different vendors.
</para>
diff --git a/doc/src/sgml/manage-ag.sgml b/doc/src/sgml/manage-ag.sgml
index 2b112932089..e5a5947ef28 100644
--- a/doc/src/sgml/manage-ag.sgml
+++ b/doc/src/sgml/manage-ag.sgml
@@ -44,7 +44,7 @@
connection level. If one <productname>PostgreSQL</> server
instance is to house projects or users that should be separate and
for the most part unaware of each other, it is therefore
- recommendable to put them into separate databases. If the projects
+ recommended to put them into separate databases. If the projects
or users are interrelated and should be able to use each other's
resources, they should be put in the same database but possibly
into separate schemas. Schemas are a purely logical structure and who can
diff --git a/doc/src/sgml/passwordcheck.sgml b/doc/src/sgml/passwordcheck.sgml
index 0050e658247..415749d5424 100644
--- a/doc/src/sgml/passwordcheck.sgml
+++ b/doc/src/sgml/passwordcheck.sgml
@@ -47,7 +47,7 @@
This limits the usefulness of the <filename>passwordcheck</filename>
module, because in that case it can only try to guess the password.
For this reason, <filename>passwordcheck</filename> is not
- recommendable if your security requirements are high.
+ recommended if your security requirements are high.
It is more secure to use an external authentication method such as Kerberos
(see <xref linkend="client-authentication">) than to rely on
passwords within the database.
diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml
index 2d9531f08d0..e34dfc0c5ae 100644
--- a/doc/src/sgml/queries.sgml
+++ b/doc/src/sgml/queries.sgml
@@ -1099,7 +1099,7 @@ SELECT product_id, p.name, (sum(s.units) * (p.price - p.cost)) AS profit
Currently, window functions always require presorted data, and so the
query output will be ordered according to one or another of the window
functions' <literal>PARTITION BY</>/<literal>ORDER BY</> clauses.
- It is not recommendable to rely on this, however. Use an explicit
+ It is not recommended to rely on this, however. Use an explicit
top-level <literal>ORDER BY</> clause if you want to be sure the
results are sorted in a particular way.
</para>
--
GitLab