Apply suggestions from code review

Co-authored-by: Copilot <[email protected]>

Author: guardrex

aspnetcore/blazor/call-web-api.md

@@ -922,7 +922,7 @@ Follow the guidance in the <xref:web-api/jsonpatch> article to add a PATCH contr
 
 :::moniker range=">= aspnetcore-10.0"
 
-Add a package reference for the [`Microsoft.AspNetCore.JsonPatch.SystemTextJson`](https://www.nuget.org/packages/Microsoft.AspNetCore.Mvc.NewtonsoftJson) NuGet package to the web API app.
+Add a package reference for the [`Microsoft.AspNetCore.JsonPatch.SystemTextJson`](https://www.nuget.org/packages/Microsoft.AspNetCore.JsonPatch.SystemTextJson) NuGet package to the web API app.
 
 In the `Program` file add an `@using` directive for the <xref:Microsoft.AspNetCore.JsonPatch.SystemTextJson?displayProperty=fullName> namespace:
 

aspnetcore/blazor/state-management/server.md

@@ -99,7 +99,7 @@ Persisting component state across circuits is built on top of the existing <xref
 > [NOTE]
 > Persisting component state for prerendering works for any interactive render mode, but circuit state persistence only works for the **Interactive Server** render mode.
 
-Annotate component properties the [`[PersistentState]` attribute](xref:Microsoft.AspNetCore.Components.PersistentStateAttribute) to enable circuit state persistence. The following example also keys the items with the [`@key` directive attribute](xref:blazor/components/key) to provide a unique identifier for each component instance:
+Annotate component properties with the [`[PersistentState]` attribute](xref:Microsoft.AspNetCore.Components.PersistentStateAttribute) to enable circuit state persistence. The following example also keys the items with the [`@key` directive attribute](xref:blazor/components/key) to provide a unique identifier for each component instance:
 
 ```razor
 @foreach (var item in Items)

aspnetcore/security/authentication/passkeys/index.md

@@ -398,7 +398,7 @@ The stored <xref:Microsoft.AspNetCore.Identity.UserPasskeyInfo> contains all of
 
 ### Step 8: Post-registration tasks
 
-After successfully registering a passkey, apps often perform additional tasks to improve the user experience. A common pattern is to prompt users to provide a friendly name for their passkey, making it easier to identify among multiple credentials. The <xref:Microsoft.AspNetCore.Identity.UserPasskeyInfo.Name%2A?displayProperty=nameWithType> property stores this user-friendly name, which can be updated using the same `AddOrUpdatePasskeyAsync` method:
+After successfully registering a passkey, apps often perform additional tasks to improve the user experience. A common pattern is to prompt users to provide a friendly name for their passkey, making it easier to identify among multiple credentials. The <xref:Microsoft.AspNetCore.Identity.UserPasskeyInfo.Name%2A?displayProperty=nameWithType> property stores this user-friendly name, which can be updated using the same <xref:Microsoft.AspNetCore.Identity.UserManager%601.AddOrUpdatePasskeyAsync%2A> method:
 
 ```csharp
 passkey.Name = "My iPhone";
@@ -554,7 +554,7 @@ For scenarios requiring more control, you can use <xref:Microsoft.AspNetCore.Ide
 
 ### Step 8: Session establishment
 
-Upon successful authentication, ASP.NET Core Identity establishes an authenticated session for the user. The <xref:Microsoft.AspNetCore.Identity.SignInManager%601.PasskeySignInAsync%2A> method handles this automatically, creating the necessary authentication cookies and claims. The app then redirects the user to protected resources or display personalized content.
+Upon successful authentication, ASP.NET Core Identity establishes an authenticated session for the user. The <xref:Microsoft.AspNetCore.Identity.SignInManager%601.PasskeySignInAsync%2A> method handles this automatically, creating the necessary authentication cookies and claims. The app then redirects the user to protected resources or displays personalized content.
 
 ## Mitigate `PublicKeyCredential.toJSON` error (`TypeError: Illegal invocation`)