(1) This is used several times in the readme: "Authorization: Bearer ey..rg". However, it is not explained that the actual token that has been previously generated must be used. Also, in the first command it is eyJ...59g instead of ey..rg which is confusing - is it a different string?
(2) Some lines in readme end with : - What is it? I think either colon or dash should be used.
(3) "The quickstart also contains an endpoint that makes use of the birthdate claim to calculate how long until the callers birthday, this can be called using a token which contains the Subscriber group." - this instruction comes after "If a token is now generated and use without the Subscriber group access to this endpoint should be rejected." - if used with token generated with this command, the subsequent command fails. I suggest either explicitly specify that the token generated by first command should be used or to swap the 2 commands.
(4) "This section has been a fast run through of the commands required to deploy the quickstart, generate JWT tokens and call the various endpoints, for further information as to how this was achieved please read through the next section where the process to generate this quickstart from scratch is described step by step." - this sentence is too long, I suggest splitting it in 2: "This section has been a fast run through of the commands required to deploy the quickstart, generate JWT tokens and call the various endpoints. For further information as to how this was achieved please read through the next section where the process to generate this quickstart from scratch is described step by step."
(6) Consider adding standard sections - see other (non-MP - because these were not yet tested)

• Use of the EAP_HOME and QUICKSTART_HOME Variables
• Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse
• Also consider using standard sections "Build and Deploy the Quickstart" and "Access the Application" instead of "Solution"