FMSLogo Code

Merge the two style guides.
I don't know why there are two of them, but I suspect that I created a second one after forgetting that the first one existed.

Capitalize MAX in the error message in the second example.
This better follows the style guide (all procedure names are capitalized)

Remove the techincal terms "synchronous" and "asynchronous" and instead just describe the behavior.
This makes the manual simpler (easier to read by a non-technical audience)

Separate the description of 0 and 1-127 for a MIDI velocity.
This makes the description clearer, since 0 means "is released" and there's no way to express "how hard" a key is released.

Add more <userinput> tags to the glossary for "contents list".
This makes it clearer what's part of all contents lists and what's part of the specific example given in the glossary.

Change the first sentence of MCI to a fragment, following the convention of the rest of the manual.

Remove the comma before "o" and "y" in an enumeration.
This follows 1.2.1 of the section for «coma» in «Diccionario panhispánico de dudas».

Remove the comma before "o" in an enumeration.
This follows 1.2.1 of the section for «coma» in «Diccionario panhispánico de dudas».

Add tests for TRANSFER

Improve the error code checking in APPLYTEST.BADINPUT