Docs: Standardize "cannot" usage in SGML source

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Docs: Standardize "cannot" usage in SGML source
Date: 2025-12-11 10:00:20
Message-ID: CAEoWx2kyiD+7-vUoOYhH=y2Hrmvqyyhm4EhzgKyrxGBXOMWCxw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Hacker,

While reviewing a patch, I happened to notice the PG docs prefer “cannot”
than “can not”.

Under doc/src/sgml, if we count:
```
sgml % grep -r "cannot" . | wc -l
818
```

“Cannot” has 818 occurrences, but “can not” has only 3:
```
sgml % grep -rE "can\s+not" .
./ecpg.sgml: some SQL statement is declared, "database" can not be used
as a cursor
./func/func-aggregate.sgml: The <parameter>key</parameter> can not
be null. If the
./func/func-aggregate.sgml: The <parameter>key</parameter> can not
be null. If the
```

So, maybe we should fix these 3 and keep a consistent usage of “cannot”.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

Attachment Content-Type Size
v1-0001-Docs-Standardize-cannot-usage-in-SGML-source.patch application/octet-stream 2.5 KB

Browse pgsql-hackers by date

  From Date Subject
Next Message Feilong Meng 2025-12-11 10:17:39 Re: Fix uninitialized PruneFreezeResult in pruneheap and vacuumlazy
Previous Message Chao Li 2025-12-11 09:38:40 Re: Report bytes and transactions actually sent downtream