...Oh right, there’s a reason we made a new flavor text field.  The span class was being used for scams too often, and we got really tired of it.

By the way, you put your flavor text in the admin field. And that was a COV.

CoV   per Rodlen.

Hopping on the bandwagon.

Rodlen: Why does this allow for scams using the span class?

The first part strikes me as a little ambiguous.  “the enacting admin may ignore such errors.”  Define “ignore”. 

for reasons stated above, and because it was very annoying having to go look up in the Ruleset where these amendments were to take place (seriously, “after the second occurrence of [word]”?)

Anyway, what difference does it make if an admin ignores a typo?  Besides the literal changing of the state of a Proposal to “Enacted”, admins don’t change the gamestate upon enactment of a proposal.  The Ruleset changes the Gamestate, and the admin updates documents to reflect this change.

CoV for speed

I assume the scam is that you can put the flavour text span class around some words, but also add further CSS styling to make it look like normal text - when the proposal enacts, those words vanish.

I’ve recently removed the “flavour text” button from the edit interface, as it was obsolete, so there’s no reason why anyone would be using the flavour text span class.