copy editing updates

Author: haleychaas

docs/content/guides/ai-apps.md

@@ -13,14 +13,14 @@ AI apps comprise a new messaging experience for Slack. If you're unfamiliar with
 
 ## Configuring your app to support AI apps features {#configuring-your-app}
 
-1. Within [App Settings](https://api.slack.com/apps), enable the **Agents & AI Apps** feature.
+1. Within [app settings](https://api.slack.com/apps), enable the **Agents & AI Apps** feature.
 
-2. Within the App Settings **OAuth & Permissions** page, add the following scopes: 
+2. Within the app settings **OAuth & Permissions** page, add the following scopes: 
   * [`assistant:write`](https://docs.slack.dev/reference/scopes/assistant.write)
   * [`chat:write`](https://docs.slack.dev/reference/scopes/chat.write)
   * [`im:history`](https://docs.slack.dev/reference/scopes/im.history)
 
-3. Within the App Settings **Event Subscriptions** page, subscribe to the following events: 
+3. Within the app settings **Event Subscriptions** page, subscribe to the following events: 
   * [`assistant_thread_started`](https://docs.slack.dev/reference/events/assistant_thread_started)
   * [`assistant_thread_context_changed`](https://docs.slack.dev/reference/events/assistant_thread_context_changed)
   * [`message.im`](https://docs.slack.dev/reference/events/message.im)
@@ -75,15 +75,15 @@ While the `assistant_thread_started` and `assistant_thread_context_changed` even
 
 If you do provide your own `threadContextService` property, it must feature `get` and `save` methods.
 
-:::tip
+:::tip[Tip]
 Be sure to give the [AI apps reference docs](/reference#agents--assistants) a look!
 :::
 
 ## 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
+:::tip[Tip]
 When a user opens a thread with your app while in a channel, the channel info is stored as the thread's `AssistantThreadContext` data. You can grab that info by using the `context.getThreadContext()` utility, as subsequent user message event payloads won't include the channel info.
 :::
 

docs/content/guides/app-distribution.md

@@ -6,11 +6,11 @@ lang: en
 
 An [App Home](https://docs.slack.dev/surfaces/app-home) is a private, one-to-one space in Slack shared by a user and an app. Each App Home contains a number of tabbed surfaces, including a Messages tab for app-user conversation, and a Home tab that can be fully customized by the app.
 
-### Slack App Configuration
+### Slack app configuration
 
-To enable Home tabs, visit the [Slack App configuration page](http://api.slack.com/apps), choose the app you're working on, go to **Features** > **App Home** on the left pane, and then turn on **Home Tab**.
+To enable Home tabs, visit the [Slack app settings page](http://api.slack.com/apps), choose the app you're working on, go to **Features** > **App Home** on the left pane, and then turn on **Home Tab**.
 
-To enable Events API, go to **Features** > **Event Subscriptions** on the left pane. There are a few things to do on the page.
+To enable the Events API, go to **Features** > **Event Subscriptions** on the left pane. There are a few things to do on the page.
 
 * Turn on **Enable Events**
 * Set the **Request URL** to `https://{your app's public URL domain}/slack/events` (this step is not required for Socket Mode apps)
@@ -20,25 +20,25 @@ To enable Events API, go to **Features** > **Event Subscriptions** on the left p
   * Choose **app_home_opened** event
 * Click the **Save Changes** button at the bottom for sure
 
-### What Your Bolt App Does
+### What your Bolt app does
 
-All your app needs to do to provide Home tabs to your app users are:
+To provide Home tabs to your app users:
 
-1. Call the [**views.publish**](https://docs.slack.dev/reference/methods/views.publish) method to update the Home tab on a per-user basis
-2. Handle any user interactions in Home tab (`"block_actions"`, `"block_suggestion"`)
+1. Call the [`views.publish`](https://docs.slack.dev/reference/methods/views.publish) method to update the Home tab on a per-user basis
+2. Handle any user interactions in Home tab (`block_actions`, `block_suggestion`)
 
-Most commonly, [`"app_home_opened"`](https://docs.slack.dev/reference/events/app_home_opened) events would be used as the trigger to call the [**views.publish**](https://docs.slack.dev/reference/methods/views.publish) method. Subscribing this event type is useful particularly for the initial Home tab creation. But it's also fine to publish Home tabs by any other means.
+Most commonly, [`app_home_opened`](https://docs.slack.dev/reference/events/app_home_opened) events would be used as the trigger to call the [`views.publish`](https://docs.slack.dev/reference/methods/views.publish) method. Subscribing this event type is useful particularly for the initial Home tab creation. But it's also fine to publish Home tabs by any other means.
 
 ---
 ## Examples
 
-:::tip 
+:::tip[Tip]
 
 If you're a beginner to using Bolt for Slack App development, consult [Getting Started with Bolt](/guides/getting-started-with-bolt), first.
 
 :::
 
-The following code calls [**views.publish**](https://docs.slack.dev/reference/methods/views.publish) method when receiving an [`"app_home_opened"` events](https://docs.slack.dev/reference/events/app_home_opened) for the user that triggered the event. The user will see the updated Home tab immediately after the [**views.publish**](https://docs.slack.dev/reference/methods/views.publish) call has been successfully completed.
+The following code calls the [`views.publish`](https://docs.slack.dev/reference/methods/views.publish) method when receiving an [`app_home_opened`](https://docs.slack.dev/reference/events/app_home_opened) event for the user that triggered the event. The user will see the updated Home tab immediately after the [`views.publish`](https://docs.slack.dev/reference/methods/views.publish) call has been successfully completed.
 
 ```java
 import com.slack.api.methods.response.views.ViewsPublishResponse;
@@ -78,7 +78,7 @@ app.event(AppHomeOpenedEvent.class, (payload, ctx) -> {
 });
 ```
 
-It looks like as below in Kotlin. (New to Kotlin? [Getting Started in Kotlin](/guides/getting-started-with-bolt#getting-started-in-kotlin) may be helpful)
+It looks like this in Kotlin. (New to Kotlin? [Getting Started in Kotlin](/guides/getting-started-with-bolt#getting-started-in-kotlin) may be helpful.)
 
 ```kotlin
 // static imports
@@ -130,6 +130,6 @@ val appHomeView = view { it
 }
 ```
 
-### Under the Hood
+## Under the hood
 
 Refer to [the Events API guide](/guides/events-api).

docs/content/guides/app-home.md

@@ -4,16 +4,16 @@ lang: en
 
 # Audit Logs API
 
-[Audit Logs API](https://api.lack.com/docs/audit-logs-api) is a set of APIs for monitoring what's happening in your [Enterprise Grid](https://docs.slack.dev/enterprise-grid/) organization.
+The [Audit Logs API](https://api.lack.com/docs/audit-logs-api) is used for monitoring what is happening in your [Enterprise Grid](https://docs.slack.dev/enterprise-grid/) organization.
 
 The Audit Logs API can be used by security information and event management (SIEM) tools to provide an analysis of how your Slack organization is being accessed. You can also use this API to write your own applications to see how members of your organization are using Slack.
 
-Follow the instructions in [the API document](https://docs.slack.dev/admins/audit-logs-api) to get a valid token for using Audit Logs API. Your Slack app for Audit Logs API needs to be installed on the Enterprise Grid Organization, not an individual workspace within the organization.
+Follow the instructions in [the API documentation](https://docs.slack.dev/admins/audit-logs-api) to get a valid token for using the Audit Logs API. Your Slack app used for accessing the Audit Logs API needs to be installed at the org level on the Enterprise Grid organization, not an individual workspace within the organization.
 
 ---
-## Call Audit Logs API in Java
+## Call the Audit Logs API in Java
 
-It's straight-forward to call Audit Logs API using the `slack-api-client` library.
+Use the `slack-api-client` library to call the Audit Logs API.
 
 ```java
 import com.slack.api.Slack;
@@ -24,17 +24,17 @@ String token = System.getenv("SLACK_ADMIN_ACCESS_TOKN"); // `auditlogs:read` sco
 AuditClient audit = slack.audit(token);
 ```
 
-All the endpoints are supported.
+All of the endpoints are supported.
 
 |Java Method|Endpoint|
 |-|-|
 |`AuditClient#getLogs()`|`GET /logs`|
 |`AuditClient#getSchemas()`|`GET /schemas`|
 |`AuditClient#getActions()`|`GET /actions`|
 
-### getLogs()
+### `getLogs()`
 
-This is the primary endpoint for retrieving actual audit events from your organization. It will return a list of actions that have occurred on the installed workspace or grid organization. Authentication required.
+This is the primary endpoint for retrieving actual audit events from your organization. It will return a list of actions that have occurred on the installed workspace or grid organization. Authentication is required.
 
 ```java
 import com.slack.api.audit.response.LogsResponse;
@@ -46,45 +46,43 @@ LogsResponse response = audit.getLogs(req -> req
 );
 ```
 
-Refer to [Javadoc](https://oss.sonatype.org/service/local/repositories/releases/archive/com/slack/api/slack-api-client/sdkLatestVersion/slack-api-client-sdkLatestVersion-javadoc.jar/!/com/slack/api/audit/response/LogsResponse.html) to know the response data structure.
+Refer to the [Javadoc](https://oss.sonatype.org/service/local/repositories/releases/archive/com/slack/api/slack-api-client/sdkLatestVersion/slack-api-client-sdkLatestVersion-javadoc.jar/!/com/slack/api/audit/response/LogsResponse.html) to know the response data structure.
 
-### getSchemas()
+### `getSchemas()`
 
-This endpoint returns information about the kind of objects which the Audit Logs API returns as a list of all objects and a short description. Authentication not required.
+This endpoint returns information about the kind of objects, which the Audit Logs API returns as a list of all objects and a short description. Authentication is not required.
 
 ```java
 import com.slack.api.audit.response.SchemasResponse;
 
 SchemasResponse response = audit.getSchemas();
 ```
 
-Refer to [Javadoc](https://oss.sonatype.org/service/local/repositories/releases/archive/com/slack/api/slack-api-client/sdkLatestVersion/slack-api-client-sdkLatestVersion-javadoc.jar/!/com/slack/api/audit/response/SchemasResponse.html) to know the response data structure.
+Refer to the [Javadoc](https://oss.sonatype.org/service/local/repositories/releases/archive/com/slack/api/slack-api-client/sdkLatestVersion/slack-api-client-sdkLatestVersion-javadoc.jar/!/com/slack/api/audit/response/SchemasResponse.html) to know the response data structure.
 
-### getActions()
+### `getActions()`
 
-This endpoint returns information about the kind of actions that the Audit Logs API returns as [a list of all actions](https://oss.sonatype.org/service/local/repositories/releases/archive/com/slack/api/slack-api-client/sdkLatestVersion/slack-api-client-sdkLatestVersion-javadoc.jar/!/com/slack/api/audit/Actions.html) and a short description of each. Authentication not required.
+This endpoint returns information about the kind of actions that the Audit Logs API returns as [a list of all actions](https://oss.sonatype.org/service/local/repositories/releases/archive/com/slack/api/slack-api-client/sdkLatestVersion/slack-api-client-sdkLatestVersion-javadoc.jar/!/com/slack/api/audit/Actions.html) and a short description of each. Authentication is not required.
 
 ```java
 import com.slack.api.audit.response.ActionsResponse;
 
 ActionsResponse response = audit.getActions();
 ```
 
-Refer to [Javadoc](https://oss.sonatype.org/service/local/repositories/releases/archive/com/slack/api/slack-api-client/sdkLatestVersion/slack-api-client-sdkLatestVersion-javadoc.jar/!/com/slack/api/audit/response/ActionsResponse.html) to know the response data structure.
+Refer to the [Javadoc](https://oss.sonatype.org/service/local/repositories/releases/archive/com/slack/api/slack-api-client/sdkLatestVersion/slack-api-client-sdkLatestVersion-javadoc.jar/!/com/slack/api/audit/response/ActionsResponse.html) to know the response data structure.
 
 
 ---
-## Rate Limits
+## Rate limits
 
-The Audit Logs API methods conform to Slack's [rate limits](https://docs.slack.dev/apis/web-api/rate-limits) and all methods are rated Tier 3. This allows for up to 50 calls per minute, with an allowance for sporadic bursts. Refer to [the API document](https://docs.slack.dev/admins/audit-logs-api) for more details.
+The Audit Logs API methods conform to Slack's [rate limits](https://docs.slack.dev/apis/web-api/rate-limits) and all methods are rated Tier 3. This allows for up to 50 calls per minute, with an allowance for sporadic bursts. Refer to [the API documentation](https://docs.slack.dev/admins/audit-logs-api) for more details.
 
-`AsyncAuditClient`, the async client, has great consideration for Rate Limits.
+The async client, `AsyncAuditClient`, has great consideration for rate limits. The async client internally has its queue systems to avoid burst traffics as much as possible while `AuditClient`, the synchronous client, always blindly sends requests. Both sync and async clients maintain the metrics data in a `MetricsDatastore` together. This allows the async client to accurately know the current traffic they generated toward the Slack platform and estimate the remaining amount to call.
 
-The async client internally has its queue systems to avoid burst traffics as much as possible while `AuditClient`, the synchronous client, always blindly sends requests. The good thing is that both sync and async clients maintain the metrics data in a `MetricsDatastore` together. This allows the async client to accurately know the current traffic they generated toward the Slack Platform and estimate the remaining amount to call.
+The default implementation of the datastore is an in-memory one using the JVM heap memory. The default `SlackConfig` enables the in-memory one. 
 
-The default implementation of the datastore is in-memory one using the JVM heap memory. The default `SlackConfig` enables the in-memory one. It should work nicely for most cases. If your app is fine with it, you don't need to configure anything.
-
-`AsyncAuditClient` considers the metrics data very well. It may delay API requests to avoid rate-limited errors if the clients in the app already sent too many requests within a short period.
+The `AsyncAuditClient` considers the metrics data well. It may delay API requests to avoid rate-limited errors if the clients in the app already sent too many requests within a short period.
 
 ```java
 import com.slack.api.audit.*;