fix: repoint 6 broken cross-page anchors on REST, GraphQL, and webhook pages (#62415)

heiskr · Copilot · web-flow · commit c1e38e7ca0a7 · 2026-07-24T14:07:37.000Z
Co-authored-by: Copilot &lt;223556219+Copilot@users.noreply.github.com&gt;
Copilot-Session: 7bc51b35-b5bd-4cec-9948-a1664d171f4c
diff --git a/content/actions/how-tos/deploy/configure-and-manage-deployments/create-custom-protection-rules.md b/content/actions/how-tos/deploy/configure-and-manage-deployments/create-custom-protection-rules.md
@@ -46,7 +46,7 @@ Custom deployment protection rules are not compatible when a workflow job's envi
 
 {% endif %}
 
-1. Validate the incoming `POST` request. For more information, see [AUTOTITLE](/webhooks/using-webhooks/validating-webhook-deliveries#validating-payloads-from-github).
+1. Validate the incoming `POST` request. For more information, see [AUTOTITLE](/webhooks/using-webhooks/validating-webhook-deliveries#validating-webhook-deliveries).
 1. Use a JSON Web Token to authenticate as a {% data variables.product.prodname_github_app %}. For more information, see [AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-as-a-github-app#about-authentication-as-a-github-app).
 1. Using the installation ID from the `deployment_protection_rule` webhook payload, generate an install token. For more information, see [AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/about-authentication-with-a-github-app#authenticating-as-a-github-app).
 
diff --git a/content/code-security/tutorials/secret-scanning-partner-program.md b/content/code-security/tutorials/secret-scanning-partner-program.md
@@ -125,7 +125,7 @@ will provide several `key_identifier` and public keys. You can determine which p
 key to use based on the value of `Github-Public-Key-Identifier`.
 
 > [!NOTE]
-> When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a {% data variables.product.pat_v1 %} (no scopes required) or a {% data variables.product.pat_v2 %} (only the automatic public repositories read access required) as suggested in the samples below, or use a conditional request. For more information, see [AUTOTITLE](/rest/using-the-rest-api/getting-started-with-the-rest-api#conditional-requests).
+> When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a {% data variables.product.pat_v1 %} (no scopes required) or a {% data variables.product.pat_v2 %} (only the automatic public repositories read access required) as suggested in the samples below, or use a conditional request. For more information, see [AUTOTITLE](/rest/using-the-rest-api/best-practices-for-using-the-rest-api#use-conditional-requests-if-appropriate).
 
 > [!NOTE]
 > The signature was generated using the raw message body. So it's important you also use the raw message body for signature validation, instead of parsing and stringifying the JSON, to avoid rearranging the message or changing spacing.
diff --git a/content/rest/guides/building-a-ci-server.md b/content/rest/guides/building-a-ci-server.md
@@ -29,7 +29,7 @@ Travis, Jenkins, or something else entirely. The crux of this guide will be sett
 and configuring the server managing the communication.
 
 If you haven't already, [download `ngrok`](https://ngrok.com/), and learn how
-to [use it](/webhooks/using-webhooks/handling-webhook-deliveries#using-ngrok). We find it to be a very useful tool for exposing local
+to [use it](https://ngrok.com/docs/getting-started/). We find it to be a very useful tool for exposing local
 applications to the internet.
 
 {% ifversion cli-webhook-forwarding %}
diff --git a/content/rest/guides/delivering-deployments.md b/content/rest/guides/delivering-deployments.md
@@ -29,7 +29,7 @@ Heroku, Amazon, or something else entirely. The crux of this guide will be setti
 and configuring the server managing the communication.
 
 If you haven't already, be sure to [download `ngrok`](https://ngrok.com/), and learn how
-to [use it](/webhooks/using-webhooks/handling-webhook-deliveries#using-ngrok). We find it to be a very useful tool for exposing local
+to [use it](https://ngrok.com/docs/getting-started/). We find it to be a very useful tool for exposing local
 applications to the internet.
 
 {% ifversion cli-webhook-forwarding %}
diff --git a/content/rest/quickstart.md b/content/rest/quickstart.md
@@ -119,7 +119,7 @@ You can use Octokit.js to interact with the {% data variables.product.prodname_d
    });
    ```
 
-1. Use `octokit.request` to execute your request. Send the HTTP method and path as the first argument. Specify any path, query, and body parameters in an object as the second argument. For more information about parameters, see [AUTOTITLE](/rest/using-the-rest-api/getting-started-with-the-rest-api#using-parameters).
+1. Use `octokit.request` to execute your request. Send the HTTP method and path as the first argument. Specify any path, query, and body parameters in an object as the second argument. For more information about parameters, see [AUTOTITLE](/rest/using-the-rest-api/getting-started-with-the-rest-api#parameters).
 
    For example, in the following request the HTTP method is `GET`, the path is `/repos/{owner}/{repo}/issues`, and the parameters are {% ifversion ghes %}`owner: "REPO-OWNER"` and `repo: "REPO-NAME"`{% else %}`owner: "octocat"` and `repo: "Spoon-Knife"`{% endif %}.{% ifversion ghes %} Replace `REPO-OWNER` with the name of the account that owns the repository, and `REPO-NAME` with the name of the repository.{% endif %}
 
diff --git a/content/rest/rate-limit/rate-limit.md b/content/rest/rate-limit/rate-limit.md
@@ -18,7 +18,7 @@ category:
 
 You can check your current rate limit status at any time. For more information about rate limit rules, see [AUTOTITLE](/rest/using-the-rest-api/rate-limits-for-the-rest-api).
 
-The REST API for searching items has a custom rate limit that is separate from the rate limit governing the other REST API endpoints. For more information, see [AUTOTITLE](/rest/search/search). The GraphQL API also has a custom rate limit that is separate from and calculated differently than rate limits in the REST API. For more information, see [AUTOTITLE](/graphql/overview/rate-limits-and-query-limits-for-the-graphql-api#rate-limit). For these reasons, the API response categorizes your rate limit. Under `resources`, you'll see objects relating to different categories:
+The REST API for searching items has a custom rate limit that is separate from the rate limit governing the other REST API endpoints. For more information, see [AUTOTITLE](/rest/search/search). The GraphQL API also has a custom rate limit that is separate from and calculated differently than rate limits in the REST API. For more information, see [AUTOTITLE](/graphql/overview/rate-limits-and-query-limits-for-the-graphql-api#primary-rate-limit). For these reasons, the API response categorizes your rate limit. Under `resources`, you'll see objects relating to different categories:
 
 * The `core` object provides your rate limit status for all non-search-related resources in the REST API.
 
diff --git a/content/rest/using-the-rest-api/using-pagination-in-the-rest-api.md b/content/rest/using-the-rest-api/using-pagination-in-the-rest-api.md
@@ -60,11 +60,11 @@ curl --include --request GET \
 --header "Accept: application/vnd.github+json"
 ```
 
-The URLs in the `link` header use query parameters to indicate which page of results to return. The query parameters in the `link` URLs may differ between endpoints, however each paginated endpoint will use the `page`, `before`/`after`, or `since` query parameters. (Some endpoints use the `since` parameter for something other than pagination.) In all cases, you can use the URLs in the `link` header to fetch additional pages of results. For more information about query parameters see [AUTOTITLE](/rest/using-the-rest-api/getting-started-with-the-rest-api#using-query-parameters).
+The URLs in the `link` header use query parameters to indicate which page of results to return. The query parameters in the `link` URLs may differ between endpoints, however each paginated endpoint will use the `page`, `before`/`after`, or `since` query parameters. (Some endpoints use the `since` parameter for something other than pagination.) In all cases, you can use the URLs in the `link` header to fetch additional pages of results. For more information about query parameters see [AUTOTITLE](/rest/using-the-rest-api/getting-started-with-the-rest-api#query-parameters).
 
 ## Changing the number of items per page
 
-If an endpoint supports the `per_page` query parameter, then you can control how many results are returned on a page. For more information about query parameters see [AUTOTITLE](/rest/using-the-rest-api/getting-started-with-the-rest-api#using-query-parameters).
+If an endpoint supports the `per_page` query parameter, then you can control how many results are returned on a page. For more information about query parameters see [AUTOTITLE](/rest/using-the-rest-api/getting-started-with-the-rest-api#query-parameters).
 
 For example, this request uses the `per_page` query parameter to return two items per page:
 
