Missing preposition 'of'

[PG Doc comments form]

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/11/queries-table-expressions.html
Description:

By the end of section 7.2.1.5, the preposition 'of' is missing:
"(...) we could find out which ones those are like this: (...)"
should read
"(...) we could find out which ones of those are like this: (...)"

Wrong formatting of the word 'executed'

[PG Doc comments form]

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/11/plpgsql-expressions.html
Description:

In section 43.4, in the sentence "(...) and then this prepared statement is
EXECUTEd (...)", the word executed should be modified to lower case.

Re: Missing preposition 'of'

[Tom Lane]

PG Doc comments form  writes:
> By the end of section 7.2.1.5, the preposition 'of' is missing:
> "(...) we could find out which ones those are like this: (...)"
> should read
> "(...) we could find out which ones of those are like this: (...)"

I dunno, the existing wording seems like perfectly good English to
me, while your revision is at best awkward.

regards, tom lane

Re: Wrong formatting of the word 'executed'

[Alvaro Herrera]

On 2019-Jul-25, PG Doc comments form wrote:

> The following documentation comment has been logged on the website:
> 
> Page: https://www.postgresql.org/docs/11/plpgsql-expressions.html
> Description:
> 
> In section 43.4, in the sentence "(...) and then this prepared statement is
> EXECUTEd (...)", the word executed should be modified to lower case.

ISTM that this is intentional, since it refers to the use of the EXECUTE
command.  It does seem maybe too informal to use command names as verbs
and conjugate them ... we don't do it too much, except for "TOASTed".

$ git grep 'e\?d'
doc/src/sgml/gist.sgml:function should return a pointer to newly 
palloc()ed
doc/src/sgml/lobj.sgml:up to 4 TB in size, whereas 
TOASTed fields can be at
doc/src/sgml/lobj.sgml:done efficiently, while most operations on a 
TOASTed
doc/src/sgml/plpgsql.sgml: and then this prepared statement is 
EXECUTEd for each
doc/src/sgml/storage.sgml:called TOASTed 
values work by modifying or
doc/src/sgml/storage.sgml:handle potentially TOASTed input 
values: an input might not
doc/src/sgml/storage.sgml:the value is an ordinary 
un-TOASTed value of the data type, and
doc/src/sgml/storage.sgml:TOASTed values are kept in the 
TOAST table, as
doc/src/sgml/storage.sgml:identifying the particular TOASTed 
value),
doc/src/sgml/storage.sgml:TOASTed value therefore needs to 
store the OID of the
doc/src/sgml/storage.sgml:of TOASTed attributes will only be 
pulled out (if selected at all)
doc/src/sgml/storage.sgml:pages). There was no run time difference compared to 
an un-TOASTed

We do append "s" to make plurals a lot, though.

-- 
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services