From 2019e24dd8093a36331a4fe02c1ac8943bdc0c23 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sat, 22 Jul 2000 04:45:10 +0000 Subject: [PATCH] spell cleanups --- doc/src/sgml/ref/pg_dump.sgml | 4 ++-- doc/src/sgml/ref/postgres-ref.sgml | 4 ++-- doc/src/sgml/ref/psql-ref.sgml | 18 +++++++++--------- doc/src/sgml/ref/reindex.sgml | 12 ++++++------ 4 files changed, 19 insertions(+), 19 deletions(-) diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 354ac158a0..ac853761c2 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,5 +1,5 @@ @@ -367,7 +367,7 @@ dumpSequence(table): SELECT failed When doing a data only dump, pg_dump emits queries to disable triggers on user tables before inserting the data and queries to - reenable them after the data has been inserted. If the restore is stopped + re-enable them after the data has been inserted. If the restore is stopped in the middle, the system catalogs may be left in the wrong state. diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index c07ec0a5e6..7650ddd945 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -1,5 +1,5 @@ @@ -65,7 +65,7 @@ postgres [ -B nBuffers ] [ -C ] [ - is the number of shared-memory buffers that the postmaster has allocated for the backend server processes that it starts. If the - backend is running standalone, this specifies the number of buffers to + backend is running stand-alone, this specifies the number of buffers to allocate. This value defaults to 64 buffers, where each buffer is 8k bytes (or whatever BLCKSZ is set to in config.h). diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index d1f554be25..fccc7ef5c6 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -1,5 +1,5 @@ @@ -1645,7 +1645,7 @@ bar DBNAME - The name of the database you are currently connected to. This is set everytime + The name of the database you are currently connected to. This is set every time you connect to a database (including program startup), but can be unset. @@ -1727,7 +1727,7 @@ bar HOST - The database server host you are currently connected to. This is set everytime + The database server host you are currently connected to. This is set every time you connect to a database (including program startup), but can be unset. @@ -1755,7 +1755,7 @@ bar The value of the last affected oid, as returned from an INSERT - or lo_insert commmand. This variable is only guaranteed to be + or lo_insert command. This variable is only guaranteed to be valid until after the result of the next SQL command has been displayed. @@ -1799,7 +1799,7 @@ bar By default, if non-interactive scripts encounter an error, such as a malformed SQL query or internal meta-command, - processing continues. This has been the traditional behaviour of + processing continues. This has been the traditional behavior of psql but it is sometimes not desirable. If this variable is set, script processing will immediately terminate. If the script was called from another script it will terminate in the same fashion. @@ -2023,7 +2023,7 @@ testdb=> \set content `sed -e "s/'/\\\\\\'/g" < my_file.txt`digits starts with 0x the rest of the characters are interpreted at a hexadecimal digit and the character with the corresponding code is - subsituted. If the first digit is 0 the characters are + substituted. If the first digit is 0 the characters are interpreted as on octal number and the corresponding character is substituted. Otherwise a decimal number is assumed. @@ -2184,7 +2184,7 @@ peter@localhost testdb=> SELECT * FROM my_table; (4 rows) - Notice how the int4 colums in right aligned while the text column in left aligned. + Notice how the int4 columns in right aligned while the text column in left aligned. You can make this table look differently by using the \pset command: @@ -2279,7 +2279,7 @@ Field separator is "oo". - psql only works smootly with servers of the + psql only works smoothly with servers of the same version. That does not mean other combinations will fail outright, but subtle and not-so-subtle problems might come up. @@ -2288,7 +2288,7 @@ Field separator is "oo". Pressing Control-C during a copy in (data sent to the - server) doesn't show the most ideal of behaviours. If you get a message + server) doesn't show the most ideal of behaviors. If you get a message such as PQexec: you gotta get out of a COPY state yourself, simply reset the connection by entering \c - -. diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml index 22bd5ed6a0..51c4e77c1e 100644 --- a/doc/src/sgml/ref/reindex.sgml +++ b/doc/src/sgml/ref/reindex.sgml @@ -1,5 +1,5 @@ @@ -15,7 +15,7 @@ Postgres documentation REINDEX - Recover corrupted system indexes under standalone Postgres + Recover corrupted system indexes under stand-alone Postgres @@ -40,7 +40,7 @@ REINDEX { TABLE | DATABASE | INDEX } nameTABLE - Recreate all indexes of a specfied table. + Recreate all indexes of a specified table. @@ -48,7 +48,7 @@ REINDEX { TABLE | DATABASE | INDEX } nameDATABASE - Recreate all system indexes of a specfied database. + Recreate all system indexes of a specified database. @@ -56,7 +56,7 @@ REINDEX { TABLE | DATABASE | INDEX } nameINDEX - Recreate a specfied index. + Recreate a specified index. @@ -116,7 +116,7 @@ REINDEX REINDEX is used to recover corrupted system indexes. In order to run REINDEX command,Postmaster must be shutdown and - standalone Postgres should be started instead with options -O and + stand-alone Postgres should be started instead with options -O and -P(an option to ignore system indexes). Note that we couldn't rely on system indexes for the recovery of system indexes.