diff --git a/detections/endpoint/shedule_task_with_http_command_arguments.yml b/detections/endpoint/schedule_task_with_http_command_arguments.yml
similarity index 67%
rename from detections/endpoint/shedule_task_with_http_command_arguments.yml
rename to detections/endpoint/schedule_task_with_http_command_arguments.yml
index 751030b94a..779e75f541 100644
--- a/detections/endpoint/shedule_task_with_http_command_arguments.yml
+++ b/detections/endpoint/schedule_task_with_http_command_arguments.yml
@@ -1,4 +1,4 @@
-name: Shedule Task with HTTP Command Arguments
+name: Schedule Task with HTTP Command Arguments
 id: 523c2684-a101-11eb-916b-acde48001122
 version: 1
 date: '2021-04-19'
@@ -10,20 +10,20 @@ description: The following query utilizes Windows Security EventCode 4698, `A sc
   task was created`, to identify suspicious tasks registered on Windows either via
   schtasks.exe OR TaskService with an arguments "HTTP" string that are unique entry
   of malware or attack that uses lolbin to download other file or payload to the infected
-  machine.\ The search will return the first time and last time the task was registered,
+  machine. The search will return the first time and last time the task was registered,
   as well as the `Command` to be executed, `Task Name`, `Author`, `Enabled`, and whether
-  it is `Hidden` or not.\ schtasks.exe is natively found in `C:\Windows\system32`
-  and `C:\Windows\syswow64`.\ The following DLL(s) are loaded when schtasks.exe or
-  TaskService is launched -`taskschd.dll`. If found loaded by another process, it
-  is possible a scheduled task is being registered within that process context in
-  memory.\ Upon triage, identify the task scheduled source. Was it schtasks.exe or
-  via TaskService? Review the job created and the Command to be executed. Capture
-  any artifacts on disk and review. Identify any parallel processes within the same
-  timeframe to identify source.'
+  it is `Hidden` or not. schtasks.exe is natively found in `C:\Windows\system32` and
+  `C:\Windows\syswow64`. The following DLL(s) are loaded when schtasks.exe or TaskService
+  is launched -`taskschd.dll`. If found loaded by another process, it is possible
+  a scheduled task is being registered within that process context in memory. Upon
+  triage, identify the task scheduled source. Was it schtasks.exe or via TaskService?
+  Review the job created and the Command to be executed. Capture any artifacts on
+  disk and review. Identify any parallel processes within the same timeframe to identify
+  source.'
 search: '`wineventlog_security` EventCode=4698 | xmlkv Message| search Arguments IN
   ("*http*") | stats count min(_time) as firstTime max(_time) as lastTime by dest,
   Task_Name, Command, Author, Enabled, Hidden, Arguments | `security_content_ctime(firstTime)`
-  | `security_content_ctime(lastTime)` | `shedule_task_with_http_command_arguments_filter`'
+  | `security_content_ctime(lastTime)` | `schedule_task_with_http_command_arguments_filter`'
 how_to_implement: To successfully implement this search, you need to be ingesting
   logs with the task schedule (Exa. Security Log EventCode 4698) endpoints. Tune and
   filter known instances of Task schedule used in your environment.
diff --git a/tests/endpoint/shedule_task_with_http_command_arguments.test.yml b/tests/endpoint/schedule_task_with_http_command_arguments.test.yml
similarity index 68%
rename from tests/endpoint/shedule_task_with_http_command_arguments.test.yml
rename to tests/endpoint/schedule_task_with_http_command_arguments.test.yml
index cedd314f01..7a0dedb3c1 100644
--- a/tests/endpoint/shedule_task_with_http_command_arguments.test.yml
+++ b/tests/endpoint/schedule_task_with_http_command_arguments.test.yml
@@ -1,7 +1,7 @@
-name: Shedule Task with HTTP Command Arguments Unit Test
+name: Schedule Task with HTTP Command Arguments Unit Test
 tests:
-- name: Shedule Task with HTTP Command Arguments
-  file: endpoint/shedule_task_with_http_command_arguments.yml
+- name: Schedule Task with HTTP Command Arguments
+  file: endpoint/schedule_task_with_http_command_arguments.yml
   pass_condition: '| stats count | where count > 0'
   earliest_time: '-24h'
   latest_time: 'now'