Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 0525876

Browse files
committed
doc: Various typo/grammar fixes
Errors detected using Topy (https://github.com/intgr/topy), all changes verified by hand and some manual tweaks added. Marti Raudsepp Individual changes backpatched, where applicable, as far as 9.0.
1 parent d5d7d07 commit 0525876

18 files changed

+23
-23
lines changed

doc/src/sgml/datatype.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2321,7 +2321,7 @@ January 8 04:05:06 1999 PST
23212321
<para>
23222322
Time zones, and time-zone conventions, are influenced by
23232323
political decisions, not just earth geometry. Time zones around the
2324-
world became somewhat standardized during the 1900's,
2324+
world became somewhat standardized during the 1900s,
23252325
but continue to be prone to arbitrary changes, particularly with
23262326
respect to daylight-savings rules.
23272327
<productname>PostgreSQL</productname> uses the widely-used

doc/src/sgml/func.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15608,7 +15608,7 @@ SELECT pg_type_is_visible('myschema.widget'::regtype);
1560815608
<parameter>schema</> is the schema name that the object belongs in, or
1560915609
<literal>NULL</> for object types that do not belong to schemas;
1561015610
<parameter>name</> is the name of the object, quoted if necessary, only
15611-
present if it can be used (alongside schema name, if pertinent) as an unique
15611+
present if it can be used (alongside schema name, if pertinent) as a unique
1561215612
identifier of the object, otherwise <literal>NULL</>;
1561315613
<parameter>identity</> is the complete object identity, with the precise format
1561415614
depending on object type, and each part within the format being
@@ -17583,7 +17583,7 @@ FOR EACH ROW EXECUTE PROCEDURE suppress_redundant_updates_trigger();
1758317583
<entry><type>text</type></entry>
1758417584
<entry>
1758517585
Name of the object, if the combination of schema and name can be
17586-
used as an unique identifier for the object; otherwise <literal>NULL</>.
17586+
used as a unique identifier for the object; otherwise <literal>NULL</>.
1758717587
No quoting is applied, and name is never schema-qualified.
1758817588
</entry>
1758917589
</row>

doc/src/sgml/mvcc.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1258,7 +1258,7 @@ UPDATE accounts SET balance = balance - 100.00 WHERE acctnum = 22222;
12581258
correctly. Advisory locks can be useful for locking strategies
12591259
that are an awkward fit for the MVCC model.
12601260
For example, a common use of advisory locks is to emulate pessimistic
1261-
locking strategies typical of so called <quote>flat file</> data
1261+
locking strategies typical of so-called <quote>flat file</> data
12621262
management systems.
12631263
While a flag stored in a table could be used for the same purpose,
12641264
advisory locks are faster, avoid table bloat, and are automatically

doc/src/sgml/pgbench.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -762,7 +762,7 @@ pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</>
762762

763763
<para>
764764
By default, or when <literal>uniform</> is specified, all values in the
765-
range are drawn with equal probability. Specifiying <literal>gaussian</>
765+
range are drawn with equal probability. Specifying <literal>gaussian</>
766766
or <literal>exponential</> options modifies this behavior; each
767767
requires a mandatory threshold which determines the precise shape of the
768768
distribution.
@@ -950,7 +950,7 @@ END;
950950
(useful when multiple scripts were specified with <option>-f</>),
951951
and <replaceable>time_epoch</>/<replaceable>time_us</> are a
952952
UNIX epoch format timestamp and an offset
953-
in microseconds (suitable for creating a ISO 8601
953+
in microseconds (suitable for creating an ISO 8601
954954
timestamp with fractional seconds) showing when
955955
the transaction completed.
956956
</para>

doc/src/sgml/pgcrypto.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -592,7 +592,7 @@ pgp_pub_encrypt_bytea(data bytea, key bytea [, options text ]) returns bytea
592592
</synopsis>
593593
<para>
594594
Encrypt <parameter>data</> with a public PGP key <parameter>key</>.
595-
Giving this function a secret key will produce a error.
595+
Giving this function a secret key will produce an error.
596596
</para>
597597
<para>
598598
The <parameter>options</> parameter can contain option settings,

doc/src/sgml/pltcl.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@
5151
Sometimes it is desirable to write Tcl functions that are not restricted
5252
to safe Tcl. For example, one might want a Tcl function that sends
5353
email. To handle these cases, there is a variant of <application>PL/Tcl</> called <literal>PL/TclU</>
54-
(for untrusted Tcl). This is the exact same language except that a full
54+
(for untrusted Tcl). This is exactly the same language except that a full
5555
Tcl interpreter is used. <emphasis>If <application>PL/TclU</> is used, it must be
5656
installed as an untrusted procedural language</emphasis> so that only
5757
database superusers can create functions in it. The writer of a <application>PL/TclU</>

doc/src/sgml/queries.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2098,7 +2098,7 @@ DELETE FROM parts
20982098
statements in <literal>WITH</>, the order in which the specified updates
20992099
actually happen is unpredictable. All the statements are executed with
21002100
the same <firstterm>snapshot</> (see <xref linkend="mvcc">), so they
2101-
cannot <quote>see</> each others' effects on the target tables. This
2101+
cannot <quote>see</> one another's effects on the target tables. This
21022102
alleviates the effects of the unpredictability of the actual order of row
21032103
updates, and means that <literal>RETURNING</> data is the only way to
21042104
communicate changes between different <literal>WITH</> sub-statements and

doc/src/sgml/ref/alter_tsdictionary.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ ALTER TEXT SEARCH DICTIONARY my_dict ( StopWords = newrussian );
126126
</programlisting>
127127

128128
<para>
129-
The following example command changes the language option to dutch,
129+
The following example command changes the language option to <literal>dutch</>,
130130
and removes the stopword option entirely.
131131
</para>
132132

doc/src/sgml/ref/comment.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -288,7 +288,7 @@ COMMENT ON SERVER myserver IS 'my foreign server';
288288
COMMENT ON TABLE my_schema.my_table IS 'Employee Information';
289289
COMMENT ON TABLESPACE my_tablespace IS 'Tablespace for indexes';
290290
COMMENT ON TEXT SEARCH CONFIGURATION my_config IS 'Special word filtering';
291-
COMMENT ON TEXT SEARCH DICTIONARY swedish IS 'Snowball stemmer for swedish language';
291+
COMMENT ON TEXT SEARCH DICTIONARY swedish IS 'Snowball stemmer for Swedish language';
292292
COMMENT ON TEXT SEARCH PARSER my_parser IS 'Splits text into words';
293293
COMMENT ON TEXT SEARCH TEMPLATE snowball IS 'Snowball stemmer';
294294
COMMENT ON TRIGGER my_trigger ON my_table IS 'Used for RI';

doc/src/sgml/ref/select.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1312,7 +1312,7 @@ KEY SHARE
13121312
is also acquired by any <command>DELETE</> on a row, and also by an
13131313
<command>UPDATE</> that modifies the values on certain columns. Currently,
13141314
the set of columns considered for the <command>UPDATE</> case are those that
1315-
have an unique index on them that can be used in a foreign key (so partial
1315+
have a unique index on them that can be used in a foreign key (so partial
13161316
indexes and expressional indexes are not considered), but this may change
13171317
in the future.
13181318
Also, if an <command>UPDATE</command>, <command>DELETE</command>,

0 commit comments

Comments
 (0)