Minor additions and edits to the v2.16 Release Notes

Add: notes on New configuration option to ignore self approval on label
Add: notes on CodeMirror plugin for PolyGerrit
Add: additional notes on Migration to NoteDb
Various formatting and style changes

Change-Id: Ib46cbf058f5ae3f1a5f05dd0ef5578c18be91e5e
diff --git a/pages/site/releases/2.16.md b/pages/site/releases/2.16.md
index 3cb8d4d..dc0661a 100644
--- a/pages/site/releases/2.16.md
+++ b/pages/site/releases/2.16.md
@@ -1,20 +1,18 @@
 ---
-title: "Gerrit 2.16 Release (RC1)"
+title: "Gerrit 2.16 Release (RC3)"
 permalink: 2.16.html
 hide_sidebar: true
 hide_navtoggle: true
 toc: true
 ---
 
-Download: **[2.16-rc1](https://gerrit-releases.storage.googleapis.com/gerrit-2.16-rc1.war)**
+Download: **[2.16-rc3](https://gerrit-releases.storage.googleapis.com/gerrit-2.16-rc3.war)**
 
-Documentation: **[2.16-rc1](https://gerrit-documentation.storage.googleapis.com/Documentation/2.16/index.html)**
+Documentation: **[2.16-rc3](https://gerrit-documentation.storage.googleapis.com/Documentation/2.16/index.html)**
 
 ## Release Highlights
 
-* GWT UI is deprecated
-
-* PolyGerrit is now the default UI
+* GWT UI is deprecated, and PolyGerrit is now the default UI.
 
 * Experimental Dark Mode in PolyGerrit.
 
@@ -22,16 +20,27 @@
 
 * Redesigned UI for PolyGerrit based on material design.
 
+* New configuration option to ignore self approval on labels.
+
 * New CommonMark/Markdown parser.
 
 ## Important Notes
 
+[NoteDb](https://gerrit-documentation.storage.googleapis.com/Documentation/2.16/note-db.html)
+is now required for accounts (since 2.15) and groups (since 2.16), and is the preferred storage for changes.
+
+When upgrading to Gerrit v2.16, you are strongly advised to migrate fully (including changes) from ReviewDb to NoteDb.
+
+Although ReviewDb is still technically available on Gerrit v2.16, the upgrade to NoteDb is strongly recommended, although not enforced.
+
+Note that in the next version of Gerrit (v3.0), ReviewDb will not be available.
+
 ### Schema Changes
 
 This release contains schema changes. To upgrade:
 
 ``` sh
-  java -jar gerrit.war init -d site_path
+  java -jar gerrit.war init -d ${site_path}
 ```
 
 ### New logging framework
@@ -57,7 +66,7 @@
 
 SLF4J can still be used by plugins, but using SLF4J in plugins is deprecated and
 with the next Gerrit release SLF4J will no longer be exported as part of the
-Gerrit plugin API jar. This means from the next release on plugins must either
+Gerrit plugin API jar. This means from the next release onwards, plugins must either
 migrate to Flogger or have an own dependency on SLF4J.
 
 ### Reindex for new projects index and changed group index
@@ -67,37 +76,37 @@
 Gerrit:
 
 ``` sh
-  java -jar gerrit.war reindex --index projects -d site_path
+  java -jar gerrit.war reindex --index projects -d ${site_path}
 ```
 
-The group index got two new fields upon which Gerrit 2.16 depends. For this
+The group index gained two new fields, which Gerrit 2.16 depends on. For this
 reason, the following command to offline reindex the group index must be
 executed as well:
 
 ``` sh
-  java -jar gerrit.war reindex --index groups -d site_path
+  java -jar gerrit.war reindex --index groups -d ${site_path}
 ```
 
 The offline reindex for groups should also be run on Gerrit slave hosts.
 
-Note that it is not necessary to reindex the changes and accounts indexes
+Note that if you are migrating from v2.15, it is not necessary to reindex the changes and accounts indexes
 offline. These will automatically be reindexed by the online reindexer after
-starting Gerrit, assuming you were migrating from v2.15.
+starting Gerrit.
 
 ### Migration to NoteDb
 
-NoteDb is the preferred storage for changes and you are strongly advised to
-migrate changes from ReviewDb when upgrading to Gerrit v2.16 from either v2.14
-or v2.15.
-
-See more information about the migration process to NoteDb in the Gerrit Documentation:
+You should review the documentation on [NoteDb](https://gerrit-documentation.storage.googleapis.com/Documentation/2.16/note-db.html),
+including the information about the migration process to NoteDb:
 
 - [On-line migration](https://gerrit-review.googlesource.com/Documentation/note-db.html#online-migration)
 - [Off-line migration](https://gerrit-review.googlesource.com/Documentation/note-db.html#offline-migration)
 
-**NOTE: ReviewDb is still technically available on Gerrit v2.16**.
-However, upgrade to NoteDb is strongly recommended, although not enforced during migration.
-The next version of Gerrit (v3.0) won't support ReviewDb anymore.
+In Gerrit 2.15:
+* Account data (with the exception of Group data) was moved to NoteDB ([release notes](https://www.gerritcodereview.com/2.15.html#notedb-for-accounts)).
+* Change data could be either moved to NoteDB ([migration process](https://gerrit-documentation.storage.googleapis.com/Documentation/2.15/note-db.html#migration)), or left in ReviewDB.
+
+In Gerrit 2.16:
+* Group data is always moved to NoteDB (it is migrated automatically during the upgrade process, when you run `gerrit.war init`).
 
 ### Support for GWT UI is deprecated
 
@@ -145,6 +154,26 @@
 
 ### REST API
 
+There are several new REST endpoints and additions to existing endpoints, as described in the [REST API](https://gerrit-documentation.storage.googleapis.com/Documentation/2.16/rest-api.html) documentation.
+
+### New configuration option to ignore self approval on labels
+
+A new option for Review Labels,
+[label.<Label-Name>.ignoreSelfApproval](https://gerrit-documentation.storage.googleapis.com/Documentation/2.16/config-labels.html#label_ignoreSelfApproval),
+is available.
+
+If true, the label may be voted on by the uploader of the latest patch set, but their approval does not make a change submittable. Instead, a non-uploader who has the right to vote has to approve the change.
+
+It defaults to `false`, but one possible use case is to set the value to `true` for the `Code-Review` label in the `All-Projects` project.
+That value will then be inherited by all projects that do not override the `Code-Review` label settings.
+
+### CodeMirror plugin for PolyGerrit
+
+A new core plugin, `codemirror-editor`, is available,
+which uses [CodeMirror](https://codemirror.net/) to provide a rich code editing experience in PolyGerrit.
+
+When you upgrade Gerrit using `init -d`, you are given the option to install the `codemirror-editor` plugin.
+
 ### Request Tracing
 
 Tracing can now be enabled for single requests. If a request is traced a unique