Common way to describe golang concurrency design?

Go has a powerful concurrency support. With goroutines and channels, the synchronization is implemented in a different way than mutex.

Example: Codewalk: Share Memory By Communicating

However, when comes to describing the design, it seems not quite clear and easy since there may be many goroutines and channels involved, orchestrated.

Does anybody know if there's some common language/format in text or in diagram, to describe such design? (e.g. use above link as example)