Hyperlint Automation: Broken Link Fixes (#19685)

* Fix issue: WorkspaceTaskSubType.BROKEN_LINK

* Fix issue: WorkspaceTaskSubType.BROKEN_LINK

* Fix issue: WorkspaceTaskSubType.BROKEN_LINK

* Fix issue: WorkspaceTaskSubType.BROKEN_LINK

* Fix issue: WorkspaceTaskSubType.BROKEN_LINK

* Update src/content/docs/workers/testing/vitest-integration/get-started/write-your-first-test.mdx

---------

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
Co-authored-by: ToriLindsay <[email protected]>

Author: hyperlint-ai[bot]

src/content/docs/pages/configuration/git-integration/github-integration.mdx

@@ -67,7 +67,7 @@ To remove access to an individual GitHub repository, you can navigate to **Repos
 
 #### Remove Cloudflare access to the entire GitHub account
 
-To remove Cloudflare Workers and Pages access to your entire Git account, you can navigate to **Uninstall "Cloudflare Workers and Pages"**, then select **Uninstall**. Removing access to the Cloudflare Workers and Pages app will revoke Cloudflare's access to _all repositories_ from that GitHub account. If you want to only disable automatic builds and deployments, follow the [Disable Build](/workers/ci-cd/builds/#disabling-builds) instructions.
+To remove Cloudflare Workers and Pages access to your entire Git account, you can navigate to **Uninstall "Cloudflare Workers and Pages"**, then select **Uninstall**. Removing access to the Cloudflare Workers and Pages app will revoke Cloudflare's access to _all repositories_ from that GitHub account. If you want to only disable automatic builds and deployments, follow the [Disable Build](/workers/ci-cd/builds/#disconnecting-builds) instructions.
 
 Note that removing access to GitHub will disable new builds for Workers and Pages project that were connected to those repositories, though your previous deployments will continue to be hosted by Cloudflare Workers.
 

src/content/docs/pages/framework-guides/nextjs/ssr/bindings.mdx

@@ -59,7 +59,7 @@ interface CloudflareEnv {
 
 ## Other Cloudflare APIs (`cf`, `ctx`)
 
-Access context about the incoming request from the [`cf` object](/workers/runtime-apis/request/#incomingrequestcfproperties), as well as [lifecycle methods from the `ctx` object](/workers/runtime-apis/handlers/fetch/#lifecycle-methods) from the return value of [`getRequestContext()`](https://github.com/cloudflare/next-on-pages/blob/main/packages/next-on-pages/src/api/getRequestContext.ts):
+Access context about the incoming request from the [`cf` object](/workers/runtime-apis/request/#incomingrequestcfproperties), as well as [lifecycle methods from the `ctx` object](/workers/runtime-apis/handlers/fetch/) from the return value of [`getRequestContext()`](https://github.com/cloudflare/next-on-pages/blob/main/packages/next-on-pages/src/api/getRequestContext.ts):
 
 ```js
 import { getRequestContext } from "@cloudflare/next-on-pages";

src/content/docs/workers/ci-cd/builds/git-integration/github-integration.mdx

@@ -60,7 +60,7 @@ To remove access to an individual GitHub repository, you can navigate to **Repos
 
 #### Remove Cloudflare access to the entire GitHub account
 
-To remove Cloudflare Workers and Pages access to your entire Git account, you can navigate to **Uninstall "Cloudflare Workers and Pages"**, then select **Uninstall**. Removing access to the Cloudflare Workers and Pages app will revoke Cloudflare's access to _all repositories_ from that GitHub account. If you want to only disable automatic builds and deployments, follow the [Disable Build](/workers/ci-cd/builds/#disabling-builds) instructions.
+To remove Cloudflare Workers and Pages access to your entire Git account, you can navigate to **Uninstall "Cloudflare Workers and Pages"**, then select **Uninstall**. Removing access to the Cloudflare Workers and Pages app will revoke Cloudflare's access to _all repositories_ from that GitHub account. If you want to only disable automatic builds and deployments, follow the [Disable Build](/workers/ci-cd/builds/#disconnecting-builds) instructions.
 
 Note that removing access to GitHub will disable new builds for Workers and Pages project that were connected to those repositories, though your previous deployments will continue to be hosted by Cloudflare Workers.
 

src/content/docs/workers/runtime-apis/bindings/service-bindings/rpc.mdx

@@ -18,7 +18,7 @@ The [RPC system in Workers](/workers/runtime-apis/rpc) is designed feel as simil
 
 :::note
 
-You can also use RPC to communicate between Workers and [Durable Objects](/durable-objects/best-practices/create-durable-object-stubs-and-send-requests/#call-rpc-methods).
+You can also use RPC to communicate between Workers and [Durable Objects](/durable-objects/best-practices/create-durable-object-stubs-and-send-requests/#invoke-rpc-methods).
 :::
 
 ## Example

src/content/docs/workers/testing/vitest-integration/get-started/write-your-first-test.mdx

@@ -17,7 +17,7 @@ This guide will instruct you through installing and setting up the `@cloudflare/
 
 - Make sure that your Worker is developed using the ES modules format. To migrate from the service worker format to the ES modules format, refer to the [Migrate to the ES modules format](/workers/reference/migrate-to-module-workers/) guide.
 
-- In your project's `wrangler.toml / wrangler.json` file, define a [compatibility date](/workers/configuration/compatibility-dates/) of `2022-10-31` or higher, and include `nodejs_compat` in your [compatibility flags](/workers/wrangler/configuration/#use-runtime-apis-directly).
+- In your project's `wrangler.toml / wrangler.json` file, define a [compatibility date](/workers/configuration/compatibility-dates/) of `2022-10-31` or higher, and include `nodejs_compat` in your [compatibility flags](/workers/configuration/compatibility-flags).
 
 ## Install Vitest and `@cloudflare/vitest-pool-workers`