custom authentication extension > custom extension

I've excluded references in the "Error codes reference" section because the descriptions may be embedded in the product currently. I recommend that the descriptions be updated in the product and then the changes propagated to the docs.

Author: FaithOmbongi

articles/active-directory/develop/custom-extension-troubleshoot.md

@@ -45,7 +45,7 @@ To access the Azure AD sign-in logs:
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. In the **Enterprise apps** experience for your given application, select on the **Sign-in** logs tab.
 1. Select the latest sign-in log.
-1. For more details, select the **Authentication Events** tab. Information related to the custom extension REST API call is displayed, including any [error codes](#error-codes-reference).
+1. For more details, select the **Authentication Events** tab. Information related to the custom authentication extension REST API call is displayed, including any [error codes](#error-codes-reference).
 
     :::image type="content" source="media/custom-extension-troubleshoot/authentication-events.png" alt-text="Screenshot that shows the authentication events information." :::
 
@@ -85,7 +85,7 @@ Use the following table to diagnose an error code.
 
 ## Call your REST API directly
 
-Your REST API is protected by Azure AD access token. You can test your API by obtaining an access token with the [application registration](custom-extension-get-started.md#22-grant-admin-consent) associated with the custom extensions. After you acquire an access token, pass it the HTTP `Authorization` header. To obtain an access token, follow these steps:
+Your REST API is protected by Azure AD access token. You can test your API by obtaining an access token with the [application registration](custom-extension-get-started.md#22-grant-admin-consent) associated with the custom authentiction extensions. After you acquire an access token, pass it the HTTP `Authorization` header. To obtain an access token, follow these steps:
 
 1. Sign in to the [Azure portal](https://portal.azure.com/) with your Azure administrator account.
 1. Select **Azure Active Directory** > **App registrations**.
@@ -135,7 +135,7 @@ To test your API directly from the Postman, follow these steps:
             "@odata.type": "microsoft.graph.onTokenIssuanceStartCalloutData",
             "tenantId": "<Your tenant GUID>",
             "authenticationEventListenerId": "<GUID>",
-            "customAuthenticationExtensionId": "<Your custom extension ID>",
+            "customAuthenticationExtensionId": "<Your custom authentication extension ID>",
             "authenticationContext": {
                 "correlationId": "fcef74ef-29ea-42ca-b150-8f45c8f31ee6",
                 "client": {
@@ -189,4 +189,4 @@ One of the most common issues is that your custom claims provider API doesn't re
 
 - Learn how to [create and register a custom claims provider](custom-extension-get-started.md) with a sample Open ID Connect application.
 - If you already have a custom claims provider registered, you can configure a [SAML application](custom-extension-configure-saml-app.md) to receive tokens with claims sourced from an external store.
-- Learn more about custom claims providers with the [custom claims provider reference](custom-claims-provider-reference.md) article.
+- Learn more about custom claims providers with the [custom claims provider reference](custom-claims-provider-reference.md) article.