API Docs are extremely redundant - possible to streamline?

#1

For example, the Channel page lists every Collection comprehension function (filter, filterIndexed, filterIndexedTo, filterNot, filterNotNull, etc etc)

It makes it very hard to skim the page and immediately see “what makes the Channel class special

Compare to something like Java’s APIs, where all redundant method calls are bucketed under “Methods declared in class X” at the bottom.