Merge pull request #2796 from splunk/fix-aws-al-desc

Update description

Author: patel-bhavin

playbooks/AWS_IAM_Account_Locking.json

@@ -4,7 +4,7 @@
     "category": "Account Locking",
     "coa": {
         "data": {
-            "description": "Accepts user name that needs to be disabled in AWS IAM Active Directory. Generates an observable output based on the status of account locking or disabling.",
+            "description": "Accepts user name that needs to be disabled in AWS IAM Active Directory. Disabling an account involves deleting their login profile which will clear the user's password. Generates an observable output based on the status of account locking or disabling.",
             "edges": [
                 {
                     "id": "port_0_to_port_2",

playbooks/AWS_IAM_Account_Locking.yml

@@ -4,7 +4,7 @@ version: 1
 date: '2023-05-08'
 author: Teoderick Contreras, Splunk
 type: Investigation
-description: "Accepts user, to be disabled using AWS IAM connector. This playbook produces a normalized observables output for each user and device."
+description: "Accepts user name that needs to be disabled in AWS IAM Active Directory. Disabling an account involves deleting their login profile which will clear the user's password. Generates an observable output based on the status of account locking or disabling."
 playbook: AWS_IAM_Account_Locking
 how_to_implement: This input playbook requires the AWS IAM connector to be configured. 
   It is designed to work in conjunction with the Dynamic Attribute Lookup playbook or other playbooks in the same style.