daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix spelling, spaces, and wording (#27093) 

* Fix misspellings and improve wording

This syncs with line 375.

* Improve wording and fix spaces
pull/27096/head
GitHubPang 2022-09-26 08:50:34 +08:00 committed by GitHub
parent 8aa19c6a92
commit 3057fe3e95
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
aspnetcore/fundamentals/localization.md
View File

@ -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 <xref:Microsoft.AspNetCore.Builder.RequestLocalizationOptionsExtensions.AddInitialRequestCultureProvider%2A> which sets the order to `0`, so this provider takes the precedence over the others.

4
aspnetcore/mvc/controllers/filters.md
View File

@ -332,7 +332,7 @@ Resource filter examples:
## Action filters
Action filters do **not** apply to Razor Pages. Razor Pages supports <xref:Microsoft.AspNetCore.Mvc.Filters.IPageFilter> and <xref:Microsoft.AspNetCore.Mvc.Filters.IAsyncPageFilter> . For more information, see [Filter methods for Razor Pages](xref:razor-pages/filter).
Action filters do **not** apply to Razor Pages. Razor Pages supports <xref:Microsoft.AspNetCore.Mvc.Filters.IPageFilter> and <xref:Microsoft.AspNetCore.Mvc.Filters.IAsyncPageFilter>. 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 <xref:Microsoft.AspNetCore.Mvc.Filters.IPageFilter> and <xref:Microsoft.AspNetCore.Mvc.Filters.IAsyncPageFilter> . For more information, see [Filter methods for Razor Pages](xref:razor-pages/filter).
Action filters do **not** apply to Razor Pages. Razor Pages supports <xref:Microsoft.AspNetCore.Mvc.Filters.IPageFilter> and <xref:Microsoft.AspNetCore.Mvc.Filters.IAsyncPageFilter>. For more information, see [Filter methods for Razor Pages](xref:razor-pages/filter).
Action filters:

4
aspnetcore/release-notes/aspnetcore-7.0.md
View File

@ -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

4
aspnetcore/test/integration-tests.md
View File

@ -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