End-of-line hyphens must be merged with the following word. If a hyphen is only used for syllabification it should be replaced with "".
A problem with is that it is frequently miss-implemented by devices, resulting in a rendering of a hard-hyphen on the display when that hyphen should have been suppressed on rendering except when it is EOL. Thus in practice the recommendation is that not be used. Reader devices are starting to implement auto-hyphenation at rendering time without the requirement of , which is probably a step in the right direction, although these efforts seem pretty rudimentary at this time. The hyphenation problem is greatly compounded by PG and DP's requirements on using non-typographical rules on hard hyphenation and m-dashes, resulting in non-breakable strings of chars 30-40 chars long, almost guaranteeing ugly display rendering.
12. the table-of-contents must be the second section.
A requirement to place TOC at a specific location would clearly seem to be an error. If original author/pub chose to place TOC in an "unusual" location still it would seem sensible to retain that location. Conversely, if the original author/pub chose NOT to implement a TOC but the PG volunteer transcriber feels a dying need to implement a TOC in spite of the original author's intent, then the logical place to put the TOC would seem to be at the very beginning of the transcription, prior to the actual transcription, where the transcriber can make it clear that the TOC has been added by the transcriber for the convenience of readers trying to navigate the transcription on electronic devices, and that such a TOC *does not* in fact represent part of the work being transcribed. The transcriber can also highlight this fact by implementing the TOC in a non-matching choice of font.