diff --git a/content/copilot/how-tos/manage-and-track-spending/monitor-premium-requests.md b/content/copilot/how-tos/manage-and-track-spending/monitor-premium-requests.md
index c59612ddf64b..e7612a22e6e3 100644
--- a/content/copilot/how-tos/manage-and-track-spending/monitor-premium-requests.md
+++ b/content/copilot/how-tos/manage-and-track-spending/monitor-premium-requests.md
@@ -41,8 +41,6 @@ For information about viewing premium request usage for an organization or enter
 
 If you're using {% data variables.product.prodname_copilot_short %} in an editor, you can view your usage directly in the editor. For example, in {% data variables.product.prodname_vscode %}, you can view information about features included in your plan, your progress towards any limits on your plan, and the date your allowance resets.
 
-![Screenshot of the {% data variables.product.prodname_copilot_short %} current usage window in {% data variables.product.prodname_vscode %}. The "Code completions" and "Chat messages" bars indicate they are included with the user's {% data variables.product.prodname_copilot_short %} plan. The "Premium requests" bar indicates the user has used 99.5% of their allowance, and that it will reset on June 30, 2025.](/assets/images/help/copilot/vscode-current-usage.png)
-
 You can access usage information in the following IDEs.
 
 * **In {% data variables.product.prodname_vscode %}**, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) in the status bar.
diff --git a/content/issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests.md b/content/issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests.md
index c9c75f18045c..3dd70b0c6917 100644
--- a/content/issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests.md
+++ b/content/issues/tracking-your-work-with-issues/using-issues/viewing-all-of-your-issues-and-pull-requests.md
@@ -40,10 +40,7 @@ You can create up to 25 saved views.
 ### Create a saved view
 
 1. At the top of any page, click {% octicon "issue-opened" aria-label="Issues" %} to see your issues.
-1. On the left sidebar, under "Views", click **{% octicon "plus" aria-label="Create view" %}**.
-
-   ![Screenshot of the {% octicon "plus" aria-label="Create view" %}. The icon is outlined in dark orange.](/assets/images/help/issues/issues-create-saved-view.png)
-
+1. On the left sidebar, to the right of "Views", click **{% octicon "plus" aria-label="Create view" %}**.
 1. Add a title, description, and custom icon for your view.
 1. Under "Query", build your search query using the advanced filters. For help using filters, see [AUTOTITLE](/search-github/searching-on-github/searching-issues-and-pull-requests).
    > [!TIP] Use the `is:pr` filter to include pull requests in the saved view.
diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md
index 080dfa913d1c..95edbe3c99ff 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md
@@ -134,6 +134,10 @@ Optionally, you can require all comments on the pull request to be resolved befo
 Optionally, you can require a merge type of merge, squash, or rebase. This means the targeted branches may only be merged based on the allowed type. Additionally if the repository has disabled a merge method and the ruleset required a different method, the merge will be blocked. See [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github).
 {% endif %}
 
+{% ifversion repo-rules-required-reviewer %}
+Optionally, you can require review from specific teams. This means you can add a select number of reviewers who must submit a specific number of reviews for specific files and folders.
+{% endif %}
+
 ## Require status checks to pass before merging
 
 Required status checks ensure that all required CI tests are passing before collaborators can make changes to a branch or tag targeted by your ruleset. Required status checks can be checks or statuses. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks).
diff --git a/data/features/repo-rules-required-reviewer.yml b/data/features/repo-rules-required-reviewer.yml
new file mode 100644
index 000000000000..fb191f7ea00b
--- /dev/null
+++ b/data/features/repo-rules-required-reviewer.yml
@@ -0,0 +1,7 @@
+# Reference: #20097
+# Public preview for required reviewer rules
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.22'