One wonders if this is a poorly translated explanation for a little-endian architecture. When accessed as data it comes back big-endian but when accessed as instructions it is interpreted as little-endian?

I could imagine a hack like this where the CPU logic came from one vendor that had the opposite byte order than a previous CPU, and yet one wanted to keep some level of compatibility between them.