docs: fix broken links

docs/english/legacy/events-api.md

@@ -4,7 +4,7 @@
 
 Development has fully stopped for this package and all remaining open issues and pull requests have been closed. The package was removed from the project in [PR #2517](https://github.com/slackapi/node-slack-sdk/pull/2517).
 
-At this time, we recommend migrating to [Bolt for JavaScript](https://github.com/slackapi/bolt-js), a framework that offers all of the functionality available in those packages (and more). To help with that process, we've provided some [migration samples](/tools/node-slack-sdk/migration/migrating-to-v6) for those looking to convert their existing apps.
+At this time, we recommend migrating to [Bolt for JavaScript](https://github.com/slackapi/bolt-js), a framework that offers all of the functionality available in those packages (and more). To help with that process, we've provided some [migration samples](/tools/node-slack-sdk/migration/legacy/migrating-to-v6) for those looking to convert their existing apps.
 
 :::
 

docs/english/legacy/interactive-messages.md

@@ -4,7 +4,7 @@
 
 Development has fully stopped for this package and all remaining open issues and pull requests have been closed. The package was removed from the project in [PR #2517](https://github.com/slackapi/node-slack-sdk/pull/2517).
 
-At this time, we recommend migrating to [Bolt for JavaScript](https://github.com/slackapi/bolt-js), a framework that offers all of the functionality available in those packages (and more). To help with that process, we've provided some [migration samples](/tools/node-slack-sdk/migration/migrating-to-v6) for those looking to convert their existing apps.
+At this time, we recommend migrating to [Bolt for JavaScript](https://github.com/slackapi/bolt-js), a framework that offers all of the functionality available in those packages (and more). To help with that process, we've provided some [migration samples](/tools/node-slack-sdk/migration/legacy/migrating-to-v6) for those looking to convert their existing apps.
 
 :::
 

docs/english/migration/socket-mode/migrating-socket-mode-package-to-v3.md

@@ -207,7 +207,7 @@ If your logging or error monitoring tools filter on `error.name`, update those f
 ### `dispatcher` option for unified proxy/TLS configuration
 
 :::tip[You can skip manual dispatcher configuration entirely by using `http.setGlobalProxyFromEnv()` or `NODE_USE_ENV_PROXY=1`]
-See [the `httpAgent` option removed section](#we-removed-the-httpagent-option) above for more detail.
+See [the `httpAgent` option removed section](#weve-removed-the-httpagent-option) above for more detail.
 :::
 
 Pass any undici `Dispatcher` and it'll handle both WebSocket and HTTP traffic:

docs/english/tutorials/local-development.md

@@ -5,16 +5,16 @@ This tutorial is meant to guide developers through setting up and configuring a
 Feel free to skip around to the specific sections relevant to you — we won't mind. 🙂
 
 ## Create an app
-Head over to [Create an app](/tools/bolt-js/getting-started#create-an-app) within our Getting started with JavaScript for Bolt page for instructions on how to create a Slack app on [api.slack.com/apps](https://api.slack.com/apps).
+Head over to [Create an app](/tools/bolt-js/creating-an-app#creating-an-app) within our Getting started with JavaScript for Bolt page for instructions on how to create a Slack app on [api.slack.com/apps](https://api.slack.com/apps).
 
 ## Tokens and installing apps
-Head over to [Tokens and installing apps](/tools/bolt-js/getting-started#tokens-and-installing-apps) within our Getting started with JavaScript for Bolt page for information on what tokens are, the [different kinds of tokens available](/authentication/tokens), how to create them on [api.slack.com/apps](https://api.slack.com/apps), how to install your app to a live Slack workspace, and finally how to retrieve your access token.
+Head over to [Tokens and installing apps](/tools/bolt-js/creating-an-app#installing-the-app) within our Getting started with JavaScript for Bolt page for information on what tokens are, the [different kinds of tokens available](/authentication/tokens), how to create them on [api.slack.com/apps](https://api.slack.com/apps), how to install your app to a live Slack workspace, and finally how to retrieve your access token.
 
 ## Socket Mode vs. HTTP
 Your app can [communicate with Slack using one of two methods](/apis/events-api):
 
 1. [Socket Mode](/apis/events-api/using-socket-mode). Connect to Slack using a direct and long-lived socket connection. This is our recommended approach when getting started in local development because of its convenience. However, apps cannot use Socket Mode and also be listed in the [Slack Marketplace](/slack-marketplace/distributing-your-app-in-the-slack-marketplace). For that, you'll need to use [HTTP](#http). It is also important to remember that Socket Mode is more prone to network faults because the connection is a long-lived one.
-2. [HTTP](/apis/events-api/using-http-request-urls). Expose your app using a public-facing URL that Slack will send HTTP requests to. This requires a few [additional steps](/tools/bolt-js/getting-started) to set up, but may be more resilient to network disruptions than communication via Socket Mode.
+2. [HTTP](/apis/events-api/using-http-request-urls). Expose your app using a public-facing URL that Slack will send HTTP requests to. This requires a few [additional steps](/tools/bolt-js/creating-an-app#preparing-receive-events) to set up, but may be more resilient to network disruptions than communication via Socket Mode.
 
 This tutorial will cover how to set up your app using either approach.
 

docs/english/typescript.md

@@ -10,7 +10,7 @@ This page describes how to use this package from a project that also uses TypeSc
 
 Latest major versions of `@slack/web-api`, `@slack/rtm-api`, and `@slack/webhook` packages are supported to build against TypeScript version 5.3.x. You can try to use a greater minor version of Typescript like 5.4 or above, but beware that [API Breaking Changes](https://github.com/microsoft/TypeScript/wiki/API-Breaking-Changes) can be introduced in minor Typescript versions that break compatibility.
 
-The v6 versions of `@slack/web-api`, `@slack/rtm-api`, and `@slack/webhook` packages are supported to build against the minimum TypeScript version v4.1.0. See also [v5 to v6 migration guide](/tools/node-slack-sdk/migration/migrating-to-v6) for more details.
+The v6 versions of `@slack/web-api`, `@slack/rtm-api`, and `@slack/webhook` packages are supported to build against the minimum TypeScript version v4.1.0. See also [v5 to v6 migration guide](/tools/node-slack-sdk/migration/legacy/migrating-to-v6) for more details.
 
 The v5 versions of `@slack/web-api`, `@slack/rtm-api`, and `@slack/webhook` packages are supported to build against TypeScript v3.3.0 or higher. The v4 versions of the `@slack/web-api`, `@slack/rtm-api`, and `@slack/webhook` packages are supported to build against TypeScript v2.7.0 or higher.
 

docs/english/web-api.md

@@ -19,8 +19,8 @@ We recommend you read our documentation on [Basic app setup](/quickstart).
 This article contains the steps you must follow to get your access token:
 
 1. [Create a new Slack application](/quickstart)
-2. [Set permissions your app will request](/quickstart#scopes)
-3. [Install the app to a workspace](/quickstart#installing)
+2. [Set permissions your app will request](/app-management/quickstart-app-settings#scopes)
+3. [Install the app to a workspace](/app-management/quickstart-app-settings#installing)
 4. Finally, get your access token
 
 You can also read the [Getting Started guide](/tools/node-slack-sdk/getting-started) which guides