Topic as implicit method invocant under-documented about doc HOT 1 OPEN

I'm not a great fan of adding tutorial-ish stuff to type/ pages; I think those pages are meant to be references of very specific things, like here the Method type, not "methods" as a broader concept.

With language/syntax, I'm not sure what you'd like to see. It points to the class tutorial at an appropriate place, in my opinion. If you'd like to see more, please give further hints...
By the way, there is a problem there:

When declared within a class, a subroutine is named "method"

This is utterly wrong. One can declare subroutines inside of classes, moreover I think one can even declare methods outside of classes. This is the reason I don't like arguments like "nobody ever complained so it must be good". For now, I may just open an issue for it because it's not immediately obvious to me how to fix that.

For language/operators, I agree. Perhaps you would be interested in my rework ideas for the operator? In this particular case, I'm not sure what to do. Perhaps the whole concept of "methodop" should go. Some of them can be used as prefix, implying the topic, but not all of them, e.g >>. notoriously cannot be called that way; it will be a syntax error. This could be yet another aspect of operators that could be put into a table, I mean whether they can be used as "prefix", implying the topic variable as the self-object, or not.

from doc.