doc: update to reflect N-API (#410)

* doc: update to reflect N-API
* squash: accept suggestion

Co-Authored-By: mhdawson <michael_dawson@ca.ibm.com>

Author: mhdawson

README.md

@@ -112,12 +112,19 @@ weeks before being backported. It is possible for a commit to land earlier at
 the discretion of the Release working group and the maintainers of the LTS branches.
 
 Once a release moves into Maintenance mode, only ***critical*** bugs,
-***critical*** security fixes, and documentation updates will be permitted.
+***critical*** security fixes, documentation updates, and updates to ensure
+consistency and usability of the N-API across LTS releases will be permitted.
+Unless a change is ***urgent*** it will be planned into a release once per
+quarter. Such releases will only be made when necessary.
 
 Note that while it is possible that critical security and bug fixes may lead to
 *semver-major* changes landing within an LTS stream, such situations will be
 rare and will land as *semver-minor* bumps in the LTS covered version.
 
+Updates to ensure consistency and usability of the N-API across LTS releases
+are allowed as it is important to ensure that N-API native modules can be used
+across LTS versions in order to support adoption.
+
 All LTS releases will be assigned a codename. A list of expected upcoming
 codenames is available in [CODENAMES.md](./CODENAMES.md).