small changes to the azure ad oidc doc (#3013)

* small changes to the azure ad oidc doc

* fixed small typos

astro/src/content/docs/_shared/_idp-form-fields.astro

@@ -14,7 +14,7 @@ const { getStartedHref, getStartedText, idp, linkingStrategy, scopeDefault, scop
   </APIField>
 
   {idp !== 'Steam' &&
-   <APIField name="Client secret" required>The client secret obtained from {idp} used to authenticate the request. See <a href={getStartedHref}>{getStartedText}</a>.</APIField>}
+   <APIField name="Client secret" required>The client secret obtained from {idp} and used to authenticate the request. See <a href={getStartedHref}>{getStartedText}</a>.</APIField>}
 
   { idp === 'Steam' &&
 

astro/src/content/docs/lifecycle/authenticate-users/identity-providers/enterprise/azure-ad-oidc.mdx

@@ -50,13 +50,13 @@ To create an Azure AD Identity Provider return to FusionAuth and navigate to <st
 
 This will take you to the `Add OpenID Connect` panel, and you'll fill out the required fields.
 
-You will need to set <InlineField>Client authentication method</InlineField> to `HTTP Basic authentication (client_secret_basic)`.
+You will need to set the <InlineField>Client authentication method</InlineField> to `HTTP Basic authentication (client_secret_basic)`.
 
 <InlineField>Client Id</InlineField> and <InlineField>Client secret</InlineField> values reference the previously noted Azure AD Application's `Application (client) ID`, client secret `VALUE`. The <InlineField>Redirect URL</InlineField> is read only and generated for you based upon the URL of FusionAuth, this value should match the one you configured in your Azure application.
 
-Azure AD has implemented a well-known configuration endpoint, FusionAuth will be able to discover the necessary endpoints using a discovery document by entering the Microsoft Authority URL (Issuer) in the <InlineField>Issuer</InlineField> field.
+Azure AD has implemented a well-known configuration endpoint, so FusionAuth will be able to discover the necessary endpoints using a discovery document by entering the Microsoft Authority URL in the <InlineField>Issuer</InlineField> field. To see the <InlineField>Issuer</InlineField> field, you may need to toggle <InlineField>Discover endpoints</InlineField>.
 
-The Microsoft URL may diff across national clouds, so you will need to review the Microsoft documentation to ensure you have the correct URL for your region. For the Microsoft global Azure AD service, the URLs are as follows, where `{tenantId}` is the `Directory (tenant) ID` previously noted while creating our Azure AD Application.
+The Microsoft URL may differ across national clouds, so you will need to review the Microsoft documentation to ensure you have the correct URL for your region. For the Microsoft global Azure AD service, the URLs are as follows, where `{tenantId}` is the `Directory (tenant) ID` previously noted while creating our Azure AD Application.
 
 - Azure AD v1  `https://login.microsoftonline.com/{tenantId}`
 - Azure AD v2  `https://login.microsoftonline.com/{tenantId}/v2.0`