Misc suggestions for section 2.7 - 2.10 about polygen-docs HOT 3 CLOSED

We can remove some of the punctuation signs by using dashes in place of commas, so we at least don't require to concatenate them to the preceding word

The problem is that we'd be replacing the commas with the minus sign - and not a real em-dash —, which would be a punctuation error. And I'm not sure how Polygen handles em-dashes in source files, due to the char (151) being outside the ASCII range, which makes it problematic if the source file is being encoded as UTF-8 (for it would be represented by a two code points sequence). If we stick to plain ASCII characters we avoid presenting the reader with examples that could lead to encoding problems (specially with beginners).

Unfortunately, in many modern editors and IDEs it's quite hard to work with ASCII/ISO-8859-1 encoding, for they easily break it and switch to UTF-8 if you paste some contents from an UTF-8 document (instead of converting the clipboard to ISO-8859-1). So, I suggest keeping the commas to avoid similar issues.

from polygen-docs.

In the following sentence, the order of words can be altered for a more natural flow:

To avoid writing each and every variation of a sequence in which some atoms swap positions, you can enclose within curly brackets { and } the subproductions that need to be permutated.

To avoid writing each and every variation of a sequence in which some atoms swap positions, you can enclose the subproductions that need to be permutated within curly brackets { and }.

Although the latter flows slightly better it introduces some semantic ambiguity, which causes some degree of strain on the reader to resolve it.

from polygen-docs.

The commas problem in §2.7, mentioned by @RBastianini, also affects the Italian document; so I've created an issue for it: #37

from polygen-docs.