In section 3.1, the sentence reads:
When describing data, the uncapitalized terms required and optional in this document have specific formal meanings (introduced in Section 5.3.1,MinOccurs, MaxOccurs) having to do with the way element declarations are annotated in the DFDL language.
There should be a space after "5.3.1,".
This is in the published document, not an artifact of the AsciiDoc conversion. The Word cross-reference uses a REF field with the \r switch, which inserts the paragraph number only, so the field contributes "5.3.1" and stops. Everything from the comma onward is hand-typed text. It renders the same way in the GFD.240 PDF, its HTML export, and the converted build.
In section 3.1, the sentence reads:
There should be a space after "5.3.1,".
This is in the published document, not an artifact of the AsciiDoc conversion. The Word cross-reference uses a REF field with the
\rswitch, which inserts the paragraph number only, so the field contributes "5.3.1" and stops. Everything from the comma onward is hand-typed text. It renders the same way in the GFD.240 PDF, its HTML export, and the converted build.