Re: Assorted comment, trace and ok() message spelling fixes.

[Marvin]

Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
https://testbot.winehq.org/JobDetails.pl?Key=22037

Your paranoid android.

=== w1064 (64 bit device) ===
device.c:4317: Test failed: cw is 0xf60, expected 0x7f.
device.c:4326: Test failed: Callback cw is 0xf60, expected 0x7f.

Assorted comment, trace and ok() message spelling fixes.

[Francois Gouget]

On Sun, 10 Apr 2016, Marvin wrote:
[...]
> === w1064 (64 bit device) ===
> device.c:4317: Test failed: cw is 0xf60, expected 0x7f.
> device.c:4326: Test failed: Callback cw is 0xf60, expected 0x7f.

These failures were already there. Here's a run of the 
essentially unmodified d3d9:device test failing in the same way:

https://testbot.winehq.org/JobDetails.pl?Key=22054

(unfortunately we don't have regular Windows 10 WineTest results because 
ntdll:exception crashes the VM)