Rules on using Special Lexical elements in Requirements

There are constructs in the English language that don't work well in requirements. These constructs are named Special Lexical elements in rCoach One.

Special characters

The Semicolon rule checks for the special character ";" in requirements.
The Question mark rule checks for the special character "?" in requirements.
The Exclamation mark rule checks for the special character "!" in requirements.
The Parenthesis rule checks for the special characters "(" and ")" in requirements.
The Square brackets rule checks for the special characters "[" and "]" in requirements.
The Braces rule checks for the special characters "{" and "}" in requirements.
The En dash rule checks for the special character "-" in requirements.
The Em dash rule checks for the special character "--" in requirements.
The Ellipsis rule checks for the special character "..." in requirements.
The Double quotation rule checks for the special character """ in requirements.
The Single quotation rule checks for the special character "'" in requirements.

The etc. rule checks for the special expression "etc." in requirements.
The [and] so forth rule checks for the special expressions "and so forth" and "so forth" in requirements.
The [and] so on rule checks for the special expression "and so on" and "so on" in requirements.
The i.e. or ie rule checks for the special expressions "i.e." and "ie" in requirements.
The e.g. rule checks for the special expressions "e.g." and "eg" in requirements.
The for example rule checks for the special expression "for example" in requirements.
The at least rule checks for the special expression "at least" in requirements.
The T.B.C. rule checks for the special expressions "T.B.C." or "TBC" (To Be Confirmed) in requirements.
The T.B.S. rule checks for the special expressions "T.B.S." or "TBS" (To Be Specified) in requirements.
The T.B.D. rule checks for the special expressions "T.B.D." or "TBD" (To Be Defined) in requirements.