diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-12-23 11:53:35 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-12-23 11:53:35 -0500 |
| commit | ff33d1456ea098e160cbbc74b332656c06abc2ab (patch) | |
| tree | 06cb35ae1999dc48edb3f412972b93a9b4bf9815 /src/backend/parser/parse_clause.c | |
| parent | 3e6639a465a5702d0aa98fc756b5ab8c7f97cde8 (diff) | |
| download | postgresql-ff33d1456ea098e160cbbc74b332656c06abc2ab.tar.gz postgresql-ff33d1456ea098e160cbbc74b332656c06abc2ab.zip | |
Spellcheck: s/descendent/descendant/g
I got a little annoyed by reading documentation paragraphs containing
both spellings within a few lines of each other. My dictionary says
"descendant" is the preferred spelling, and it's certainly the majority
usage in our tree, so standardize on that.
For one usage in parallel.sgml, I thought it better to rewrite to avoid
the term altogether.
Diffstat (limited to 'src/backend/parser/parse_clause.c')
0 files changed, 0 insertions, 0 deletions