In keeping with the discussions about JIRA, Gitlab, and issue management
(e.g.  https://lab.civicrm.org/infrastructure/ops/issues/817), this change
would revise the "Review Standards".  Instead of specifically requiring
*a JIRA issue* for every PR, it requires *a public explanation* (which can be
provided by JIRA, Gitlab, etc).

Note: This change tries to be the smallest reasonable alteration to the
review criteria that accomodates Gitlab.  However, perhaps we could make it
better -- e.g.  by providing examples of good and bad explanations?

Related: https://github.com/civicrm/civicrm-core/blob/master/.github/PULL_REQUEST_TEMPLATE.md

Update hook_civicrm_alterPaymentProcessorParams.md

Update hook_civicrm_buildForm.md

bootstrap.md: fix typo

A person is not a PHP script.

Minor formatting issues, remove stray backslashes

Add 'MessageTemplate' to possible hook_civicrm_pre objects

Fix typos

CRM-21020 add additional params and example

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.