links

lukegalbraithrussell · lukegalbraithrussell · commit 5c61bd744080 · 2025-08-04T13:56:15.000-07:00
diff --git a/docs/english/building-an-app.md b/docs/english/building-an-app.md
@@ -173,7 +173,7 @@ When an event occurs, Slack will send your app some information about the event,
 
 :::tip[Using proxy services]
 
-For local development, you can use a proxy service like ngrok to create a public URL and tunnel requests to your development environment. Refer to [ngrok's getting started guide](https://ngrok.com/docs#getting-started-expose) on how to create this tunnel. And when you get to hosting your app, we've collected some of the most common hosting providers Slack developers use to host their apps [on our API site](/distribution/hosting-slack-apps/). 
+For local development, you can use a proxy service like ngrok to create a public URL and tunnel requests to your development environment. Refer to [ngrok's getting started guide](https://ngrok.com/docs#getting-started-expose) on how to create this tunnel. And when you get to hosting your app, we've collected some of the most common hosting providers Slack developers use to host their apps [on our API site](/app-management/hosting-slack-apps). 
 
 :::
 
diff --git a/docs/english/concepts/ai-apps.md b/docs/english/concepts/ai-apps.md
@@ -29,7 +29,7 @@ The Agents & AI Apps feature comprises a unique messaging experience for Slack.
 That being said, using the `Assistant` class will streamline the process. And we already wrote this nice guide for you!
 
 :::info
-You _could_ go it alone and [listen](/bolt-python/event-listening) for the `assistant_thread_started`, `assistant_thread_context_changed`, and `message.im` events (see implementation details below) in order to implement the AI features in your app. That being said, using the `Assistant` class will streamline the process. And we already wrote this nice guide for you!
+You _could_ go it alone and [listen](/bolt-python/concepts/event-listening) for the `assistant_thread_started`, `assistant_thread_context_changed`, and `message.im` events (see implementation details below) in order to implement the AI features in your app. That being said, using the `Assistant` class will streamline the process. And we already wrote this nice guide for you!
 :::
 
 ## The `Assistant` class instance {#assistant-class}
diff --git a/docs/english/concepts/custom-steps.md b/docs/english/concepts/custom-steps.md
@@ -69,7 +69,7 @@ Example app manifest definition
 
 Your app's custom steps may create interactivity points for users, for example: Post a message with a button.
 
-If such interaction points originate from a custom step execution, the events sent to your app representing the end-user interaction with these points are considered to be _function-scoped interactivity events_. These interactivity events can be handled by your app using the same concepts we covered earlier, such as [Listening to actions](/bolt-python/concepts/action-listening).
+If such interaction points originate from a custom step execution, the events sent to your app representing the end-user interaction with these points are considered to be _function-scoped interactivity events_. These interactivity events can be handled by your app using the same concepts we covered earlier, such as [Listening to actions](/bolt-python/concepts/actions).
 
 _function-scoped interactivity events_ will contain data related to the custom step (`function_executed` event) they were spawned from, such as custom step `inputs` and access to `complete()` and `fail()` listener arguments.
 
diff --git a/docs/english/concepts/select-menu-options.md b/docs/english/concepts/select-menu-options.md
@@ -4,7 +4,7 @@ lang: en
 slug: /bolt-python/concepts/options
 ---
 
-The `options()` method listens for incoming option request payloads from Slack. [Similar to `action()`](/bolt-python/concepts/action-listening),
+The `options()` method listens for incoming option request payloads from Slack. [Similar to `action()`](/bolt-python/concepts/actions),
 an `action_id` or constraints object is required. In order to load external data into your select menus, you must provide an options load URL in your app configuration, appended with `/slack/events`.
 
 While it's recommended to use `action_id` for `external_select` menus, dialogs do not support Block Kit so you'll have to use the constraints object to filter on a `callback_id`.
diff --git a/docs/english/concepts/updating-pushing-views.md b/docs/english/concepts/updating-pushing-views.md
@@ -12,7 +12,7 @@ To update a view, you can use the built-in client to call `views_update` with th
 
 ## The `views_push` method
 
-To push a new view onto the view stack, you can use the built-in client to call `views_push` with a valid `trigger_id` a new [view payload](/reference/interaction-payloads/view-interactions-payload/#view_submission). The arguments for `views_push` is the same as [opening modals](/bolt-python/concepts/creating-models). After you open a modal, you may only push two additional views onto the view stack.
+To push a new view onto the view stack, you can use the built-in client to call `views_push` with a valid `trigger_id` a new [view payload](/reference/interaction-payloads/view-interactions-payload/#view_submission). The arguments for `views_push` is the same as [opening modals](/bolt-python/concepts/opening-models). After you open a modal, you may only push two additional views onto the view stack.
 
 Learn more about updating and pushing views in our [API documentation](/surfaces/modals)
 
diff --git a/docs/english/getting-started.md b/docs/english/getting-started.md
@@ -296,5 +296,5 @@ You can now continue customizing your app with various features to make it right
 - Explore the different events your bot can listen to with the [`app.event()`](/bolt-python/concepts/event-listening) method. All of the [events](/reference/events) are listed on the API docs site.
 - Bolt allows you to call [Web API](/bolt-python/concepts/web-api) methods with the client attached to your app. There are [over 200 methods](/reference/methods) on the API docs site.
 - Learn more about the different [token types](/authentication/tokens) and [authentication setups](/bolt-python/concepts/authenticating-oauth). Your app might need different tokens depending on the actions you want to perform or for installations to multiple workspaces.
-- Receive events using HTTP for various deployment methods, such as deploying to [Heroku](/bolt-python/deployments/heroku) or [AWS Lambda](/bolt-python/deployments/aws-lambda).
+- Receive events using HTTP for various deployment methods, such as deploying to Heroku or AWS Lambda.
 - Read on [app design](/surfaces/app-design) and compose fancy messages with blocks using [Block Kit Builder](https://app.slack.com/block-kit-builder) to prototype messages.
diff --git a/docs/english/tutorial/ai-chatbot/ai-chatbot.md b/docs/english/tutorial/ai-chatbot/ai-chatbot.md
@@ -197,6 +197,6 @@ You can also navigate to **Bolty** in your **Apps** list and select the **Messag
 
 Congratulations! You've successfully integrated the power of AI into your workspace. Check out these links to take the next steps in your Bolt for Python journey.
 
-* To learn more about Bolt for Python, refer to the [Getting started](../getting-started) documentation.
+* To learn more about Bolt for Python, refer to the [Getting started](/getting-started) documentation.
 * For more details about creating workflow steps using the Bolt SDK, refer to the [workflow steps for Bolt](/workflows/workflow-steps) guide.
-* To use the Bolt for Python SDK to develop on the automations platform, refer to the [Create a workflow step for Workflow Builder: Bolt for Python](/bolt-python/bolt-python/tutorial/custom-steps) tutorial.
+* To use the Bolt for Python SDK to develop on the automations platform, refer to the [Create a workflow step for Workflow Builder: Bolt for Python](/bolt-python/tutorial/custom-steps-workflow-builder-new) tutorial.
diff --git a/docs/english/tutorial/custom-steps-workflow-builder-new/custom-steps-workflow-builder-new.md b/docs/english/tutorial/custom-steps-workflow-builder-new/custom-steps-workflow-builder-new.md
@@ -6,7 +6,7 @@ title: Custom Steps for Workflow Builder (new app)
 If you don't have a paid workspace for development, you can join the [Developer Program](https://api.slack.com/developer-program) and provision a sandbox with access to all Slack features for free.
 :::
 
-Adding a workflow step to your app and implementing a corresponding function listener is how you define a custom Workflow Builder step. In this tutorial, you'll use [Bolt for Python](/bolt-python/bolt-python/) to add your workflow step, then wire it up in [Workflow Builder](https://slack.com/help/articles/360035692513-Guide-to-Workflow-Builder).
+Adding a workflow step to your app and implementing a corresponding function listener is how you define a custom Workflow Builder step. In this tutorial, you'll use [Bolt for Python](/bolt-python/) to add your workflow step, then wire it up in [Workflow Builder](https://slack.com/help/articles/360035692513-Guide-to-Workflow-Builder).
 
 When finished, you'll be ready to build scalable and innovative workflow steps for anyone using Workflow Builder in your workspace.
 
@@ -70,7 +70,7 @@ All of your app's settings can be configured within these screens. By creating a
 
 Navigate to **Event Subscriptions** and expand **Subscribe to bot events** to see that we have subscribed to the `function_executed` event. This is also a requirement for adding workflow steps to our app, as it lets our app know when a step has been triggered, allowing our app to respond to it. 
 
-Another configuration setting to note is **Socket Mode**. We have turned this on for our local development, but socket mode is not intended for use in a production environment. When you are satisfied with your app and ready to deploy it to a production environment, you should switch to using public HTTP request URLs. Read more about getting started with HTTP in [Bolt for Python here](/bolt-python/bolt-python/getting-started).
+Another configuration setting to note is **Socket Mode**. We have turned this on for our local development, but socket mode is not intended for use in a production environment. When you are satisfied with your app and ready to deploy it to a production environment, you should switch to using public HTTP request URLs. Read more about getting started with HTTP in [Bolt for Python here](/bolt-python/getting-started).
 
 Clicking on **Workflow Steps** in the left nav will show you that one workflow step has been added! This reflects the `function` defined in our manifest: functions are workflow steps. We will get to this step's implementation later.
 
diff --git a/docs/english/tutorial/custom-steps.md b/docs/english/tutorial/custom-steps.md
@@ -225,7 +225,7 @@ The second argument is the callback function, or the logic that will run when yo
 
 Field | Description
 ------|------------
-`client` | A `WebClient` instance used to make things happen in Slack. From sending messages to opening modals, `client` makes it all happen. For a full list of available methods, refer to the [Web API methods](/bolt-python/methods). Read more about the `WebClient` for Bolt Python [here](https://docs.slack.dev/bolt-python/concepts/web-api/).
+`client` | A `WebClient` instance used to make things happen in Slack. From sending messages to opening modals, `client` makes it all happen. For a full list of available methods, refer to the [Web API methods](/reference/methods). Read more about the `WebClient` for Bolt Python [here](https://docs.slack.dev/bolt-python/concepts/web-api/).
 `complete` | A utility method that invokes `functions.completeSuccess`. This method indicates to Slack that a step has completed successfully without issue. When called, `complete` requires you include an `outputs` object that matches your step definition in [`output_parameters`](#inputs-outputs).
 `fail` | A utility method that invokes `functions.completeError`. True to its name, this method signals to Slack that a step has failed to complete. The `fail` method requires an argument of `error` to be sent along with it, which is used to help users understand what went wrong.
 `inputs` | An alias for the `input_parameters` that were provided to the step upon execution.
@@ -255,7 +255,7 @@ When you're ready to deploy your steps for wider use, you'll need to decide *whe
 
 ### Control step access {#access}
 
-You can choose who has access to your custom steps. To define this, refer to the [custom function access](/bolt-python/automation/functions/access) page.
+You can choose who has access to your custom steps. To define this, refer to the [custom function access](/deno-slack-sdk/guides/controlling-access-to-custom-functions) page.
 
 ### Distribution {#distribution}
 
@@ -268,5 +268,5 @@ Apps containing custom steps cannot be distributed publicly or submitted to the
 
 ## Related tutorials {#tutorials}
 
-* [Custom steps for Workflow Builder (new app)](/bolt-python/tutorial/custom-steps-WB-new)
-* [Custom steps for Workflow Builder (existing app)](/bolt-python/tutorial/custom-steps-WB-existing)
+* [Custom steps for Workflow Builder (new app)](/bolt-python/tutorial/custom-steps-workflow-builder-new)
+* [Custom steps for Workflow Builder (existing app)](/bolt-python/tutorial/custom-steps-workflow-builder-existing/)
diff --git a/docs/japanese/concepts/app-home.md b/docs/japanese/concepts/app-home.md
@@ -4,11 +4,12 @@ lang: ja-jp
 slug: /bolt-python/concepts/app-home
 ---
 
-<a href="/surfaces/app-home">ホームタブ</a>は、サイドバーや検索画面からアクセス可能なサーフェスエリアです。アプリはこのエリアを使ってユーザーごとのビューを表示することができます。アプリ設定ページで App Home の機能を有効にすると、<a href="/reference/methods/views.publis">`views.publish`</a> API メソッドの呼び出しで `user_id` と[ビューのペイロード](/reference/interaction-payloads/view-interactions-payload/#view_submission)を指定して、ホームタブを公開・更新することができるようになります。
+[ホームタブ](/surfaces/app-home)は、サイドバーや検索画面からアクセス可能なサーフェスエリアです。アプリはこのエリアを使ってユーザーごとのビューを表示することができます。アプリ設定ページで App Home の機能を有効にすると、[`views.publish`](/reference/methods/views.publish) API メソッドの呼び出しで `user_id` と[ビューのペイロード](/reference/interaction-payloads/view-interactions-payload/#view_submission)を指定して、ホームタブを公開・更新することができるようになります。
 
-<a href="/reference/events/app_home_opened">`app_home_opened`</a> イベントをサブスクライブすると、ユーザーが App Home を開く操作をリッスンできます。
+[`app_home_opened`](/reference/events/app_home_opened) イベントをサブスクライブすると、ユーザーが App Home を開く操作をリッスンできます。
+
+指定可能な引数の一覧は [モジュールドキュメント](https://docs.slack.dev/bolt-python/api-docs/slack_bolt/kwargs_injection/args.html)を参考にしてください。
 
-<span>指定可能な引数の一覧は<a href="https://docs.slack.dev/bolt-python/api-docs/slack_bolt/kwargs_injection/args.html">モジュールドキュメント</a>を参考にしてください。</span>
 ```python
 @app.event("app_home_opened")
 def update_home_tab(client, event, logger):
diff --git a/docs/japanese/concepts/custom-steps.md b/docs/japanese/concepts/custom-steps.md
@@ -68,7 +68,7 @@ Example app manifest definition
 
 Your app's custom steps may create interactivity points for users, for example: Post a message with a button.
 
-If such interaction points originate from a custom step execution, the events sent to your app representing the end-user interaction with these points are considered to be _function-scoped interactivity events_. These interactivity events can be handled by your app using the same concepts we covered earlier, such as [Listening to actions](/bolt-python/concepts/action-listening).
+If such interaction points originate from a custom step execution, the events sent to your app representing the end-user interaction with these points are considered to be _function-scoped interactivity events_. These interactivity events can be handled by your app using the same concepts we covered earlier, such as [Listening to actions](/bolt-python/concepts/actions).
 
 _function-scoped interactivity events_ will contain data related to the custom step (`function_executed` event) they were spawned from, such as custom step `inputs` and access to `complete()` and `fail()` listener arguments.
 
diff --git a/docs/japanese/concepts/select-menu-options.md b/docs/japanese/concepts/select-menu-options.md
@@ -4,7 +4,7 @@ lang: ja-jp
 slug: /bolt-python/concepts/options
 ---
 
-`options()` メソッドは、Slack からのオプション（セレクトメニュー内の動的な選択肢）をリクエストするペイロードをリッスンします。 [`action()` と同様に](/bolt-python/concepts/action-listening)、文字列型の `action_id` または制約付きオブジェクトが必要です。
+`options()` メソッドは、Slack からのオプション（セレクトメニュー内の動的な選択肢）をリクエストするペイロードをリッスンします。 [`action()` と同様に](/bolt-python/concepts/actions)、文字列型の `action_id` または制約付きオブジェクトが必要です。
 
 外部データソースを使って選択メニューをロードするためには、末部に `/slack/events` が付加された URL を Options Load URL として予め設定しておく必要があります。
 
diff --git a/docs/japanese/getting-started.md b/docs/japanese/getting-started.md
@@ -164,7 +164,7 @@ import TabItem from '@theme/TabItem';
 
 :::tip 
 
-ローカル開発の場合、ngrok などのプロキシ サービスを使用してパブリック URL を作成し、リクエストを開発環境にトンネリングできます。このトンネルの作成方法については、[ngrok のスタート ガイド](https://ngrok.com/docs#getting-started-expose) を参照してください。アプリをホスティングする際には、Slack 開発者がアプリをホストするために使用する最も一般的なホスティング プロバイダーを [API サイト](/distribution/hosting-slack-apps/) に集めました。
+ローカル開発の場合、ngrok などのプロキシ サービスを使用してパブリック URL を作成し、リクエストを開発環境にトンネリングできます。このトンネルの作成方法については、[ngrok のスタート ガイド](https://ngrok.com/docs#getting-started-expose) を参照してください。アプリをホスティングする際には、Slack 開発者がアプリをホストするために使用する最も一般的なホスティング プロバイダーを [API サイト](/app-management/hosting-slack-apps) に集めました。
 
 :::
 
