Update and rename Kerbroasting.yaml to Kerberoasting.yaml (#2754)

Double-checked against the linked Mitre pages that it is "Kerberoasting"
rather than "Kerbroasting"

artifacts/definitions/Windows/Events/Kerbroasting.yaml → artifacts/definitions/Windows/Events/Kerberoasting.yaml

@@ -1,17 +1,17 @@
-name: Windows.Events.Kerbroasting
+name: Windows.Events.Kerberoasting
 description: |
   **Description**:
   This Artifact will monitor all successful Kerberos TGS Ticket events for
   Service Accounts (SPN attribute) implemented with weak encryption. These
   tickets are vulnerable to brute force attack and this event is an indicator
-  of a Kerbroasting attack.
+  of a Kerberoasting attack.
 
-  **ATT&CK**: [T1208 - Kerbroasting](https://attack.mitre.org/techniques/T1208/)
+  **ATT&CK**: [T1208 - Kerberoasting](https://attack.mitre.org/techniques/T1208/)
   Typical attacker methodology is to firstly request accounts in the domain
   with SPN attributes, then request an insecure TGS ticket for brute forcing.
   This attack is particularly effective as any domain credentials can be used
   to implement the attack and service accounts often have elevated privileges.
-  Kerbroasting can be used for privilege escalation or persistence by adding a
+  Kerberoasting can be used for privilege escalation or persistence by adding a
   SPN attribute to an unexpected account.
 
   **Reference**: [The Art of Detecting Kerberoast Attacks](https://www.trustedsec.com/2018/05/art_of_kerberoast/)
@@ -37,7 +37,7 @@ parameters:
     default: C:\Windows\system32\winevt\logs\Security.evtx
 
 sources:
-  - name: Kerbroasting
+  - name: Kerberoasting
     query: |
       LET files = SELECT * FROM glob(globs=eventLog)