Updated scope: Complete upstream docs review of the Protect a web service by using bearer token authentication upstream guide security-oidc-bearer-token-authentication-tutorial.adoc for Jan 15th.

For Jan 15th, this upstream review includes the following scope:

1. Check the upstream source on main.
   • Run Vale and other helpful content quality checkers. 
   • Fix red errors and orange serious warnings only or legal-risk issues
   • Complete style and language checks. Ensure content is polished and ready for RHBQ publication (process for downstream publication tbc).
   • The review does not include restructuring. If a guide needs restructuring, raise a GitHub issue.
2. Send for peer review by another writer - Peer reviewer to focus on critical issues only like typos or serious quality issues.
3. Send for SME review to Sergey. Sergey to merge once review complete and approvals received.

OUTDATED: For 3.2, this task includes the following scope:

1. Check the downstream source on main. Does it match the latest 3.2 state?
2. Check the current PV2 main state. Is everything rendering OK?
3. Run Vale and other helpful content quality checkers:
   1. Run the latest vale-at-red-hat rules on the single downstream adoc file.
   2. Fix red errors and orange serious warnings only or legal-risk issues. No subjective grammar changes! 
4. Make sure the official product name is correctly used. (Diverge required here)
5. Final peer review (sanity check) by another writer - ONLY critical issues like typo or serious quality issues to be raised by 2nd writer.
6. Final RHBQ-specific SME review if needed (Send the PV2/Jenkins link).
7. Kick off the QE Quarkus task and description, links etc.