pr feedback

Author: haleychaas

docs/content/guides/app-distribution.md

@@ -19,9 +19,9 @@ Bolt for Java automatically includes support for [org-wide installations](https:
 
 ### What your Bolt app does
 
-To properly handle the OAuth Flow:
+To properly handle the OAuth flow:
 
-* Provide an endpoint starting the OAuth flow by redirecting installers to Slack's `authorize` endpoint with sufficient parameters
+* Provide an endpoint starting the OAuth flow by redirecting installers to the `authorize` endpoint with sufficient parameters
   * Generate a `state` parameter value to verify afterwards
   * Append `client_id`, `scope`, `user_scope` (only for v2), and `state` to the URL
 * Provide an endpoint to handle user redirection from Slack

docs/content/guides/audit-logs-api.md

@@ -78,7 +78,7 @@ Refer to the [Javadoc](https://oss.sonatype.org/service/local/repositories/relea
 
 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.
 
-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, `AsyncAuditClient`, takes rate limits into consideration. 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 default implementation of the datastore is an in-memory one using the JVM heap memory. The default `SlackConfig` enables the in-memory one. 
 

docs/content/guides/bolt-basics.md

@@ -154,7 +154,7 @@ app.command("/hello", (req, ctx) -> {
 ---
 ## Use Web APIs / reply using `say` utility
 
-Use `ctx.client()` to call Slack Web API methods in Bolt apps. The `MethodsClient` created by the method already holds a valid bot token, so there is no need to provide a token to it. Simply call the method with parameters as below.
+Use `ctx.client()` to call Slack Web API methods in Bolt apps. The `MethodsClient` created by the method already holds a valid bot token, so there is no need to provide a token to it. Call the method with parameters as below.
 
 ```java
 app.command("/hello", (req, ctx) -> {

docs/content/guides/composing-messages.md

@@ -29,7 +29,7 @@ ChatPostMessageResponse response = slack.methods(token).chatPostMessage(req -> r
 );
 ```
 
-As you see, using `text` is fairly simple: give a string value with a valid format. Consult [Basic formatting with `mrkdwn`](https://docs.slack.dev/messaging/formatting-message-text) for understanding the markup language.
+Use `text` by providing a string value with a valid format. Consult [Basic formatting with `mrkdwn`](https://docs.slack.dev/messaging/formatting-message-text) for understanding the markup language.
 
 ---
 ## Building blocks for rich message layouts
@@ -67,7 +67,7 @@ ChatPostMessageResponse response = slack.methods(token).chatPostMessage(req -> r
 );
 ```
 
-You build a message for incoming webhooks and `response_url` calls this way too.
+You can build a message for incoming webhooks and `response_url` calls this way too.
 
 ---
 ## Block Kit Kotlin DSL

docs/content/guides/events-api.md

@@ -141,7 +141,7 @@ app.message(":wave:", (payload, ctx) -> {
 
 ## Under the hood
 
-If you hope to understand what is happening with the above code, reading the following (a bit pseudo) code may be helpful.
+If you hope to understand what is happening with the above code, reading the following (pseudo) code may be helpful.
 
 ```java
 import java.util.Map;

docs/content/guides/getting-started-with-bolt.md

@@ -231,7 +231,7 @@ run {
 <Tabs groupId="socket-or-http">
 <TabItem value="socket-mode" label="Socket Mode">
 
-Only single source code is required to run your first Bolt app. All you need to do is define the main method that starts `SocketModeApp`.
+Only single source code is required to run your first Bolt app. You'll need to define the main method that starts `SocketModeApp`.
 
 ```java
 package hello;
@@ -254,7 +254,7 @@ public class MyApp {
 }
 ```
 
-If you go with JDK 10+, thanks to [Local Variable Type Inference](https://docs.oracle.com/en/java/javase/21/language/local-variable-type-inference.html), your code could be much more concise. To take advantage of it, install OpenJDK 11 and set the compatible Java versions in `build.gradle` as below. Also, configure the same on your IDE.
+If you go with JDK 10+, thanks to [Local Variable Type Inference](https://docs.oracle.com/en/java/javase/21/language/local-variable-type-inference.html), you can write more concise code. To do so, install OpenJDK 11 and set the compatible Java versions in `build.gradle` as below, configuring the same on your IDE.
 
 ```groovy
 java {
@@ -276,7 +276,7 @@ new SocketModeApp(app).start();
 </TabItem>
 <TabItem value="http" label="HTTP">
 
-Only single source code is required to run your first Bolt app. All you need to do is define the main method that starts `SlackAppServer`. Your server with the default configuration will listen to the 3000 port but it's configurable. Check other constructors of the class to customize the behavior.
+Only single source code is required to run your first Bolt app. You'll need to define the main method that starts `SlackAppServer`. Your server with the default configuration will listen to the 3000 port but it's configurable. Check other constructors of the class to customize the behavior.
 
 ```java
 package hello;
@@ -300,7 +300,7 @@ public class MyApp {
 }
 ```
 
-If you go with JDK 10+, thanks to [Local Variable Type Inference](https://docs.oracle.com/en/java/javase/21/language/local-variable-type-inference.html), your code could be much more concise. To take advantage of it, install OpenJDK 11 and set the compatible Java versions in `build.gradle` as below. Also, configure the same on your IDE.
+If you go with JDK 10+, thanks to [Local Variable Type Inference](https://docs.oracle.com/en/java/javase/21/language/local-variable-type-inference.html), you can write more concise code. To do so, install OpenJDK 11 and set the compatible Java versions in `build.gradle` as below, configuring the same on your IDE.
 
 ```groovy
 java {
@@ -423,7 +423,7 @@ Now you can hit the `/hello` command in your development workspace. If your app
 
 As [Spring Boot](https://spring.io/projects/spring-boot) is one of the most popular web frameworks in the Java world, you may be curious about the possibility to let this Bolt app live together with it.
 
-Rest assured, we can _inject_ Bolt into Spring Boot apps.
+Don't worry, we can _inject_ Bolt into Spring Boot apps.
 
 Add `implementation("com.slack.api:bolt:sdkLatestVersion")` to `dependencies` in `build.gradle` and write a few lines of code.
 

docs/content/guides/incoming-webhooks.md

@@ -4,7 +4,7 @@ lang: en
 
 # Incoming webhooks
 
-[Incoming webhooks](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks) are a simple way to post messages from apps into Slack. Creating an incoming webhook gives you a unique URL to which you send a JSON payload with the message and some options.
+[Incoming webhooks](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks) are a straightforward way to post messages from apps into Slack. Creating an incoming webhook gives you a unique URL to which you send a JSON payload with the message and some options.
 
 ### Slack app configuration