From 322756b407677619e86dcbfe672b545943626ebc Mon Sep 17 00:00:00 2001 From: Shane DeWael Date: Fri, 3 May 2019 16:24:43 -0700 Subject: [PATCH] Fix include --- docs/_basic/acknowledging_requests.md | 4 ++-- docs/_includes/{tagmanager.html => tag_manager.html} | 0 2 files changed, 2 insertions(+), 2 deletions(-) rename docs/_includes/{tagmanager.html => tag_manager.html} (100%) diff --git a/docs/_basic/acknowledging_requests.md b/docs/_basic/acknowledging_requests.md index 8786abbc5..cc58601c4 100644 --- a/docs/_basic/acknowledging_requests.md +++ b/docs/_basic/acknowledging_requests.md @@ -1,11 +1,11 @@ --- -title: Acknowledging requests +title: Acknowledging events slug: acknowledge order: 7 ---
-Actions, commands, and options requests must **always** be acknowledged using the `ack()` function. This lets Slack know that the event was received and updates the Slack user interface accordingly. Depending on the type of event, your acknowledgement may be different. For example, when acknowledging 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 events must **always** be acknowledged using the `ack()` function. This lets Slack know that the event was received and updates the Slack user interface accordingly. Depending on the type of event, your acknowledgement may be different. For example, when acknowledging 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.
diff --git a/docs/_includes/tagmanager.html b/docs/_includes/tag_manager.html similarity index 100% rename from docs/_includes/tagmanager.html rename to docs/_includes/tag_manager.html