From 824f1a6b369d672f0b09e66c1b1c5540e899e16e Mon Sep 17 00:00:00 2001 From: Stephen Sauceda Date: Sun, 18 Dec 2016 11:29:00 -0500 Subject: [PATCH] Remove redundant sentence --- docs/_pages/auth.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/_pages/auth.md b/docs/_pages/auth.md index 025d28280..d774d4a72 100644 --- a/docs/_pages/auth.md +++ b/docs/_pages/auth.md @@ -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: @@ -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 \ No newline at end of file + * App client ids and client secrets