Imagine you open a Maritime square
and Q could be one of the flags displayed there.
If it is shown first, then it could be mistaken
for one of the prompts that demands you keep waitin’.
That means you have only two seconds to notice
which trips you up easily if you lose focus.
From now on, the first flag is never a Q,
ensuring an undeserved strike won’t ensue.

Fixing the subtle concern on Twitch Plays
where users got strikes in abundant arrays
when tapping one cyclable square while another
with Morse Code or Tap Code was active. Oh brother!

More problems were caused by an earlier change:
On Twitch Plays the module’s behaviour was strange.
But now from one square to the next you can switch.
It will award strikes without nary a hitch!

When Kudosudoku on Twitch Plays was played,
some players were sharply and gravely dismayed
that points weren’t awarded to them as intended.
But now, this occurrence of heartache has ended.

Imagine you tap a new square at a time
when another is active. This isn't a crime!
Yet doing this used to result in a strike,
which, frankly, was not very gentlemanlike.
So therefore, from now on, this act is permitted.
The waiting or cycling square will be submitted.
The only exceptions are Tap Code and Morse,
As those must be entered through timing, of course.

The Cube is alright, but its symbols are phoney;
they’re not a real alphabet. Swap it with Zoni!

Added a visible frame, two by two,
to show that it is, in fact, a Sudoku.
While a panel is open, the hue of the square
is yellow instead of green now. Go compare!

I had the wrong pictures for 3 mahjong flowers!
But fortunately, someone has spider-sense powers
that tingle when errors like this come about.
PeterRed, thank you for pointing this out!

The manual still referenced Listening! Rotten!
I swiftly removed these two lines I’d forgotten.

Quick fix for a programmer’s cardinal sin:
purge debugging code accidentally left in.