Skip to content

Commit f3ad615

Browse files
tglsfdctglsfdc
committed
Fix a batch of speling misteaks identified by Peter's spell-checker tool.
1 parent 3438065 commit f3ad615

18 files changed

+54
-53
lines changed

‎doc/src/sgml/datetime.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.35 2003/09/11 16:22:42 momjian Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.36 2003/09/20 20:12:04 tgl Exp $
33
-->
44

55
<appendix id="datetime-appendix">
@@ -570,7 +570,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.35 2003/09/11 16:22:42 mo
570570
<row>
571571
<entry>AFT</entry>
572572
<entry>+04:30</entry>
573-
<entry>Afganistan Time</entry>
573+
<entry>Afghanistan Time</entry>
574574
</row>
575575
<row>
576576
<entry>EAST</entry>

‎doc/src/sgml/ecpg.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.51 2003/09/11 21:42:19 momjian Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.52 2003/09/20 20:12:04 tgl Exp $
33
-->
44

55
<chapter id="ecpg">
@@ -992,7 +992,7 @@ EXEC SQL WHENEVER SQLERROR STOP;
992992
different action was set for the same condition between the first
993993
<literal>EXEC SQL WHENEVER</literal> and the SQL statement causing
994994
the condition, regardless of the flow of control in the C program.
995-
So neither of the two following C program exerpts will have the
995+
So neither of the two following C program excerpts will have the
996996
desired effect.
997997
<programlisting>
998998
/*
@@ -1072,7 +1072,7 @@ struct
10721072
If no error occurred in the last <acronym>SQL</acronym> statement,
10731073
<literal>sqlca.sqlcode</literal> will be 0 and
10741074
<literal>sqlca.sqlstate</literal> will be
1075-
<literal>"00000"</literal>. If a warning or error occured, then
1075+
<literal>"00000"</literal>. If a warning or error occurred, then
10761076
<literal>sqlca.sqlcode</literal> will be negative and
10771077
<literal>sqlca.sqlstate</literal> will be different from
10781078
<literal>"00000"</literal>. A positive

‎doc/src/sgml/features.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.19 2003/09/11 21:42:19 momjian Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.20 2003/09/20 20:12:04 tgl Exp $
33
-->
44

55
<appendix id="features">
@@ -17,12 +17,12 @@ $Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.19 2003/09/11 21:42:19 mo
1717
The formal name of the SQL standard is ISO/IEC 9075 <quote>Database
1818
Language SQL</quote>. A revised version of the standard is released
1919
from time to time; the most recent one appearing in 1999. That
20-
version is refered to as ISO/IEC 9075:1999, or informally as SQL99.
20+
version is referred to as ISO/IEC 9075:1999, or informally as SQL99.
2121
The version prior to that was SQL92.
2222
<productname>PostgreSQL</productname> development tends to aim for
2323
conformance with the latest official version of the standard where
2424
such conformance does not contradict traditional features or common
25-
sense. At the time of this writing, ballotting is under way for a
25+
sense. At the time of this writing, balloting is under way for a
2626
new revision of the standard, which, if approved, will eventually
2727
become the conformance target for future
2828
<productname>PostgreSQL</productname> development.

‎doc/src/sgml/func.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.174 2003/09/13 00:19:43 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.175 2003/09/20 20:12:04 tgl Exp $
33
PostgreSQL documentation
44
-->
55

@@ -469,7 +469,7 @@ PostgreSQL documentation
469469

470470
<row>
471471
<entry> <literal>&lt;&lt;</literal> </entry>
472-
<entry>biwise shift left</entry>
472+
<entry>bitwise shift left</entry>
473473
<entry><literal>1 &lt;&lt; 4</literal></entry>
474474
<entry><literal>16</literal></entry>
475475
</row>

‎doc/src/sgml/information_schema.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/information_schema.sgml,v 1.8 2003/09/11 23:15:51 tgl Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/information_schema.sgml,v 1.9 2003/09/20 20:12:05 tgl Exp $ -->
22

33
<chapter id="information-schema">
44
<title>The Information Schema</title>
@@ -330,7 +330,7 @@
330330
<literal>SELECT</literal>, <literal>INSERT</literal>,
331331
<literal>UPDATE</literal>, <literal>REFERENCES</literal>. If you
332332
want to make your applications fit for possible future
333-
developements, it is generally the right choice to use this view
333+
developments, it is generally the right choice to use this view
334334
instead of <literal>table_privileges</literal> if one of those
335335
privilege types is concerned.
336336
</para>
@@ -1508,7 +1508,7 @@ ORDER BY c.ordinal_position;
15081508
<entry><literal>object_type</literal</entry>
15091509
<entry><type>character_data</type></entry>
15101510
<entry>
1511-
The type of the object that uses the array being descibed: one
1511+
The type of the object that uses the array being described: one
15121512
of <literal>TABLE</literal> (the array is used by a column of
15131513
that table), <literal>DOMAIN</literal> (the array is used by
15141514
that domain), <literal>ROUTINE</literal> (the array is used by
@@ -2424,7 +2424,7 @@ ORDER BY c.ordinal_position;
24242424
objects to a group that the current user is a member of. In
24252425
<productname>PostgreSQL</productname>, this currently only applies
24262426
to domains, and since domains do not have real privileges in
2427-
<productname>PostgreSQL</productname>, this view is empty. Futher
2427+
<productname>PostgreSQL</productname>, this view is empty. Further
24282428
information can be found under <literal>usage_privileges</literal>.
24292429
In the future, this view may contain more useful information.
24302430
</para>

‎doc/src/sgml/jdbc.sgml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.48 2003/08/31 17:32:19 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.49 2003/09/20 20:12:05 tgl Exp $
33
-->
44

55
<chapter id="jdbc">
@@ -262,7 +262,7 @@ jdbc:postgresql://<replaceable class="parameter">host</replaceable>:<replaceable
262262
</listitem>
263263
</itemizedlist>
264264

265-
The parametes have the following meanings:
265+
The parameters have the following meanings:
266266

267267
<variablelist>
268268
<varlistentry>
@@ -397,7 +397,7 @@ st.close();
397397
<title>Getting results based on a cursor</title>
398398

399399
<para>By default the driver collects all the results for the
400-
query at once. This can be inconvieniant for large data sets so
400+
query at once. This can be inconvenient for large data sets so
401401
the JDBC driver provides a means of basing
402402
a <classname>ResultSet</classname> on a database cursor and
403403
only fetching a small number of rows.</para>
@@ -631,7 +631,7 @@ upperProc.close();
631631
as <classname>ResultSet</classname> values.</para>
632632

633633
<example id="get-refcursor-from-function-call">
634-
<title>Gettig <type>refcursor</type> values from a
634+
<title>Getting <type>refcursor</type> values from a
635635
function</title>
636636

637637
<para>When calling a function that returns
@@ -741,7 +741,7 @@ st.close();
741741
that contains a Large Object reference does not delete the Large Object.
742742
Deleting the Large Object is a separate operation that needs to
743743
be performed. Large Objects also have some security
744-
issues since anyone connected to the database cann view
744+
issues since anyone connected to the database can view
745745
and/or modify any Large Object, even if they don't have
746746
permissions to view/update the row containing the Large Object reference.
747747
</para>

‎doc/src/sgml/libpq.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.136 2003/09/11 21:42:20 momjian Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.137 2003/09/20 20:12:05 tgl Exp $
33
-->
44

55
<chapter id="libpq">
@@ -1945,7 +1945,7 @@ It is not thread-safe.
19451945

19461946
<para>
19471947
<function>PQescapeString</function> escapes a string for use within an SQL
1948-
commmand. This is useful when inserting data values as literal constants
1948+
command. This is useful when inserting data values as literal constants
19491949
in SQL commands. Certain characters (such as quotes and backslashes) must
19501950
be escaped to prevent them from being interpreted specially by the SQL parser.
19511951
<function>PQescapeString</> performs this operation.

‎doc/src/sgml/mvcc.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/mvcc.sgml,v 2.37 2003/09/12 22:17:23 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/mvcc.sgml,v 2.38 2003/09/20 20:12:05 tgl Exp $
33
-->
44

55
<chapter id="mvcc">
@@ -661,7 +661,7 @@ ERROR: could not serialize access due to concurrent update
661661
</indexterm>
662662

663663
<para>
664-
The use of explicit locking can increase the likelyhood of
664+
The use of explicit locking can increase the likelihood of
665665
<firstterm>deadlocks</>, wherein two (or more) transactions each
666666
hold locks that the other wants. For example, if transaction 1
667667
acquires an exclusive lock on table A and then tries to acquire

‎doc/src/sgml/protocol.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.44 2003/09/11 21:42:20 momjian Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.45 2003/09/20 20:12:05 tgl Exp $ -->
22

33
<chapter id="protocol">
44
<title>Frontend/Backend Protocol</title>
@@ -238,7 +238,7 @@
238238

239239
<para>
240240
The authentication cycle ends with the server either rejecting the
241-
connection attempt (ErrorResponse), or sending AuthenticationOK.
241+
connection attempt (ErrorResponse), or sending AuthenticationOk.
242242
</para>
243243

244244
<para>
@@ -729,7 +729,7 @@
729729
<command>BEGIN</>/<command>COMMIT</> transaction block (<quote>close</>
730730
meaning to commit if no error, or roll back if error). Then a
731731
ReadyForQuery response is issued. The purpose of Sync is to provide
732-
a resychronization point for error recovery. When an error is detected
732+
a resynchronization point for error recovery. When an error is detected
733733
while processing any extended-query message, the backend issues
734734
ErrorResponse, then reads and discards messages until a Sync is reached,
735735
then issues ReadyForQuery and returns to normal message processing.

‎doc/src/sgml/ref/create_sequence.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.35 2003/09/12 00:12:47 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.36 2003/09/20 20:12:05 tgl Exp $
33
PostgreSQL documentation
44
-->
55

@@ -230,7 +230,7 @@ SELECT * FROM <replaceable>seqname</replaceable>;
230230
<para>
231231
Furthermore, although multiple sessions are guaranteed to allocate
232232
distinct sequence values, the values may be generated out of
233-
sequence when all the sessions are considered. FFor example, with
233+
sequence when all the sessions are considered. For example, with
234234
a <replaceable class="parameter">cache</replaceable> setting of 10,
235235
session A might reserve values 1..10 and return
236236
<function>nextval</function>=1, then session B might reserve values

0 commit comments

Comments
 (0)