bug#36618: 26.2; Misnamed `*-hooks' variables

[Drew Adams]

> > A user looking for hooks will fall upon these misleading
> > names of non-hooks using completion (e.g. substring).
> 
> Not necessarily: we have a section in the ELisp manual that lists all
> the standard hooks.

A user looking for hooks is not necessarily looking
for _standard_ hooks, and she is not necessarily
looking for coverage of hooks in the manual.

As one simple example, `C-h v' with various types
of completion (substring is one example, but there
are others) can match such non-hook variables.
Similarly, searches.

Hook naming conventions are documented.  And hook
names have been improved over the years to better
reflect the conventions.  There are a few functions
that mislead by their names.  That misleading is
not needed - it doesn't help anything.