From e1623c3959aac707732d7a6ad09adfb5751763b3 Mon Sep 17 00:00:00 2001 From: Greg Stark Date: Fri, 3 Jun 2016 15:13:36 +0100 Subject: Fix various common mispellings. Mostly these are just comments but there are a few in documentation and a handful in code and tests. Hopefully this doesn't cause too much unnecessary pain for backpatching. I relented from some of the most common like "thru" for that reason. The rest don't seem numerous enough to cause problems. Thanks to Kevin Lyda's tool https://pypi.python.org/pypi/misspellings --- doc/src/sgml/config.sgml | 2 +- doc/src/sgml/pgcrypto.sgml | 2 +- doc/src/sgml/ref/psql-ref.sgml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 72b5920aba1..94e183b9c3e 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -2518,7 +2518,7 @@ include_dir 'conf.d' less than wal_writer_flush_after bytes of WAL have been produced since, WAL is only written to the OS, not flushed to disk. If wal_writer_flush_after is set to 0 WAL is - flushed everytime the WAL writer has written WAL. The default is + flushed every time the WAL writer has written WAL. The default is 1MB. This parameter can only be set in the postgresql.conf file or on the server command line. diff --git a/doc/src/sgml/pgcrypto.sgml b/doc/src/sgml/pgcrypto.sgml index a3b987a4c4e..5f8bbf9f4ec 100644 --- a/doc/src/sgml/pgcrypto.sgml +++ b/doc/src/sgml/pgcrypto.sgml @@ -866,7 +866,7 @@ Applies to: pgp_sym_encrypt be a value between 1024 and 65011712, inclusive. -Default: A random value bewteen 65536 and 253952 +Default: A random value between 65536 and 253952 Applies to: pgp_sym_encrypt, only with s2k-mode=3 diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index df79a3733fa..06803ab89ca 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -4168,7 +4168,7 @@ testdb=> \crosstabview first second This second example shows a multiplication table with rows sorted in reverse -numerical order and columns with an independant, ascending numerical order. +numerical order and columns with an independent, ascending numerical order. testdb=> SELECT t1.first as "A", t2.first+100 AS "B", t1.first*(t2.first+100) as "AxB", testdb(> row_number() over(order by t2.first) AS ord -- cgit v1.2.3