Skip to content

Commit 966cb19

Browse files
authored
Update scenario-web-app-call-api-app-configuration.md
1 parent e13fcfe commit 966cb19

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/develop/scenario-web-app-call-api-app-configuration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ ms.custom: aaddev
2222

2323
As shown in the [Web app that signs in users](scenario-web-app-sign-user-overview.md) scenario, the web app uses the [OAuth 2.0 authorization code flow](v2-oauth2-auth-code-flow.md) to sign the user in. This flow has two steps:
2424

25-
1. Request an authorization code. This part delegates a private dialog with the user to the Microsoft identity platform. During that dialog, the user signs in and consents to the use of web APIs. When the private dialog ends successfully, the web app receives an authorization code on its redirect URI.
25+
1. Request an authorization code. This part delegates a private dialogue with the user to the Microsoft identity platform. During that dialogue, the user signs in and consents to the use of web APIs. When the private dialogue ends successfully, the web app receives an authorization code on its redirect URI.
2626
1. Request an access token for the API by redeeming the authorization code.
2727

2828
The [Web app that signs in users](scenario-web-app-sign-user-overview.md) scenarios covered only the first step. Here you learn how to modify your web app so that it not only signs users in but also now calls web APIS.
@@ -258,7 +258,7 @@ In ASP.NET Core, building the confidential client application uses information t
258258
The `BuildConfidentialClientApplication` method also uses the ASP.NET Core configuration. The configuration has an "AzureAD" section, and also is bound to both of the following elements:
259259

260260
- The `_applicationOptions` data structure of type [ConfidentialClientApplicationOptions](https://docs.microsoft.com/dotnet/api/microsoft.identity.client.confidentialclientapplicationoptions?view=azure-dotnet).
261-
- the `azureAdOptions` instance of type [AzureAdOptions](https://github.com/aspnet/AspNetCore/blob/master/src/Azure/AzureAD/Authentication.AzureAD.UI/src/AzureADOptions.cs), defined in ASP.NET Core `Authentication.AzureAD.UI`.
261+
- The `azureAdOptions` instance of type [AzureAdOptions](https://github.com/aspnet/AspNetCore/blob/master/src/Azure/AzureAD/Authentication.AzureAD.UI/src/AzureADOptions.cs), defined in ASP.NET Core `Authentication.AzureAD.UI`.
262262
263263
Finally, the application needs to maintain token caches. You'll learn more about that in the next section.
264264

0 commit comments

Comments
 (0)