Reword the Imperatives rule to say as follows:
;Can, May: “is able to”
;Shall, Must: “is required to”
;Can not, May not, Shall not, Must not: “is forbidden from”
;Should: “is recommended that”. You should not use the imperative “should” in most case.
;Should not: “is not recommend that”. You should not use the imperative “should not” in most case.
The idea of this is since we have made not much progress in the years; this is a “as how we use it” update.
Interestingly, Must and May is not defined in this list, but we keep using it.
The original text is:
===Imperatives===
;Can: “is able to”
;Shall: “is required to”
;Should: “is recommended that”
This defines the inversions as how we use it and add may and must; two commonly seen imperative.
Josh: he/they
This isn’t really an “as how we use it” update at all though, is it? Because it tries to enshrine in the ruleset an instruction that ‘you should not use the imperative “should” in most case’, when ‘should’ is the imperative that we use most often in the ruleset, and for good reason.
No-one is going to get anywhere on reworking imperatives if they do not engage with the question of why ‘should’ is the default choice and why all route-one attempts to shift to alternatives have floundered. It has not developed in that way without a reason; the past twenty years of the game have not occurred in a vacuum, without smart people considering their choices of words. I admit to having given up on fixing this but I don’t believe a fix is impossible - but it does require engaging with the prior work in this area.