Update howto-identity-protection-simulate-risk.md

fixed a few typos

Author: cuixi1222

articles/active-directory/identity-protection/howto-identity-protection-simulate-risk.md

@@ -84,23 +84,23 @@ The sign-in shows up in the Identity Protection dashboard within 2-4 hours.
 
 ## Leaked Credentials for Workload Identities
 
-This risk detection indicates that the appplication's valid credentials have been leaked. This leak can occur when someone checks in the credentials in public code artifact on GitHub. Therefore, to the simulation this detection, you need a GitHub account and can [sign up a GitHub account](https://docs.github.com/en/get-started/signing-up-for-github) if you don't have one already.
+This risk detection indicates that the application's valid credentials have been leaked. This leak can occur when someone checks in the credentials in a public code artifact on GitHub. Therefore, to simulate this detection, you need a GitHub account and can [sign up a GitHub account](https://docs.github.com/en/get-started/signing-up-for-github) if you don't have one already.
 
 **To simulate Leaked Credentials in GitHub for Workload Identities, perform the following steps**:
 1. Navigate to the [Azure portal](https://portal.azure.com).
 2. Browse to **Azure Active Directory** > **App registrations**.
-3. Select **New registration** to register a new application or resue an exsiting stale application.
-4. Select **Certificates & Secrets** > **New client Secret** , add a description of your client secret and set an expiration for the secret or specify a custom lifetime and click **Add**. Record the secret's value for later use for GitHub Commit, note **You can not retrieve the secret again after you leave this page**.
+3. Select **New registration** to register a new application or reuse an exsiting stale application.
+4. Select **Certificates & Secrets** > **New client Secret** , add a description of your client secret and set an expiration for the secret or specify a custom lifetime and click **Add**. Record the secret's value for later use for your GitHub Commit. Note: **You can not retrieve the secret again after you leave this page**.
 5. Get the TenantID and Application(Client)ID in the **Overview** page.
-6. You may need disable the application via **Azure Active Directory** > **Enterprise Application** > **Properties** > Set **Enabled for users to sign-in** to No
+6. Ensure you disable the application via **Azure Active Directory** > **Enterprise Application** > **Properties** > Set **Enabled for users to sign-in** to **No**
 7. Create a **public** GitHub Repository, add the following config and commit the change.
    ```GitHub file
      "AadClientId": "XXXX-2dd4-4645-98c2-960cf76a4357",
      "AadSecret": "p3n7Q~XXXX",
      "AadTenantDomain": "XXXX.onmicrosoft.com",
      "AadTenantId": "99d4947b-XXX-XXXX-9ace-abceab54bcd4",
    ```
-7. In about 24 hours, you are able to view a leaked credentail detection under **Azure Active Directory** > **Security** > **Risk Detection** > **Workload identity detections** where the additional info contains your the URL of your GitHub commit.
+7. In about 8 hours, you will be able to view a leaked credentail detection under **Azure Active Directory** > **Security** > **Risk Detection** > **Workload identity detections** where the additional info will contain your the URL of your GitHub commit.
 
 ## Testing risk policies