Skip to content

Commit

Permalink
fix: correct words that had better alternatives
Browse files Browse the repository at this point in the history
Co-authored-by: Luke Russell <[email protected]>
  • Loading branch information
zimeg and lukegalbraithrussell authored Aug 24, 2024
1 parent 946a661 commit 0b021e8
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/content/basic/authenticating-oauth.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,15 +9,15 @@ in distributing your app. For each completed authentication process, you receive
unique [access tokens and related information](#the-installation-object) that
can be retrieved for incoming events and used to make scoped API requests.

All of the additional underlying details around authentications can be found at
[api.slack.com/authentication/oauth-v2][oauth-v2]!
All of the additional underlying details around authentications can be found within
[the Slack API documentation][oauth-v2]!

## Configuring the application

To set your Slack app up for distribution, you will need to enable Bolt OAuth
and store installation information securely. Bolt supports OAuth by using
the [`@slack/oauth`][oauth-node] package to handle most of the work; this includes setting
up OAuth routes, state verification, and passing your app an installation object
up OAuth routes, verifying state, and passing your app an installation object
which you must store.

### App options
Expand Down Expand Up @@ -247,7 +247,7 @@ links to the authorization page!

:::note

Authorization requests with changed or additional scops require
Authorization requests with changed or additional scopes require
[generating a unique authorization URL](#extra-authorizations).

:::
Expand Down

0 comments on commit 0b021e8

Please sign in to comment.