diff --git a/docs/_site/concepts.html b/docs/_site/concepts.html
index a6f3c89a2..33822d81f 100644
--- a/docs/_site/concepts.html
+++ b/docs/_site/concepts.html
@@ -443,7 +443,7 @@ Using respond()
Acknowledging requests
-
Actions, commands, and options requests must always be acknowledged using the ack() function. This lets Slack know that the request was received and updates the Slack user interface accordingly. Depending on the type of reuqest, your acknowledgement may be different. For example, when responding to a dialog submission you will call ack() with validation errors if the submission contains errors, or with no parameters if the submission is valid.
+
Actions, commands, and options requests must always be acknowledged using the ack() function. This lets Slack know that the request was received and updates the Slack user interface accordingly. Depending on the type of request, your acknowledgement may be different. For example, when responding to a dialog submission you will call ack() with validation errors if the submission contains errors, or with no parameters if the submission is valid.
We recommend calling ack() right away before sending a new message or fetching information from your database since you only have 3 seconds to respond.
Create an app
After you fill out an app name (you can change it later) and picking a workspace to install it to, hit the Create App button and you’ll land on your app’s Basic Information page.
-This page contains an overview of your app in addition to important credentials you’ll need later, like the Signing Secret under the App Crendentials header.
+This page contains an overview of your app in addition to important credentials you’ll need later, like the Signing Secret under the App Credentials header.
@@ -164,7 +164,7 @@ Create an app
Tokens and installing apps
Slack apps use the industry standard OAuth to manage access to Slack’s APIs. When an app is installed, you’ll receive a token that your app can use to call various API methods.
-There are two token types availalbe to a Slack app: user (xoxp) tokens and bot (xoxb) tokens. User tokens allow you to call API methods on behalf of users who are a part of your workspace. By default, your app receive an xoxp token associated with the person who installs the app. Bot tokens require adding a bot user to your app, which is granted a default set of permissions.
+There are two token types available to a Slack app: user (xoxp) tokens and bot (xoxb) tokens. User tokens allow you to call API methods on behalf of users who are a part of your workspace. By default, your app receive an xoxp token associated with the person who installs the app. Bot tokens require adding a bot user to your app, which is granted a default set of permissions.
Tokens require one or more scopes, which define the actions the token can perform. Every API method has a corresponding scope that’s required for an app to call the method.
@@ -189,7 +189,7 @@ Tokens and installing apps
Setting up your local project
With the initial configuration handled, it’s time to set up a new Bolt project. This is where you’ll write the code that handles the logic for your app. One important thing to note is that Slack doesn’t host your code — you do.
-If you don’t already have a project, let’s create a new one. Create an empty directory and initalize a new project:
+If you don’t already have a project, let’s create a new one. Create an empty directory and initialize a new project:
@@ -216,7 +216,7 @@
Setting up your local project
- - Copy your bot (xoxb) token from the OAuth & Permissions page and store it in another enviornment variable.
+ - Copy your bot (xoxb) token from the OAuth & Permissions page and store it in another environment variable.
@@ -241,7 +241,7 @@
Setting up your local project
const { App } = require('@slack/bolt');
-// Initalizes your app with your bot token and signing secret
+// Initializes your app with your bot token and signing secret
const app = new App({
token: process.env.SLACK_BOT_TOKEN,
signingSecret: process.env.SLACK_SIGNING_SECRET
@@ -286,7 +286,7 @@ Using a local Request URL for development
If you’re just getting started with your app’s development, you probably don’t have a publicly accessible URL yet. Eventually, you’ll want to set that up, but for now a development proxy like ngrok will do the job. We’ve written a separate tutorial about using ngrok with Slack for local development that should help you get everything set up.
- Once you’ve installed a development proxy, run it to begin forwarding requests to a specific port (we’re using port 3000 for this example, but if you customized the port used to intialize your app use that port instead):
+ Once you’ve installed a development proxy, run it to begin forwarding requests to a specific port (we’re using port 3000 for this example, but if you customized the port used to initialize your app use that port instead):
diff --git a/docs/_tutorials/getting_started.md b/docs/_tutorials/getting_started.md
index f93e32f6d..4478ededf 100644
--- a/docs/_tutorials/getting_started.md
+++ b/docs/_tutorials/getting_started.md
@@ -32,7 +32,7 @@ First thing's first: before you start developing with Bolt, you'll want to [crea
After you fill out an app name (_you can change it later_) and pick a workspace to install it to, hit the `Create App` button and you'll land on your app's **Basic Information** page.
-This page contains an overview of your app in addition to important credentials you'll need later, like the `Signing Secret` under the **App Crendentials** header.
+This page contains an overview of your app in addition to important credentials you'll need later, like the `Signing Secret` under the **App Credentials** header.
@@ -64,7 +64,7 @@ You'll see two tokens. For now, we'll just use the `xoxb` bot token. (If you scr
### Setting up your local project
With the initial configuration handled, it's time to set up a new Bolt project. This is where you'll write the code that handles the logic for your app.
-If you don’t already have a project, let’s create a new one. Create an empty directory and initalize a new project:
+If you don’t already have a project, let’s create a new one. Create an empty directory and initialize a new project:
```shell
mkdir first-bolt-app
@@ -82,7 +82,7 @@ Before we install the Bolt package to your new project, let's save the bot token
export SLACK_SIGNING_SECRET=
```
-2. **Copy your bot (xoxb) token from the OAuth & Permissions page** and store it in another enviornment variable.
+2. **Copy your bot (xoxb) token from the OAuth & Permissions page** and store it in another environment variable.
```shell
export SLACK_BOT_TOKEN=xoxb-
@@ -141,7 +141,7 @@ When an event occurs, Slack will send your app some information about the event,
If you’re just getting started with your app's development, you probably don’t have a publicly accessible URL yet. Eventually, you’ll want to set that up, but for now a development proxy like [ngrok](https://ngrok.com/) will create a public URL and tunnel requests to your own development environment. We've written a separate tutorial about [using ngrok with Slack for local development](https://api.slack.com/tutorials/tunneling-with-ngrok) that should help you get everything set up.
-Once you’ve installed a development proxy, run it to begin forwarding requests to a specific port (we’re using port 3000 for this example, but if you customized the port used to intialize your app use that port instead):
+Once you’ve installed a development proxy, run it to begin forwarding requests to a specific port (we’re using port 3000 for this example, but if you customized the port used to initialize your app use that port instead):
```shell
ngrok http 3000