RFR: Section on backporting

[Iris Clark]

On Sat, 20 Nov 2021 02:03:51 GMT, Jesper Wilhelmsson <jwilhelm at openjdk.org> wrote:

> Guidance on backporting.
> Also moved "Backing out a change" to the testing section where I believe it fits better. This section is unchanged.

src/index.md line 1377:

> 1375: If a change causes a regression that can't be fixed within reasonable time the best way to handle the regression can be to back out the change. Backing out means that the inverse (anti-delta) of the change is pushed to effectively undo the change in the repository. There are two parts to this task, how to do the bookkeeping in JBS, and how to do the actual backout in git or mercurial.
> 1376: 
> 1377: The backout is a regular change and will have to go through the standard code review process, but is considered a [trivial](#trivial) change. The rationale is that a backout is usually urgent in nature and the change itself is automatically generated. In areas where two reviewers are normally required, only one additional Reviewer is required for a backout since the person who is performing the backout also will review the change.

Recommend that both instances of "reviewer*" in the final sentence be of the same case.  I would choose upper.

-------------

PR: https://git.openjdk.java.net/guide/pull/66