diff --git a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners.md b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners.md
index c5ae33dfdc58..52d3a0f172b4 100644
--- a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners.md
+++ b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/autoscaling-with-self-hosted-runners.md
@@ -93,7 +93,7 @@ For instructions on how to install the latest runner version, see the installati
 You can create your own autoscaling environment by using payloads received from the [`workflow_job`](/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook. This webhook is available at the repository, organization, and enterprise levels, and the payload for this event contains an `action` key that corresponds to the stages of a workflow job's life-cycle; for example when jobs are `queued`, `in_progress`, and `completed`. You must then create your own scaling automation in response to these webhook payloads.
 
 - For more information about the `workflow_job` webhook, see "[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)."
-- To learn how to work with webhooks, see "[AUTOTITLE](/webhooks-and-events/webhooks/creating-webhooks)."
+- To learn how to work with webhooks, see "[AUTOTITLE](/webhooks)."
 
 ## Authentication requirements
 
diff --git a/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md b/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
index e34555fbd79c..a259c51b1879 100644
--- a/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
+++ b/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
@@ -33,7 +33,7 @@ If you use a third-party static analysis tool that can produce results as Static
 
 ## Integrations with webhooks
 
-You can use {% data variables.product.prodname_code_scanning %} webhooks to build or configure integrations, such as [{% data variables.product.prodname_github_apps %}](/apps/creating-github-apps/setting-up-a-github-app) or [{% data variables.product.prodname_oauth_apps %}](/apps/oauth-apps/building-oauth-apps), that subscribe to {% data variables.product.prodname_code_scanning %} events in your repository. For example, you could build an integration that creates an issue on {% data variables.product.product_name %} or sends you a Slack notification when a new {% data variables.product.prodname_code_scanning %} alert is added in your repository. For more information, see "[AUTOTITLE](/webhooks-and-events/webhooks/creating-webhooks)" and "[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert)."
+You can use {% data variables.product.prodname_code_scanning %} webhooks to build or configure integrations, such as [{% data variables.product.prodname_github_apps %}](/apps/creating-github-apps/setting-up-a-github-app) or [{% data variables.product.prodname_oauth_apps %}](/apps/oauth-apps/building-oauth-apps), that subscribe to {% data variables.product.prodname_code_scanning %} events in your repository. For example, you could build an integration that creates an issue on {% data variables.product.product_name %} or sends you a Slack notification when a new {% data variables.product.prodname_code_scanning %} alert is added in your repository. For more information, see "[AUTOTITLE](/webhooks)" and "[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert)."
 
 ## Further reading
 
diff --git a/content/webhooks/testing-and-troubleshooting-webhooks/receiving-webhooks-with-the-github-cli.md b/content/webhooks/testing-and-troubleshooting-webhooks/receiving-webhooks-with-the-github-cli.md
index dcead762bf97..6896ac1271a1 100644
--- a/content/webhooks/testing-and-troubleshooting-webhooks/receiving-webhooks-with-the-github-cli.md
+++ b/content/webhooks/testing-and-troubleshooting-webhooks/receiving-webhooks-with-the-github-cli.md
@@ -16,7 +16,7 @@ redirect_from:
 
 When you make changes to your integration code, running the code in a local environment lets you test and iterate quickly without deploying the code. You can use {% data variables.product.prodname_cli %} to forward webhooks to your local environment.
 
-Webhook forwarding in the {% data variables.product.prodname_cli %} only works with repository and organization webhooks. If you want to test sponsorship, GitHub App, enterprise, or Marketplace webhooks locally, you'll need to do this manually. For more information, see "[AUTOTITLE](/webhooks-and-events/webhooks/creating-webhooks).
+Webhook forwarding in the {% data variables.product.prodname_cli %} only works with repository and organization webhooks. If you want to test other types of webhooks locally, you'll need to do this manually. For more information, see "[AUTOTITLE](/webhooks/testing-and-troubleshooting-webhooks/testing-webhooks)."
 
 {% warning %}
 
diff --git a/content/webhooks/using-webhooks/best-practices-for-using-webhooks.md b/content/webhooks/using-webhooks/best-practices-for-using-webhooks.md
index b80e252933c0..3c7045996aaa 100644
--- a/content/webhooks/using-webhooks/best-practices-for-using-webhooks.md
+++ b/content/webhooks/using-webhooks/best-practices-for-using-webhooks.md
@@ -13,7 +13,7 @@ topics:
 
 ## Subscribe to the minimum number of events
 
-You should only subscribe to the webhook events that you need. This will reduce the amount of work your server needs to do. For more information, see "[AUTOTITLE](/webhooks/creating-webhooks)."
+You should only subscribe to the webhook events that you need. This will reduce the amount of work your server needs to do. For more information about subscribing to events, see "[AUTOTITLE](/webhooks/creating-webhooks)" and "[AUTOTITLE](/webhooks/using-webhooks/editing-webhooks)."
 
 ## Use a webhook secret
 
diff --git a/content/webhooks/webhook-events-and-payloads.md b/content/webhooks/webhook-events-and-payloads.md
index 58b9d83620a5..94dbd2654ec8 100644
--- a/content/webhooks/webhook-events-and-payloads.md
+++ b/content/webhooks/webhook-events-and-payloads.md
@@ -22,7 +22,7 @@ autogenerated: webhooks
 
 ## About webhook events and payloads
 
-You can create webhooks that subscribe to the events listed on this page. Each webhook event on this page includes a description of the webhook properties for that event. If the event has multiple actions, the properties corresponding to each action are included. For more information, see "[AUTOTITLE](/webhooks/creating-webhooks)."
+You can create webhooks that subscribe to the events listed on this page. Each webhook event on this page includes a description of the webhook properties for that event. If the event has multiple actions, the properties corresponding to each action are included. For more information about subscribing to events, see "[AUTOTITLE](/webhooks/creating-webhooks)" and "[AUTOTITLE](/webhooks/using-webhooks/editing-webhooks)."
 
 {% note %}
 
diff --git a/data/features/actions-ref-protected-ruleset.yml b/data/features/actions-ref-protected-ruleset.yml
new file mode 100644
index 000000000000..ac7a72bb0550
--- /dev/null
+++ b/data/features/actions-ref-protected-ruleset.yml
@@ -0,0 +1,5 @@
+# Ref protected variable respects ruleset configuration
+versions:
+  fpt: '*'
+  ghec: '*'
+  # ghes: TBD
diff --git a/data/reusables/actions/ref_protected-description.md b/data/reusables/actions/ref_protected-description.md
index 9975dc406a3c..6c3757edb94f 100644
--- a/data/reusables/actions/ref_protected-description.md
+++ b/data/reusables/actions/ref_protected-description.md
@@ -1 +1 @@
-`true` if branch protections are configured for the ref that triggered the workflow run.
+`true` if branch protections {% ifversion actions-ref-protected-ruleset %}or [rulesets](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/managing-rulesets-for-a-repository) {% endif %}are configured for the ref that triggered the workflow run.