admonitions

Author: lukegalbraithrussell

docs/english/concepts/acknowledge.md

@@ -10,9 +10,7 @@ Depending on the type of request, your acknowledgement may be different. For exa
 
 We recommend calling `ack()` right away before initiating any time-consuming processes such as fetching information from your database or sending a new message, since you only have 3 seconds to respond before Slack registers a timeout error.
 
-:::info 
-
-When working in a FaaS / serverless environment, our guidelines for when to `ack()` are different. See the section on [Lazy listeners (FaaS)](/concepts/lazy-listeners) for more detail on this.  
+:::info[When working in a FaaS / serverless environment, our guidelines for when to `ack()` are different. See the section on [Lazy listeners (FaaS)](/concepts/lazy-listeners) for more detail on this.]
 
 :::
 

docs/english/concepts/ai-apps.md

@@ -24,8 +24,10 @@ AI apps comprise a new messaging experience for Slack. If you're unfamiliar with
 * [`assistant_thread_context_changed`](https://docs.slack.dev/reference/events/assistant_thread_context_changed)
 * [`message.im`](https://docs.slack.dev/reference/events/message.im)
 
-:::info
-You _could_ implement your own AI app by [listening](event-listening) for the `assistant_thread_started`, `assistant_thread_context_changed`, and `message.im` events (see implementation details below). That being said, using the `Assistant` class will streamline the process. And we already wrote this nice guide for you!
+:::info[You _could_ implement your own AI app by [listening](event-listening) for the `assistant_thread_started`, `assistant_thread_context_changed`, and `message.im` events (see implementation details below).] 
+
+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}
@@ -101,16 +103,14 @@ 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://tools.slack.dev/bolt-python/api-docs/slack_bolt/kwargs_injection/args.html) to learn the available listener arguments.
+:::tip[Refer to the [module document](https://tools.slack.dev/bolt-python/api-docs/slack_bolt/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 app, the [`assistant_thread_started`](https://docs.slack.dev/reference/events/assistant_thread_started) event will be sent to your app.
 
-:::tip
-When a user opens an AI 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 AI 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 AI app thread {#block-kit-interactions}

docs/english/concepts/message-listening.md

@@ -8,9 +8,7 @@ To listen to messages that [your app has access to receive](https://docs.slack.d
 
 `message()` accepts an argument of type `str` or `re.Pattern` object that filters out any messages that don't match the pattern.
 
-:::info
-
-Refer to [the module document](https://tools.slack.dev/bolt-python/api-docs/slack_bolt/kwargs_injection/args.html) to learn the available listener arguments.
+:::info[Refer to [the module document](https://tools.slack.dev/bolt-python/api-docs/slack_bolt/kwargs_injection/args.html) to learn the available listener arguments.]
 
 :::
 

docs/english/concepts/web-api.md

@@ -8,9 +8,7 @@ You can call [any Web API method](https://docs.slack.dev/reference/methods) usin
 
 The token used to initialize Bolt can be found in the `context` object, which is required to call most Web API methods.
 
-:::info 
-
-Refer to [the module document](https://tools.slack.dev/bolt-python/api-docs/slack_bolt/kwargs_injection/args.html) to learn the available listener arguments.
+:::info[Refer to [the module document](https://tools.slack.dev/bolt-python/api-docs/slack_bolt/kwargs_injection/args.html) to learn the available listener arguments.]
 
 :::
 

docs/english/getting-started.md

@@ -15,9 +15,7 @@ When you're finished, you'll have this ⚡️[Getting Started with Slack app](ht
 ### Create an app {#create-an-app}
 First thing's first: before you start developing with Bolt, you'll want to [create a Slack app](https://api.slack.com/apps/new).
 
-:::tip  
-
-We recommend using a workspace where you won't disrupt real work getting done — [you can create a new one for free](https://slack.com/get-started#create).
+:::tip[We recommend using a workspace where you won't disrupt real work getting done — [you can create a new one for free](https://slack.com/get-started#create).]
 
 :::
 
@@ -55,9 +53,7 @@ We're going to use bot and app-level tokens for this guide.
 
 6. Navigate to **Socket Mode** on the left side menu and toggle to enable. 
 
-:::tip  
-
-Treat your tokens like passwords and [keep them safe](https://docs.slack.dev/authentication/best-practices-for-security). Your app uses tokens to post and retrieve information from Slack workspaces.
+:::tip[Treat your tokens like passwords and [keep them safe](https://docs.slack.dev/authentication/best-practices-for-security). Your app uses tokens to post and retrieve information from Slack workspaces.]
 
 :::
 
@@ -169,9 +165,9 @@ When an event occurs, Slack will send your app some information about the event,
 
 2. Add your Request URL. Slack will send HTTP POST requests corresponding to events to this [Request URL](https://docs.slack.dev/apis/events-api/#subscribing) endpoint. Bolt uses the `/slack/events` path to listen to all incoming requests (whether shortcuts, events, or interactivity payloads). When configuring your Request URL within your app configuration, you'll append `/slack/events`, e.g. `https://<your-domain>/slack/events`. 💡 As long as your Bolt app is still running, your URL should become verified.
 
-:::tip 
+:::tip[For local development, you can use a proxy service like ngrok to create a public URL and tunnel requests to your development environment.] 
 
-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](https://docs.slack.dev/distribution/hosting-slack-apps/). 
+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](https://docs.slack.dev/distribution/hosting-slack-apps/). 
 
 :::
 
@@ -266,9 +262,9 @@ With Socket Mode on, basic interactivity is enabled by default, so no further ac
 
 Similar to events, you'll need to specify a URL for Slack to send the action (such as *user clicked a button*). Back on your app configuration page, click on **Interactivity & Shortcuts** on the left side. You'll see that there's another **Request URL** box.
 
-:::tip 
+:::tip[By default, Bolt is configured to use the same endpoint for interactive components that it uses for events] 
 
-By default, Bolt is configured to use the same endpoint for interactive components that it uses for events, so use the same request URL as above (for example, `https://8e8ec2d7.ngrok.io/slack/events`). Press the **Save Changes** button in the lower right hand corner, and that's it. Your app is set up to handle interactivity!
+Use the same request URL as above (for example, `https://8e8ec2d7.ngrok.io/slack/events`). Press the **Save Changes** button in the lower right hand corner, and that's it. Your app is set up to handle interactivity!
 
 :::
 
@@ -366,9 +362,9 @@ The value inside of `say()` is now an object that contains an array of `blocks`.
 
 You'll notice in the button `accessory` object, there is an `action_id`. This will act as a unique identifier for the button so your app can specify what action it wants to respond to.
 
-:::tip  
+:::tip[The [Block Kit Builder](https://app.slack.com/block-kit-builder) is a simple way to prototype your interactive messages.] 
 
-The [Block Kit Builder](https://app.slack.com/block-kit-builder) is an simple way to prototype your interactive messages. The builder lets you (or anyone on your team) mockup messages and generates the corresponding JSON that you can paste directly in your app.
+The builder lets you (or anyone on your team) mockup messages and generates the corresponding JSON that you can paste directly in your app.
 
 :::
 

docs/english/legacy/steps-from-apps.md

@@ -4,9 +4,7 @@ lang: en
 slug: /legacy/steps-from-apps
 ---
 
-:::danger
-
-Steps from Apps is a deprecated feature.
+:::danger[Steps from Apps is a deprecated feature.]
 
 Steps from Apps are different than, and not interchangeable with, Slack automation workflows. We encourage those who are currently publishing steps from apps to consider the new [Slack automation features](https://docs.slack.dev/workflows/), such as [custom steps for Bolt](https://docs.slack.dev/workflows/workflow-steps).
 

docs/english/tutorial/custom-steps-workflow-builder-new/custom-steps-workflow-builder-new.md

@@ -120,8 +120,7 @@ You'll know the local development server is up and running successfully when it
 
 With your development server running, continue to the next step.
 
-:::info
-If you need to stop running the local development server, press `<CTRL>` + `c` to end the process.
+:::info[If you need to stop running the local development server, press `<CTRL>` + `c` to end the process.]
 :::
 
 ## Wiring up the sample step in Workflow Builder {#wfb}

docs/japanese/getting-started.md

@@ -16,9 +16,7 @@ lang: ja-jp
 ### アプリを作成する {#create-an-app}
 最初にやるべきこと : Bolt での開発を始める前に、[Slack アプリを作成](https://api.slack.com/apps/new)します。
 
-:::tip 
-
-通常の業務の妨げにならないよう、別の開発用のワークスペースを使用することをおすすめします。[新しいワークスペースは無料で作成できます](https://slack.com/get-started#create)
+:::tip[通常の業務の妨げにならないよう、別の開発用のワークスペースを使用することをおすすめします。[新しいワークスペースは無料で作成できます](https://slack.com/get-started#create)]
 
 :::
 
@@ -56,9 +54,7 @@ Slack アプリで使用できるトークンには、ユーザートークン
 
 6. 左サイドメニューの「**Socket Mode**」を有効にします。
 
-:::tip
-
-トークンはパスワードと同様に取り扱い、[安全な方法で保管してください](https://docs.slack.dev/authentication/best-practices-for-security)。アプリはこのトークンを使って Slack ワークスペースで投稿をしたり、情報の取得をしたりします。
+:::tip[トークンはパスワードと同様に取り扱い、[安全な方法で保管してください](https://docs.slack.dev/authentication/best-practices-for-security)。アプリはこのトークンを使って Slack ワークスペースで投稿をしたり、情報の取得をしたりします。]
 
 :::
 
@@ -99,9 +95,9 @@ export SLACK_BOT_TOKEN=xoxb-<ボットトークン>
 ```shell
 export SLACK_APP_TOKEN=<アプリレベルトークン>
 ```
-:::warning
+:::warning[🔒 全てのトークンは安全に保管してください。]
 
-🔒 全てのトークンは安全に保管してください。少なくともパブリックなバージョン管理にチェックインするようなことは避けるべきでしょう。また、上にあった例のように環境変数を介してアクセスするようにしてください。詳細な情報は [アプリのセキュリティのベストプラクティス](https://docs.slack.dev/authentication/best-practices-for-security)のドキュメントを参照してください。
+少なくともパブリックなバージョン管理にチェックインするようなことは避けるべきでしょう。また、上にあった例のように環境変数を介してアクセスするようにしてください。詳細な情報は [アプリのセキュリティのベストプラクティス](https://docs.slack.dev/authentication/best-practices-for-security)のドキュメントを参照してください。
 
 :::
 
@@ -359,9 +355,9 @@ if __name__ == "__main__":
 
 ボタンを含む `accessory` オブジェクトでは、`action_id` を指定していることがわかります。これは、ボタンを一意に示す識別子として機能します。これを使って、アプリをどのアクションに応答させるかを指定できます。
 
-:::tip
+:::tip[[Block Kit Builder](https://app.slack.com/block-kit-builder) を使用すると、インタラクティブなメッセージのプロトタイプを簡単に作成できます。]
 
-[Block Kit Builder](https://app.slack.com/block-kit-builder) を使用すると、インタラクティブなメッセージのプロトタイプを簡単に作成できます。自分自身やチームメンバーがメッセージのモックアップを作成し、生成される JSON をアプリに直接貼りつけることができます。
+自分自身やチームメンバーがメッセージのモックアップを作成し、生成される JSON をアプリに直接貼りつけることができます。
 
 :::