I removed this sentence because I don't think it's accurate.

We have these review criteria:
https://docs.civicrm.org/extensions/lifecycle/#review-criteria

The criteria do say that you can't use PHP overrides. But there are
other interfaces (like BAO functions for example) that are not in the
"supported methods" list but also not prohibited based on the extension
review criteria.

No content edits here. Just a direct copy paste.

Per discussion in documentation channel I think we need to document what methods are considered supported / expected to be stable. The last 4 items in this list have not been previously documented as a supported way to interact with CiviCRM so may be subject to discussion

Redirect Setting+up+your+personal+testing+sandbox+HOWTO to Testing

The purpose of the intro paragraph is to prep the reader to see several
different test types/tools.  So it...  should probably use the word "test"
somewhere.

Fixed typo and added a little extra detail

Update javascript.md

Missing ; and .

Expand definition of "Non-Functional Change". Add examples and counter-examples.

If I disagree with using the "NFC" label, I'd like to be able to quickly
reference a link that explains the rationale and provides examples.

Update codebase.md

Minor tweaks, typos etc

hook_civicrm_alterEntityRefParams: Correct release number for introduction

 Add description for report filter option default_op

Adds new section User Dashboard to docs > framework > region

Fix Typo

"Security Doucmentation" --> "Security Documentation"

ref: https://lab.civicrm.org/documentation/docs/issues/7

CiviVisulise to CiviVisualize + link

Update setting.md

Some more details about creating a settings page for an extension.

best practices for seting PATH

Update setting.md

Update setting.md

standard/review - Consistent order. Use comments for instructions. Emphasize r-run prose.

Three changes here:
 * Sort criteria in the same order across all three templates.
 * For meta-instructions, use the Markdown/HTML comment notation.
 * For `r-run`, we really don't want boilerplate. Remove the boilerplate.

The DEL workflow produces more readable output.

standards/review.md - Add templates. Tweak codes.