From f63c1ef042f8aba9bb3af3b8a4657e883d2dfc75 Mon Sep 17 00:00:00 2001
From: Moshe Eichler <78307768+MosheEichler@users.noreply.github.com>
Date: Tue, 23 Jul 2024 17:25:06 +0300
Subject: [PATCH] Fix typo in playbook docs (#1585)

---
 docs/playbooks/playbooks-overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/playbooks/playbooks-overview.md b/docs/playbooks/playbooks-overview.md
index 70401f740..79821acca 100644
--- a/docs/playbooks/playbooks-overview.md
+++ b/docs/playbooks/playbooks-overview.md
@@ -16,7 +16,7 @@ As you are building out your playbook, keep in mind the following:
 
 
 ## Task Types
-The answers to the above questions will determine what kind of task you will need to create. Playbooks support the folloiwng task types:
+The answers to the above questions will determine what kind of task you will need to create. Playbooks support the following task types:
 
 * Standard tasks - these range from manual tasks like creating an incident or escalating an existing incident, to automated tasks such as parsing a file or enriching indicators. Automated tasks are based on scripts that exist in the system. These scripts can be something that was created by you, the user, or come pre-packaged as part of an integration. For example, the *!file* command enables you to enrich a file using any number of integrations that you have installed in your system. Alternatively, the *!ADGetUser* command is specific to the Active Directory integration.