chore: Clarify RFD acceptance procedures

This clarifies the procedures around updating the RFD number
in an RFD pull request after approval of an RFD by the
CVE Board.

Signed-off-by: Andrew Lilley Brinker <abrinker@mitre.org>

Author: alilleybrinker

rfds/0000-establishing-the-rfd-process.md

@@ -179,9 +179,9 @@ RFD are:
 - [Open a pull request][gh_pr] from your feature branch to the `develop` branch on the
   CVEProject/cve-schema repository.
 - After the pull request is open, amend the RFD proposal file to link to that
-  Pull Request. Leave the RFD number as `0000`, it will be modified upon
-  acceptance (if accepted) to take the next available integer ID for an RFD.
-  Commit and push that modification to the RFD file.
+  Pull Request. Leave the RFD number as `0000`. Commit and push that
+  modification to the RFD file. If the RFD is accepted, the RFD number will be
+  modified by a QWG Co-Chair to take the next available integer ID for an RFD.
 
 ### What process would RFDs follow after submission?
 
@@ -239,11 +239,19 @@ instance of the RFD to provide a clear historic record.
 
 Accepted RFDs, meaning RFDs which have been advanced to the CVE Board by the
 QWG and which the CVE Board has voted to approve, will be merged into the
-[CVEProject/cve-schema][gh_repo] repository, and a Tracking Issue will then be
-opened on the repository to track progress on implementing the changes proposed
-in the RFD. The changes, as they've in-principle been approved by the CVE Board
-as part of the process of approving the RFD, will not need to be re-reviewed by
-the Board.
+[CVEProject/cve-schema][gh_repo] repository via the following procedure.
+
+Upon acceptance of an RFD, a QWG Co-Chair will add a commit to the RFD's
+Pull Request branch, updating the RFD document's RFD number in both the
+filename prefix and within the header text of the RFD itself to use the
+next-available integer ID. For example, if the most-recently-merged RFD had
+the number #0003, the next RFD to be merged would use the ID #0004.
+
+After this commit is added, the Pull Request for the RFD will be merged by a
+QWG Co-Chair, and a Tracking Issue will then be opened on the repository to
+track progress on implementing the changes proposed in the RFD. The changes,
+as they've in-principle been approved by the CVE Board as part of the process
+of approving the RFD, will not need to be re-reviewed by the Board.
 
 When all implementation of the RFD is complete and has been merged, the
 Tracking Issue will be closed and the changes proposed by the RFD and now