Apply changes to review section

Co-authored-by: Daira Emma Hopwood <daira@jacaranda.org>

zip-0000.rst

@@ -220,16 +220,19 @@ Reviewing a ZIP
 ---------------
 
 Any ZIP Editor can suggest changes to a ZIP. These suggestions are the
-opinion of the individual ZIP Editor. ZIP Editors are expected to perform
-independent technical and process review, regardless of contractural or
-any other relationships.
+opinion of the individual ZIP Editor. Any technical or process review that
+ZIP Editors perform is expected to be independent of their contractual or
+other relationships.
+
+ZIP Owners are free to clarify, modify, or decline suggestions from ZIP Editors.
+If the ZIP Editors make a change to a ZIP that the Owner disagrees with, then
+the Editors SHOULD revert the change.
 
-ZIP Owners can clarify, modify, or decline suggestions from ZIP Editors.
 
 Typically, the ZIP Editors suggest changes in two phases:
 - `content review`: multiple ZIP Editors discuss the ZIP, and suggest
   changes to the overall content. This is a "big picture" review.
-- `format review`: one or two ZIP Editors do a detailed review of the
+- `format review`: two ZIP Editors do a detailed review of the
   structure and format of the ZIP. This ensures the ZIP is consistent
   with other Zcash specifications.
 
@@ -239,9 +242,9 @@ among the current Editors.
 
 When a ZIP is ready, the ZIP Editors will:
 
-* Assign a ZIP number in the pull request.
+* Ensure that a unique ZIP number has been assigned in the pull request.
 * Regenerate the corresponding HTML documents, if required.
-* Remove Draft status and merge the pull request when it is ready.
+* Remove Draft status and merge the pull request.
 
 The ZIP editors monitor ZIP changes and update ZIP headers as
 appropriate.