From 5325c104a7cb13ff00a12125ede642ba0197739b Mon Sep 17 00:00:00 2001 From: Luke Latham Date: Sat, 22 Aug 2020 16:15:32 -0500 Subject: [PATCH] Fix double words (#19621) --- aspnetcore/blazor/host-and-deploy/webassembly.md | 2 +- aspnetcore/blazor/progressive-web-app.md | 4 ++-- .../blazor/security/server/additional-scenarios.md | 2 +- aspnetcore/host-and-deploy/proxy-load-balancer.md | 6 +++--- .../blazor-security/index-page-authentication.md | 2 +- aspnetcore/includes/blazor-security/index-page-msal.md | 2 +- aspnetcore/migration/identity.md | 2 +- aspnetcore/mvc/views/razor.md | 2 +- aspnetcore/security/authentication/cookie.md | 2 +- aspnetcore/tutorials/razor-pages/page.md | 10 ++++------ 10 files changed, 16 insertions(+), 18 deletions(-) diff --git a/aspnetcore/blazor/host-and-deploy/webassembly.md b/aspnetcore/blazor/host-and-deploy/webassembly.md index 961113680a43..79b1d42b5cc8 100644 --- a/aspnetcore/blazor/host-and-deploy/webassembly.md +++ b/aspnetcore/blazor/host-and-deploy/webassembly.md @@ -36,7 +36,7 @@ Blazor relies on the host to the serve the appropriate compressed files. When us * When hosting on static hosting solutions that don't support statically-compressed file content negotiation, such as GitHub Pages, consider configuring the app to fetch and decode Brotli compressed files: * Obtain the JavaScript Brotli decoder from the [google/brotli GitHub repository](https://github.com/google/brotli). As of July 2020, the decoder file is named `decode.min.js` and found in the repository's [`js` folder](https://github.com/google/brotli/tree/master/js). - * Update the app to use the decoder. Change the markup inside the the closing `` tag in `wwwroot/index.html` to the following: + * Update the app to use the decoder. Change the markup inside the closing `` tag in `wwwroot/index.html` to the following: ```html diff --git a/aspnetcore/blazor/progressive-web-app.md b/aspnetcore/blazor/progressive-web-app.md index df441e829a8d..85b8e4a4de61 100644 --- a/aspnetcore/blazor/progressive-web-app.md +++ b/aspnetcore/blazor/progressive-web-app.md @@ -56,7 +56,7 @@ Optionally, PWA can be configured for an app created from the ASP.NET Core Hoste When visiting an app created using the PWA template, users have the option of installing the app into their OS's start menu, dock, or home screen. The way this option is presented depends on the user's browser. When using desktop Chromium-based browsers, such as Edge or Chrome, an **Add** button appears within the URL bar. After the user selects the **Add** button, they receive a confirmation dialog: -![The confirmation diaglog in Google Chrome presents an Install button button to the user for the 'MyBlazorPwa' app.](progressive-web-app/_static/image2.png) +![The confirmation dialog in Google Chrome presents an Install button to the user for the 'MyBlazorPwa' app.](progressive-web-app/_static/image2.png) On iOS, visitors can install the PWA using Safari's **Share** button and its **Add to Homescreen** option. On Chrome for Android, users should select the **Menu** button in the upper-right corner, followed by **Add to Home screen**. @@ -276,7 +276,7 @@ To create an offline PWA app that interacts with authentication: * Queue operations while the app is offline and apply them when the app returns online. * During sign out, clear the stored user. -The [`CarChecker`](https://github.com/SteveSandersonMS/CarChecker) sample app demonstrates the the preceding approaches. See the following parts of the app: +The [`CarChecker`](https://github.com/SteveSandersonMS/CarChecker) sample app demonstrates the preceding approaches. See the following parts of the app: * `OfflineAccountClaimsPrincipalFactory` (`Client/Data/OfflineAccountClaimsPrincipalFactory.cs`) * `LocalVehiclesStore` (`Client/Data/LocalVehiclesStore.cs`) diff --git a/aspnetcore/blazor/security/server/additional-scenarios.md b/aspnetcore/blazor/security/server/additional-scenarios.md index dfe34be5a860..7d8214e5f71a 100644 --- a/aspnetcore/blazor/security/server/additional-scenarios.md +++ b/aspnetcore/blazor/security/server/additional-scenarios.md @@ -177,7 +177,7 @@ If tacking on a segment to the authority isn't appropriate for the app's OIDC pr ### Code changes * The list of claims in the ID token changes for v2.0 endpoints. For more information, see [Why update to Microsoft identity platform (v2.0)?](/azure/active-directory/azuread-dev/azure-ad-endpoint-comparison) in the Azure documentation. -* Since resources are specified in scope URIs for v2.0 endpoints, remove the the property setting in : +* Since resources are specified in scope URIs for v2.0 endpoints, remove the property setting in : ```csharp services.Configure(AzureADDefaults.OpenIdScheme, options => diff --git a/aspnetcore/host-and-deploy/proxy-load-balancer.md b/aspnetcore/host-and-deploy/proxy-load-balancer.md index 0d7348d5750a..c99a7ab7a666 100644 --- a/aspnetcore/host-and-deploy/proxy-load-balancer.md +++ b/aspnetcore/host-and-deploy/proxy-load-balancer.md @@ -62,7 +62,7 @@ Configure the middleware with (options => { @@ -570,7 +570,7 @@ You can also supply the address in hexadecimal format (`10.11.12.1` represented ```csharp // To access IPNetwork and IPAddress, add the following namespaces: -// using using System.Net; +// using System.Net; // using Microsoft.AspNetCore.HttpOverrides; services.Configure(options => { diff --git a/aspnetcore/includes/blazor-security/index-page-authentication.md b/aspnetcore/includes/blazor-security/index-page-authentication.md index 178098eb2ddc..4948231ef0f4 100644 --- a/aspnetcore/includes/blazor-security/index-page-authentication.md +++ b/aspnetcore/includes/blazor-security/index-page-authentication.md @@ -1,4 +1,4 @@ -The Index page (`wwwroot/index.html`) page includes a script that defines the `AuthenticationService` in JavaScript. `AuthenticationService` handles the low-level details of the the OIDC protocol. The app internally calls methods defined in the script to perform the authentication operations. +The Index page (`wwwroot/index.html`) page includes a script that defines the `AuthenticationService` in JavaScript. `AuthenticationService` handles the low-level details of the OIDC protocol. The app internally calls methods defined in the script to perform the authentication operations. ```html