From 3057fe3e950d41d39d55b45d7545acdba63defed Mon Sep 17 00:00:00 2001 From: GitHubPang <61439577+GitHubPang@users.noreply.github.com> Date: Mon, 26 Sep 2022 08:50:34 +0800 Subject: [PATCH] Fix spelling, spaces, and wording (#27093) * Fix misspellings and improve wording This syncs with line 375. * Improve wording and fix spaces --- aspnetcore/fundamentals/localization.md | 2 +- aspnetcore/mvc/controllers/filters.md | 4 ++-- aspnetcore/release-notes/aspnetcore-7.0.md | 4 ++-- aspnetcore/test/integration-tests.md | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/aspnetcore/fundamentals/localization.md b/aspnetcore/fundamentals/localization.md index f8a674f811..9faad33e69 100644 --- a/aspnetcore/fundamentals/localization.md +++ b/aspnetcore/fundamentals/localization.md @@ -743,7 +743,7 @@ Use `RequestLocalizationOptions` to add or remove localization providers. }); ``` -In the preceding example above, the order of `QueryStringRequestCultureProvider` and `CookieRequestCultureProvider` is swithched, so the `RequestLocalizationMiddleware` looks for the cultures from the cookies first, then query string. +In the preceding example, the order of `QueryStringRequestCultureProvider` and `CookieRequestCultureProvider` is switched, so the `RequestLocalizationMiddleware` looks for the cultures from the cookies first, then query string. As previously mentioned, add a custom provider via which sets the order to `0`, so this provider takes the precedence over the others. diff --git a/aspnetcore/mvc/controllers/filters.md b/aspnetcore/mvc/controllers/filters.md index a49bfc11ec..8fe47759c7 100644 --- a/aspnetcore/mvc/controllers/filters.md +++ b/aspnetcore/mvc/controllers/filters.md @@ -332,7 +332,7 @@ Resource filter examples: ## Action filters -Action filters do **not** apply to Razor Pages. Razor Pages supports and . For more information, see [Filter methods for Razor Pages](xref:razor-pages/filter). +Action filters do **not** apply to Razor Pages. Razor Pages supports and . For more information, see [Filter methods for Razor Pages](xref:razor-pages/filter). Action filters: @@ -919,7 +919,7 @@ Resource filter examples: ## Action filters -Action filters do **not** apply to Razor Pages. Razor Pages supports and . For more information, see [Filter methods for Razor Pages](xref:razor-pages/filter). +Action filters do **not** apply to Razor Pages. Razor Pages supports and . For more information, see [Filter methods for Razor Pages](xref:razor-pages/filter). Action filters: diff --git a/aspnetcore/release-notes/aspnetcore-7.0.md b/aspnetcore/release-notes/aspnetcore-7.0.md index f7237b1c1f..4c5558dfa4 100644 --- a/aspnetcore/release-notes/aspnetcore-7.0.md +++ b/aspnetcore/release-notes/aspnetcore-7.0.md @@ -164,7 +164,7 @@ There is no built-in support for [antiforgery](/aspnet/core/security/anti-reques ### `[AsParameters]` attribute enables parameter binding for argument lists -The [`[AsParameters]` attribute](xref:Microsoft.AspNetCore.Http.AsParametersAttribute) enables parameter binding for argument lists . For more information, see [Parameter binding for argument lists with `[AsParameters]`](xref:fundamentals/minimal-apis?view=aspnetcore-7.0&preserve-view=true#asparam7). +The [`[AsParameters]` attribute](xref:Microsoft.AspNetCore.Http.AsParametersAttribute) enables parameter binding for argument lists. For more information, see [Parameter binding for argument lists with `[AsParameters]`](xref:fundamentals/minimal-apis?view=aspnetcore-7.0&preserve-view=true#asparam7). ## gRPC @@ -291,7 +291,7 @@ services.AddW3CLogging(logging => }); ``` -For more information,see [W3CLogger options](xref:fundamentals/w3c-logger/index#w3clogger-options-1). +For more information, see [W3CLogger options](xref:fundamentals/w3c-logger/index#w3clogger-options-1). ### Request decompression diff --git a/aspnetcore/test/integration-tests.md b/aspnetcore/test/integration-tests.md index 162f74ff80..8aa86f68a4 100644 --- a/aspnetcore/test/integration-tests.md +++ b/aspnetcore/test/integration-tests.md @@ -25,7 +25,7 @@ The sample app is a Razor Pages app and assumes a basic understanding of Razor P * [Razor Pages unit tests](xref:test/razor-pages-tests) > [!NOTE] -> For testing SPAs, we recommended a tool such as [Playwright for .NET](https://playwright.dev/dotnet/), which can automate a browser. +> For testing SPAs, we recommend a tool such as [Playwright for .NET](https://playwright.dev/dotnet/), which can automate a browser. [!INCLUDE[](~/includes/integrationTests.md)] @@ -166,7 +166,7 @@ The `SendAsync` helper extension methods (`Helpers/HttpClientExtensions.cs`) and > [AngleSharp](https://anglesharp.github.io/) is a third-party parsing library used for demonstration purposes in this topic and the sample app. AngleSharp isn't supported or required for integration testing of ASP.NET Core apps. Other parsers can be used, such as the [Html Agility Pack (HAP)](https://html-agility-pack.net/). Another approach is to write code to handle the antiforgery system's request verification token and antiforgery cookie directly. > [!NOTE] -> The [EF-Core in-memory database provider](/ef/core/testing/choosing-a-testing-strategy#in-memory-as-a-database-fake) can be used for limited and basic testing, however the [SQLite provider](/ef/core/testing/choosing-a-testing-strategy#sqlite-as-a-database-fake) is the recommend choice for in-memory testing. +> The [EF-Core in-memory database provider](/ef/core/testing/choosing-a-testing-strategy#in-memory-as-a-database-fake) can be used for limited and basic testing, however the [SQLite provider](/ef/core/testing/choosing-a-testing-strategy#sqlite-as-a-database-fake) is the recommended choice for in-memory testing. ## Customize the client with WithWebHostBuilder