diff --git a/data/reusables/repositories/about-push-rule-delegated-bypass.md b/data/reusables/repositories/about-push-rule-delegated-bypass.md
index f92756a2f2..3de93a8f59 100644
--- a/data/reusables/repositories/about-push-rule-delegated-bypass.md
+++ b/data/reusables/repositories/about-push-rule-delegated-bypass.md
@@ -1,5 +1,3 @@
->[!NOTE] Delegated bypass for push rules is currently in {% data variables.release-phases.public_preview %} and subject to change.
-
 Delegated bypass for push rulesets lets you control who can bypass push protection and which blocked pushes should be allowed.
 
  With delegated bypass, contributors to a repository must request "bypass privileges" when pushing commits that contain restricted content. The request is sent to a designated group of reviewers, who either approve or deny the request to bypass push rules.
diff --git a/data/reusables/repositories/managing-delegated-bypass.md b/data/reusables/repositories/managing-delegated-bypass.md
index 6e15289928..8766af6fa1 100644
--- a/data/reusables/repositories/managing-delegated-bypass.md
+++ b/data/reusables/repositories/managing-delegated-bypass.md
@@ -1,7 +1,5 @@
 ## Managing requests to bypass push rules
 
->[!NOTE] Delegated bypass for push rules is currently in {% data variables.release-phases.public_preview %} and subject to change.
-
 You can view and manage all requests for bypass privileges on the “Bypass Requests" page, located under the **Rules** settings of the repository.
 
 {% data reusables.repositories.navigate-to-repo %}