Proposal to improve the content in subsection 8.16.6. "Composite Type Input and Output Syntax"

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/11/rowtypes.html
Description:

1. Replace this:

"...the whitespace will be ignored if the field type is integer, but not if
it is text."

with this:

"...the whitespace will be ignored if the field type is integer, but not if
it is a character data type like text."

----------------------------------------------------------------------------------------------

2. Find this:

"...you can write double quotes around any individual field value. You must
do so if the field value would otherwise confuse..."

Insert this between the two sentences, i.e. after "...any individual field
value." and before "You must do so if...":

<<
Notice that, as previously stated, the value for a field whose data type is
text, varchar, or char starts with the charater that immediately follows the
opening parenthesis or comma deliminator, and ends with the character that
immediately precedes the comma deliminator or closing parenthesis. This
means that when you choose to surround a character value with double quotes,
the opening double quote must immediately follow the starting deliminator
and the closing double quote must immediately precede the closing
deliminator, like this:

'("hello world")'

If you don't follow this rule and write, for example, this:

'( "hello world" )'

then you will not get an error. However, the rules for the outcome are
undefined and you should simply avoid doing this.
>>