diff --git a/zip-0000.rst b/zip-0000.rst
index 2153d5bf..3ac67f1f 100644
--- a/zip-0000.rst
+++ b/zip-0000.rst
@@ -606,10 +606,8 @@ ZIP Status Field
 * Obsolete: The status when a ZIP is no longer relevant (typically when
   superseded by another ZIP).
 
-More details on the status workflow are given in the section below.
-
-Specification
--------------
+Specification of Status Workflow
+--------------------------------
 
 Owners of a ZIP MAY decide on their own to change the status between
 Draft or Withdrawn.
@@ -628,29 +626,18 @@ the implementation audit. If the Owners miss this deadline, the Editors
 or Owners MAY choose to update the Deployment section of the ZIP to
 target another upgrade, at their discretion.
 
-ZIPs should be changed from Draft or Proposed status, to Rejected
-status, upon request by any person, if they have not made progress in
-one year. Such a ZIP may be changed to Draft status if the Owner
-provides revisions that meaningfully address public criticism of the
-proposal, or to Proposed status if it meets the criteria required as
-described in the previous paragraphs. Rejections are applied by consensus
-among the current ZIP Editors.
-
-A Consensus or Standards ZIP becomes Final when its associated network
-upgrade or other protocol change is activated on Zcash's mainnet.
-
-A Process or Informational ZIP may change status from Draft to Active
+A Process or Informational ZIP SHOULD change status from Draft to Active
 when it achieves rough consensus on the forum or PR. Such a proposal is
 said to have rough consensus if it has been open to discussion on the
 forum or GitHub PR for at least one month, and no person maintains
 any unaddressed substantiated objections to it. Addressed or obstructive
-objections may be ignored/overruled by general agreement that they have
-been sufficiently addressed, but clear reasoning must be given in such
+objections can be ignored/overruled by general agreement that they have
+been sufficiently addressed, but clear reasoning MUST be given in such
 circumstances.
 
-When an Active or Final ZIP is no longer relevant, its status may be
-changed to Obsolete. This change must also be objectively verifiable
-and/or discussed. Final ZIPs may be updated; the specification is still
+When an Active or Final ZIP is no longer relevant, its status SHOULD be
+changed to Obsolete. This change MUST also be objectively verifiable
+and/or discussed. Final ZIPs MAY be updated; the specification is still
 in force but modified by another specified ZIP or ZIPs (check the
 optional Updated-by header).
 
@@ -738,7 +725,7 @@ Not acceptable licenses
 -----------------------
 
 All licenses not explicitly included in the above lists are not
-acceptable terms for a Zcash Improvement Proposal.
+acceptable terms and MUST NOT be used for a Zcash Improvement Proposal.
 
 Rationale
 ---------