Matt Sawyer pointed us towards these typos/errors (CS 9 / CS 10 docs):

1 -----
A.1.14. -> Example A.13 (Admin guide)

is incorrect for the input line
The input.i3.class_id= is blank, and the input.i3.name= is duplicated
input.i3.name=subjectAltNameExtInputImplsubjectAltNameExtInputImpl

as seen in other sections, it should be:
input.i3.class_id=subjectAltNameExtInputImpl
input.i3.name=subjectAltNameExtInputImpl

2 -----
B.1.23 -> Example B.1 (Admin Guide)

$request.requester_email$ <- this is incorrect, and should be $request.requestor_email$

This variable does not exist, and the mis-match can definitely cause issues.
-> s/requester/requestor/

-> 3 wrong occurrences, other mentions are correct.

3 -----
13.2.3.9.2. Changing the DER-Encoding Order (Planning and Installation Guide)

In here, `Printable` is listed as an option, but if you input `Printable` it posts a DER validation java stack dump. The only valid option is `PrintableString`,

Additionally, extra space in examples:
X500Name.directoryStringEncodingOrder=PrintableString, UniversalString

"This however lead me down a rabbit hole that may also ultimately require some documentation updates. The DISA team has several CS customizations, many of which are based around custom input classes. I've been looking at these a bit more closely recently, and I think it would be relatively easy to submit these as PR's to expand the existing profile input configurations. Which would ultimately mean documenting each of the new features that are added. This will likely take a while to get started going through the wickets, but I thought passing that information along might be helpful.

Side-note, I believe it would be beneficial to list how each of the attributes is referenced in appendix A. For example, the Submitter Information Input states that it accepts the Requester Name/email/phone, but it does not reference the variables those inputs provide. Appendix B denotes many of them, but there's no direct assocation between the input class ID and the variables that are available for reference. I believe that information would be extremely valuable."