typo and formatting fixes in cycle notes

This commit is contained in:
James Tauber 2011-08-14 20:36:48 -04:00
parent d7035ca480
commit 8e1b71dbca

View File

@ -4,8 +4,7 @@ There are two ways we could represent cycle information:
page boundary crossing (which seems opcode-specific, oddly)
2. add cycles in individual methods like those accessing memory and the
operations themselves, to be model *why* something takes the cycles it
does.
operations themselves, to model *why* something takes the cycles it does.
I prefer 2 on the grounds of it being more instructive but it assumes that
the way we do things is closely aligned to the way the 6502 is doing them