diff --git a/src/en/wizden-staff/maintainer/review-procedure.md b/src/en/wizden-staff/maintainer/review-procedure.md
index 50b5f0501..b52618d67 100644
--- a/src/en/wizden-staff/maintainer/review-procedure.md
+++ b/src/en/wizden-staff/maintainer/review-procedure.md
@@ -5,7 +5,7 @@ This document outlines the Maintainer procedure for reviewing and merging PRs to
 
 Pull requests targeting the `staging` or `stable` branch are subject to the [Hotfix Procedure](hotfix-procedure.md).
 
-Any portion of this procedure may be waived and/or modified with written permission (_via Discord or GitHub_) from a Lead Maintainer, Project Manager or Wizard.
+Any portion of this procedure may be waived for single PRs with written permission (_via Discord or GitHub_) from a Lead Maintainer, Project Manager or Wizard.
 
 ```admonish note
 Note that these procedures are ultimately flexible; however, Maintainers who deviate from this policy are expected to provide concrete and valid reasoning when doing so.
@@ -179,4 +179,4 @@ Major game features usually follow the below dynamic:
 2. Maintainers discuss the document in an informal discussion. If most agree, the document is marked with `S: Doc Approved`, and the contributor can start work on the actual feature. As the feature is developed, the document is updated if necessary.
 3. Once the content-side implementation is ready to be merged, both the design document and the content pull request are merged in tandem.
 
-The intention behind this is to ensure that contributors do not waste time implementing a feature that may not fit well into Upstream's intended gameplay.
\ No newline at end of file
+The intention behind this is to ensure that contributors do not waste time implementing a feature that may not fit well into Upstream's intended gameplay.