Blazor integration updates (#34156)

aspnetcore/blazor/host-and-deploy/multiple-hosted-webassembly.md

@@ -66,7 +66,7 @@ The preceding configurations are beyond the scope of this article. For more info
 
 * [Host and deploy articles](xref:host-and-deploy/index)
 * <xref:security/enforcing-ssl>
-* <xref:blazor/components/integration?pivots=webassembly>
+* <xref:blazor/components/integration-hosted-webassembly>
 
 Use an existing hosted Blazor WebAssembly [solution](xref:blazor/tooling#visual-studio-solution-file-sln) or create a [new hosted Blazor WebAssembly solution](xref:blazor/tooling) from the Blazor WebAssembly project template by passing the `-ho|--hosted` option if using the .NET CLI or selecting the **ASP.NET Core Hosted** checkbox in Visual Studio when the project is created in the IDE.
 
@@ -453,7 +453,7 @@ public class HomeController : Controller
 > [!NOTE]
 > The preceding `Index` view is a minimal example purely for demonstration purposes. If the app requires additional MVC assets, such as a layout, styles, scripts, and imports, obtain them from an app created from the MVC project template. For more information, see <xref:tutorials/first-mvc-app/start-mvc>.
 
-For more information on using the Razor components from either of the client apps in pages or views of the server app, see <xref:blazor/components/integration?pivots=webassembly>.
+For more information on using the Razor components from either of the client apps in pages or views of the server app, see <xref:blazor/components/integration-hosted-webassembly>.
 
 ## Run the app
 

aspnetcore/blazor/security/webassembly/additional-scenarios.md

@@ -1283,7 +1283,7 @@ To configure a Blazor WebAssembly app to use the [ASP.NET Core gRPC framework](x
 :::moniker range="< aspnetcore-8.0"
 
 > [!NOTE]
-> Prerendering is enabled by default in hosted Blazor WebAssembly apps, so you must account for the component rendering first from the server and then from the client. Any prerendered state should flow to the client so that it can be reused. For more information, see <xref:blazor/components/integration?pivots=webassembly#persist-prerendered-state>.
+> Prerendering is enabled by default in hosted Blazor WebAssembly apps, so you must account for the component rendering first from the server and then from the client. Any prerendered state should flow to the client so that it can be reused. For more information, see <xref:blazor/components/integration-hosted-webassembly#persist-prerendered-state>.
 
 :::moniker-end
 

aspnetcore/toc.yml

@@ -546,8 +546,10 @@ items:
                 uid: blazor/components/dynamiccomponent
               - name: QuickGrid component
                 uid: blazor/components/quickgrid
-              - name: Prerender and integrate components
+              - name: Integrate with MVC/Razor Pages
                 uid: blazor/components/integration
+              - name: Integrate with MVC/Razor Pages (hosted WebAssembly)
+                uid: blazor/components/integration-hosted-webassembly
               - name: Class libraries
                 uid: blazor/components/class-libraries
               - name: Class libraries with static SSR