In Expected Results I also put any graphical updates the product did to the screen (font color change, etc.)

Whether it's "Notes" or somewhere else I put the reasoning behind the logic. As Ralph van Roosmalen writes in his blog http://softwaredevelopmentisfun.blogspot.com/2011/05/things-tester-can-learn-from-programmer.html:

"A good programmer writes why-do-we-do-this comments. For example in the above code, he describes why a should be less than 1 and why he raises an exception. As tester always try to write why-do-we-do-this comments, in your test scripts and in your automated test scripts. How you test, that is clear, describe why you are testing the software."