reference full links

Author: lukegalbraithrussell

docs/english/building-an-app.md

@@ -207,7 +207,7 @@ app = App(token=os.environ.get("SLACK_BOT_TOKEN"))
 
 # Listens to incoming messages that contain "hello"
 # To learn available listener arguments,
-# visit https://docs.slack.dev/bolt-python/reference/kwargs_injection/args.html
+# visit https://docs.slack.dev/tools/bolt-python/reference/kwargs_injection/args.html
 @app.message("hello")
 def message_hello(message, say):
     # say() sends a message to the channel where the event was triggered
@@ -233,7 +233,7 @@ app = App(
 
 # Listens to incoming messages that contain "hello"
 # To learn available listener arguments,
-# visit https://docs.slack.dev/bolt-python/reference/kwargs_injection/args.html
+# visit https://docs.slack.dev/tools/bolt-python/reference/kwargs_injection/args.html
 @app.message("hello")
 def message_hello(message, say):
     # say() sends a message to the channel where the event was triggered

docs/english/concepts/acknowledge.md

@@ -10,7 +10,7 @@ We recommend calling `ack()` right away before initiating any time-consuming pro
 
 :::
 
-Refer to [the module document](https://docs.slack.dev/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
+Refer to [the module document](https://docs.slack.dev/tools/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
 ```python
 # Example of responding to an external_select options request
 @app.options("menu_selection")

docs/english/concepts/actions.md

@@ -8,7 +8,7 @@ Actions can be filtered on an `action_id` parameter of type `str` or `re.Pattern
 
 You'll notice in all `action()` examples, `ack()` is used. It is required to call the `ack()` function within an action listener to acknowledge that the request was received from Slack. This is discussed in the [acknowledging requests guide](/tools/bolt-python/concepts/acknowledge).
 
-Refer to [the module document](https://docs.slack.dev/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
+Refer to [the module document](https://docs.slack.dev/tools/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
 
 ```python
 # Your listener will be called every time a block element with the action_id "approve_button" is triggered
@@ -45,7 +45,7 @@ There are two main ways to respond to actions. The first (and most common) way i
 
 The second way to respond to actions is using `respond()`, which is a utility to use the `response_url` associated with the action.
 
-Refer to [the module document](https://docs.slack.dev/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
+Refer to [the module document](https://docs.slack.dev/tools/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
 
 ```python
 # Your listener will be called every time an interactive component with the action_id “approve_button” is triggered

docs/english/concepts/ai-apps.md

@@ -24,10 +24,6 @@ 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](/tools/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}
 
 The `Assistant` class can be used to handle the incoming events expected from a user interacting with an app in Slack that has the Agents & AI Apps feature enabled. A typical flow would look like:
@@ -101,15 +97,16 @@ While the `assistant_thread_started` and `assistant_thread_context_changed` even
 
 If you do provide your own `threadContextStore` property, it must feature `get` and `save` methods.
 
-:::tip[Refer to the [module document](https://docs.slack.dev/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.]
+:::tip[Refer to the [module document](https://docs.slack.dev/tools/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.]
 :::
 
 ## Handling a new thread {#handling-a-new-thread}
 
 When the user opens a new thread with your AI-enabled app, the [`assistant_thread_started`](/reference/events/assistant_thread_started) event will be sent to your app.
 
-:::tip
-When a user opens an app thread while in a channel, the channel info is stored as the thread's `AssistantThreadContext` data. You can grab that info by using the `get_thread_context` utility, as subsequent user message event payloads won't include the channel info.
+:::tip[When a user opens an app thread while in a channel, the channel info is stored as the thread's `AssistantThreadContext` data.] 
+
+You can grab that info by using the `get_thread_context` utility, as subsequent user message event payloads won't include the channel info.
 :::
 
 ### Block Kit interactions in the app thread {#block-kit-interactions}
@@ -260,9 +257,9 @@ When the user messages your app, the [`message.im`](/reference/events/message.im
 Messages sent to the app do not contain a [subtype](/reference/events/message#subtypes) and must be deduced based on their shape and any provided [message metadata](/messaging/message-metadata/).
 
 There are three utilities that are particularly useful in curating the user experience:
-* [`say`](https://docs.slack.dev/bolt-python/reference/#slack_bolt.Say)
-* [`setTitle`](https://docs.slack.dev/bolt-python/reference/#slack_bolt.SetTitle)
-* [`setStatus`](https://docs.slack.dev/bolt-python/reference/#slack_bolt.SetStatus)
+* [`say`](https://docs.slack.dev/tools/bolt-python/reference/#slack_bolt.Say)
+* [`setTitle`](https://docs.slack.dev/tools/bolt-python/reference/#slack_bolt.SetTitle)
+* [`setStatus`](https://docs.slack.dev/tools/bolt-python/reference/#slack_bolt.SetStatus)
 
 ```python
 ...

docs/english/concepts/app-home.md

@@ -4,7 +4,7 @@
 
 You can subscribe to the [`app_home_opened`](/reference/events/app_home_opened) event to listen for when users open your App Home.
 
-Refer to [the module document](https://docs.slack.dev/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
+Refer to [the module document](https://docs.slack.dev/tools/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
 ```python
 @app.event("app_home_opened")
 def update_home_tab(client, event, logger):

docs/english/concepts/commands.md

@@ -8,7 +8,7 @@ There are two ways to respond to slash commands. The first way is to use `say()`
 
 When setting up commands within your app configuration, you'll append `/slack/events` to your request URL.
 
-Refer to [the module document](https://docs.slack.dev/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
+Refer to [the module document](https://docs.slack.dev/tools/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
 ```python
 # The echo command simply echoes on command
 @app.command("/echo")

docs/english/concepts/custom-steps-dynamic-options.md

@@ -214,7 +214,7 @@ A new `auto_acknowledge` flag allows you more granular control over whether spec
 
 #### Example {#bolt-py}
 
-In [Bolt for Python](https://docs.slack.dev/bolt-python/), you can set `auto_acknowledge=False` on a specific function decorator. This allows you to manually control when the `ack()` event acknowledgement helper function is executed. It flips Bolt to synchronous `function_executed` event handling mode for the specific handler. 
+In [Bolt for Python](https://docs.slack.dev/tools/bolt-python/), you can set `auto_acknowledge=False` on a specific function decorator. This allows you to manually control when the `ack()` event acknowledgement helper function is executed. It flips Bolt to synchronous `function_executed` event handling mode for the specific handler. 
 
 ```py
 @app.function("get-projects", auto_acknowledge=False)

docs/english/concepts/custom-steps.md

@@ -11,7 +11,7 @@ Your app can use the `function()` method to listen to incoming [custom step requ
 
 You can reference your custom step's inputs using the `inputs` listener argument of type `dict`.
 
-Refer to [the module document](https://docs.slack.dev/bolt-python/reference/kwargs_injection/args.html) to learn about the available listener arguments.
+Refer to [the module document](https://docs.slack.dev/tools/bolt-python/reference/kwargs_injection/args.html) to learn about the available listener arguments.
 
 ```python
 # This sample custom step formats an input and outputs it

docs/english/concepts/event-listening.md

@@ -4,7 +4,7 @@ You can listen to [any Events API event](/reference/events) using the `event()`
 
 The `event()` method requires an `eventType` of type `str`.
 
-Refer to [the module document](https://docs.slack.dev/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
+Refer to [the module document](https://docs.slack.dev/tools/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
 ```python
 # When a user joins the workspace, send a message in a predefined channel asking them to introduce themselves
 @app.event("team_join")

docs/english/concepts/global-middleware.md

@@ -4,7 +4,7 @@ Global middleware is run for all incoming requests, before any listener middlewa
 
 Both global and listener middleware must call `next()` to pass control of the execution chain to the next middleware. 
 
-Refer to [the module document](https://docs.slack.dev/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
+Refer to [the module document](https://docs.slack.dev/tools/bolt-python/reference/kwargs_injection/args.html) to learn the available listener arguments.
 ```python
 @app.use
 def auth_acme(client, context, logger, payload, next):