Fix minor errors in documents

Author: seratch

docs/_advanced/adapters.md

@@ -10,7 +10,7 @@ Adapters are responsible for handling and parsing incoming events from Slack to
 
 By default, Bolt will use the built-in <a href="https://docs.python.org/3/library/http.server.html">`HTTPSever`</a> adapter. While this is okay for local development, <b>it is not recommended for production</b>. Bolt for Python includes a collection of built-in adapters that can be imported and used with your app. The built-in adapters support a variety of popular Python frameworks including Flask, Django, and Starlette among others. Adapters support the use of any production-ready web server of your choice.
 
-To use an adapter, you'll create an app with the framework of your choosing and import its corresponding adapter. Then you'll initalize the adapter instance and call its function that handles and parses incoming events.
+To use an adapter, you'll create an app with the framework of your choosing and import its corresponding adapter. Then you'll initialize the adapter instance and call its function that handles and parses incoming events.
 
 The full list adapters, as well as configuration and sample usage, can be found within the repository's <a href="https://github.com/slackapi/bolt-python/tree/main/examples">`examples` folder</a>.
 </div>

docs/_advanced/authorization.md

@@ -22,8 +22,8 @@ For a more custom solution, you can set the `authorize` parameter to a function
 ```python
 import os
 from slack_bolt import App
-# Import the AuthorizationResult class
-from slack_bolt.authorization import AuthorizationResult
+# Import the AuthorizeResult class
+from slack_bolt.authorization import AuthorizeResult
 
 # This is just an example (assumes there are no user tokens)
 # You should store authorizations in a secure DB
@@ -46,7 +46,7 @@ installations = [
 
 def authorize(enterprise_id, team_id, logger):
     # You can implement your own logic to fetch token here
-    for (team in installations):
+    for team in installations:
         # enterprise_id doesn't exist for some teams
         is_valid_enterprise = True if (("enterprise_id" not in team) or (enterprise_id == team["enterprise_id"])) else False
         if ((is_valid_enterprise == True) and (team["team_id"] == team_id)):

docs/_advanced/custom_adapters.md

@@ -18,7 +18,7 @@ order: 1
 | `body: str` | The raw request body | **Yes** |
 | `query: any` | The query string data | No |
 | `headers: Dict[str, Union[str, List[str]]]` | Request headers | No |
-| `context: Dict[str, str]` | Any context for the request | No |
+| `context: BoltContext` | Any context for the request | No |
 
 `BoltRequest` will return [an instance of `BoltResponse`](https://github.com/slackapi/bolt-python/blob/main/slack_bolt/response/response.py) from the Bolt app.
 

docs/_advanced/lazy_listener.md

@@ -12,7 +12,7 @@ Typically you'd call `ack()` as the first step of your listener functions. Calli
 
 However, apps running on FaaS or similar runtimes that don't allow you to run threads or processes after returning an HTTP response cannot follow this pattern. Instead, you should set the `process_before_response` flag to `True`. This allows you to create a listener that calls `ack()` and handles the event safely, though you still need to complete everything within 3 seconds. For events, while a listener doesn't need `ack()` method call as you normally would, the listener needs to complete within 3 seconds, too.
 
-Rather than acting as a decorator, lazy listeners take two keyword args:
+Lazy listeners can be a solution for this issue. Rather than acting as a decorator, lazy listeners take two keyword args:
 * `ack: Callable`: Responsible for calling `ack()`
 * `lazy: List[Callable]`: Responsible for handling any time-consuming processes related to the event. The lazy function does not have access to `ack()`.
 </div>

docs/_basic/authenticating_oauth.md

@@ -19,6 +19,7 @@ To learn more about the OAuth installation flow with Slack, [read the API docume
 
 ```python
 import os
+from slack_bolt import App
 from slack_bolt.oauth.oauth_settings import OAuthSettings
 from slack_sdk.oauth.installation_store import FileInstallationStore
 from slack_sdk.oauth.state_store import FileOAuthStateStore
@@ -55,7 +56,7 @@ You can override the default OAuth using `oauth_settings`, which can be passed i
 
 ```python
 from slack_bolt.oauth.callback_options import CallbackOptions, SuccessArgs, FailureArgs
-import slack_bolt.response.BoltResponse
+from slack_bolt.response import BoltResponse
 
 def success(args: SuccessArgs) -> BoltResponse:
     assert args.request is not None
@@ -74,6 +75,12 @@ def failure(args: FailureArgs) -> BoltResponse:
 
 callback_options = CallbackOptions(success=success, failure=failure)
 
+import os
+from slack_bolt import App
+from slack_bolt.oauth.oauth_settings import OAuthSettings
+from slack_sdk.oauth.installation_store import FileInstallationStore
+from slack_sdk.oauth.state_store import FileOAuthStateStore
+
 app = App(
     signing_secret=os.environ.get("SLACK_SIGNING_SECRET"),
     installation_store=FileInstallationStore(base_dir="./data"),

docs/_basic/listening_messages.md

@@ -7,7 +7,7 @@ order: 1
 
 <div class="section-content">
 
-To listen to messages that [your app has access to receive](https://api.slack.com/messaging/retrieving#permissions), you can use the `message()` method which filters out events that aren’t of type `message`.
+To listen to messages that [your app has access to receive](https://api.slack.com/messaging/retrieving#permissions), you can use the `message()` method which filters out events that aren't of type `message`.
 
 `message()` accepts an argument of type `str` or `re.Pattern` object that filters out any messages that don’t match the pattern.
 
@@ -33,6 +33,8 @@ The `re.compile()` method can be used instead of a string for more granular matc
 </div>
 
 ```python
+import re
+
 @app.message(re.compile("(hi|hello|hey)"))
 def say_hello_regex(say, context):
     # regular expression matches are inside of context.matches