Maybe that's not the target audience?
Tutorials targetted at C newbies have been about "C pointers" for eons; why would Go tutorials refer to a different programming language?
What that program is doing would not be well-defined in C; you cannot increment a pointer from the address of one local variable to point to another, without leaving behind the ISO C standard dialect. I haven't seen any compiler-specific document which "blesses" the practice.
If that is well-defined in Go, that would be an excellent reason why the article really is specifically about Go pointers and not C pointers.
Which ANSI C example should I write for you in Go?
This means I could create a perfectly legal implementation of Go where such things result in complete nonsense. I don't think package unsafe "counts".
Or instead of starting with:
"This post is for programmers coming to Go who are unfamiliar with the idea of pointers or a pointer type in Go."
It could start with:
"This post is for programmers coming to Go from a language without pointers or a pointer type."