Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove repeated sentence in auth docs #301

Merged
merged 1 commit into from Dec 18, 2016
Merged

Remove repeated sentence in auth docs #301

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/_pages/auth.md
View file
Open in desktop
Expand Up @@ -10,7 +10,7 @@ headings:
## Handling tokens and other sensitive data

Slack tokens are the keys to your—or your customers'—teams. Keep them secret. Keep them safe. One way to do that is
to never explicitly hardcode them. One way to do that is to never explicitly hardcode them.
to never explicitly hardcode them.

Try to avoid this when possible:

Expand Down Expand Up @@ -40,4 +40,4 @@ You can use the same technique for other kinds of sensitive data that ne'er-do-w
* Incoming webhook URLs
* Slash command verification tokens
* Bot verification tokens
* App client ids and client secrets
* App client ids and client secrets