I was thinking that every opcode needs a simple (yet functional) example to accompany your documentation.
I'm probably going to start walking down the opcodes and write an example for each.
Plus, I'm going to see if a "unit test" idea will be a natural fit. That will show how the opcode works AND will test the opcodes themselves.

This will also be a way to start demonstrating effective standards for coding tests.
I'll start posting some here so we can discuss and agree before I get too deep in it.
(I might even PM you with some so we don't overly clutter up this thread)

Once you've got an inventory you like of "unit tests" for opcodes/concepts/standards, you could add it to your docs.