update beta promotion policy for template consistency and 'no significant' vs 'zero-diff'

Author: deads2k

keps/NNNN-kep-template/README.md

@@ -376,10 +376,11 @@ Below are some examples to consider, in addition to the aforementioned [maturity
 - More rigorous forms of testing—e.g., downgrade tests and scalability tests
 - All functionality completed
 - All security enforcement completed
+- All monitoring requirements completed
 - All testing requirements completed
 - All known pre-release issues and gaps resolved 
 
-**Note:** Beta criteria must include all functional, security, and testing requirements along with resolving all issues and gaps identified
+**Note:** Beta criteria must include all functional, security, monitoring, and testing requirements along with resolving all issues and gaps identified
 
 #### GA
 
@@ -388,7 +389,7 @@ Below are some examples to consider, in addition to the aforementioned [maturity
 - Allowing time for feedback
 - All issues and gaps identified as feedback during beta are resolved
 
-**Note:** GA criteria must not include any functional, security, or testing requirements.  Those must be beta requirements.
+**Note:** GA criteria must not include any functional, security, monitoring, or testing requirements.  Those must be beta requirements.
 
 **Note:** Generally we also wait at least two releases between beta and
 GA/stable, because there's no opportunity for user feedback, or even bug reports,

keps/sig-architecture/5241-beta-featuregate-promotion-requirements/README.md

@@ -190,7 +190,7 @@ This posture makes upgrades higher risk than necessary.
 
 To balance these concerns, we are changing how we evaluate Beta and GA stability criteria.
 The only valid GA criteria are “all issues and gaps identified as feedback during beta are resolved”.
-Promotion from Beta to GA must be zero-diff for the release.
+Promotion from Beta to GA must have no significant change for the release.
 This means that Beta criteria must include all functional, security, monitoring, and testing requirements along
 with resolving all issues and gaps identified prior to beta.