A receiver isn't a method. It's the "self" instance the method is invoked on. It's standard OOP terminology.
I'm with you regarding marshaling, but not because it's not an industry-standard term, it's just that Go misapplies it. Marshaling historically has referred to describing a remote procedure call and its return value; for example, you call "CreateFoo()" with a "CreateRequest", the latter must be marshaled into a payload that the remote call can read. For a network call this requires serializing the data to bytes using some kind of format, but for a local call it could just be a pointer to a data structure. However, historically people have often mixed the two terms. Python's standard library also misuses "marshal" to refer to serialization.
The history on marshaling goes back further than that. Smalltalk used the word more or less how itβs used in Go. There is definitely an RPC connotation these days though, probably because small talk was based on message passing.
What else are you familiar with? Those are extremely common terms in the object oriented community.