From 5c1b2f5daa678b94861ab29ccc0252e4f2eb40ff Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 16 Aug 2012 11:26:40 -0400
Subject: [PATCH] Revert: In docs, change a few cases of "not important" to
"unimportant".
Per request from Heikki
---
doc/src/sgml/advanced.sgml | 4 ++--
doc/src/sgml/ltree.sgml | 2 +-
doc/src/sgml/syntax.sgml | 2 +-
doc/src/sgml/tablefunc.sgml | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advanced.sgml
index 06d3a737c5f..218988e0afc 100644
--- a/doc/src/sgml/advanced.sgml
+++ b/doc/src/sgml/advanced.sgml
@@ -173,7 +173,7 @@ UPDATE branches SET balance = balance + 100.00
</para>
<para>
- The details of these commands are unimportant here; the important
+ The details of these commands are not important here; the important
point is that there are several separate updates involved to accomplish
this rather simple operation. Our bank's officers will want to be
assured that either all these updates happen, or none of them happen.
@@ -428,7 +428,7 @@ SELECT depname, empno, salary, rank() OVER (PARTITION BY depname ORDER BY salary
<para>
We already saw that <literal>ORDER BY</> can be omitted if the ordering
- of rows is unimportant. It is also possible to omit <literal>PARTITION
+ of rows is not important. It is also possible to omit <literal>PARTITION
BY</>, in which case there is just one partition containing all the rows.
</para>
diff --git a/doc/src/sgml/ltree.sgml b/doc/src/sgml/ltree.sgml
index 7f127ac49cf..06b262bccb8 100644
--- a/doc/src/sgml/ltree.sgml
+++ b/doc/src/sgml/ltree.sgml
@@ -160,7 +160,7 @@ Europe & Russia*@ & !Transportation
This will match paths that contain the label <literal>Europe</literal> and
any label beginning with <literal>Russia</literal> (case-insensitive),
but not paths containing the label <literal>Transportation</literal>.
- The location of these words within the path is unimportant.
+ The location of these words within the path is not important.
Also, when <literal>%</> is used, the word can be matched to any
underscore-separated word within a label, regardless of position.
</para>
diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml
index f496fa88004..a01f9b5fc4e 100644
--- a/doc/src/sgml/syntax.sgml
+++ b/doc/src/sgml/syntax.sgml
@@ -2375,7 +2375,7 @@ LANGUAGE SQL IMMUTABLE STRICT;
<literal>b</literal> inputs will be concatenated, and forced to either
upper or lower case depending on the <literal>uppercase</literal>
parameter. The remaining details of this function
- definition are unimportant here (see <xref linkend="extend"> for
+ definition are not important here (see <xref linkend="extend"> for
more information).
</para>
diff --git a/doc/src/sgml/tablefunc.sgml b/doc/src/sgml/tablefunc.sgml
index 520886b811b..cfa20e2a70c 100644
--- a/doc/src/sgml/tablefunc.sgml
+++ b/doc/src/sgml/tablefunc.sgml
@@ -516,7 +516,7 @@ row_name extra cat1 cat2 cat3 cat4
In practice the <parameter>source_sql</parameter> query should always
specify <literal>ORDER BY 1</> to ensure that values with the same
<structfield>row_name</structfield> are brought together. However,
- ordering of the categories within a group is unimportant.
+ ordering of the categories within a group is not important.
Also, it is essential to be sure that the order of the
<parameter>category_sql</parameter> query's output matches the specified
output column order.
--
GitLab