diff --git a/OSBindings/Mac/Clock SignalTests/68000 Comparative Tests/eor_andi_ori.json b/OSBindings/Mac/Clock SignalTests/68000 Comparative Tests/eor_and_or.json
similarity index 100%
rename from OSBindings/Mac/Clock SignalTests/68000 Comparative Tests/eor_andi_ori.json
rename to OSBindings/Mac/Clock SignalTests/68000 Comparative Tests/eor_and_or.json
diff --git a/OSBindings/Mac/Clock SignalTests/68000 Comparative Tests/readme.md b/OSBindings/Mac/Clock SignalTests/68000 Comparative Tests/readme.md
index 039774d7d..430da440a 100644
--- a/OSBindings/Mac/Clock SignalTests/68000 Comparative Tests/readme.md	
+++ b/OSBindings/Mac/Clock SignalTests/68000 Comparative Tests/readme.md	
@@ -29,3 +29,12 @@ I follow every generated opcode with three words of mostly-random data; this dat
 Similarly, all initial register contents are random except that the lowest bit is never set, just in case any of them is used to calculate an address for a word or longword.
 
 So the output is very scattergun approach, with a lot of redundancy. 
+
+## Questionable Results
+
+I am presently unconvinced by the results for:
+
+* the N flag on many of the [A/S/N]BCD results, as these often seem to conflict with Bart Trzynadlowski's 68knotes.txt; and
+* the alleged results of A7-relative JSR, for which the emulator I was testing against appears to have computed a target address for the value of A7 after pushing the existing PC to the stack, which is unlikely because the first of that instruction's program fetches occurs before any stack activity.  
+
+This emulator seems not yet to generate values for the undocumented flags of DIVU and DIVS that match those listed here, but that's through lack of documentation. The objective here is to test my implementation of behaviour I am able to find descriptions of against other people's implementations of that same behaviour, to flush out errors in my comprehension and implementation.