Updates

Author: guardrex

aspnetcore/blazor/performance/browser-developer-tools-profiling.md renamed to aspnetcore/blazor/performance/webassembly-browser-developer-tools-diagnostics.md

@@ -1,22 +1,22 @@
 ---
-title: ASP.NET Core Blazor WebAssembly browser developer tools diagnostic profiling
+title: ASP.NET Core Blazor WebAssembly browser developer tools diagnostics
 author: guardrex
-description: Learn about browser developer tools diagnostic profiling in ASP.NET Core Blazor WebAssembly apps.
+description: Learn about browser developer tools diagnostics in ASP.NET Core Blazor WebAssembly apps.
 monikerRange: '>= aspnetcore-10.0'
 ms.author: riande
 ms.custom: mvc
 ms.date: 04/30/2025
-uid: blazor/performance/browser-developer-tools
+uid: blazor/performance/webassembly-browser-developer-tools
 ---
-# ASP.NET Core Blazor WebAssembly browser developer tools diagnostic profiling
+# ASP.NET Core Blazor WebAssembly browser developer tools diagnostics
 
 <!-- UPDATE 10.0 - Activate ...
 
 [!INCLUDE[](~/includes/not-latest-version.md)]
 
 -->
 
-This article describes browser developer tools diagnostic profiling tools in Blazor WebAssembly apps.
+This article describes browser developer tools diagnostic tools in Blazor WebAssembly apps.
 
 ## Prerequisite
 
@@ -56,17 +56,16 @@ In the app's project file (`.csproj`):
   <WasmProfilers>browser;</WasmProfilers>
   <WasmNativeStrip>false</WasmNativeStrip>
   <WasmNativeDebugSymbols>true</WasmNativeDebugSymbols>
-  <WasmBuildNative>true</WasmBuildNative>
 </PropertyGroup>
 ```
 
 Alternatively, enable features when the app is built with the .NET CLI. The following options passed to the `dotnet build` command mirror the preceding MS Build property configuration:
 
 ```dotnetcli
-/p:WasmProfilers=browser /p:WasmNativeStrip=false /p:WasmNativeDebugSymbols=true /p:WasmBuildNative=true
+/p:WasmProfilers=browser /p:WasmNativeStrip=false /p:WasmNativeDebugSymbols=true
 ```
 
-Setting WebAssembly profilers with `<WasmProfilers>browser;</WasmProfilers>` doesn't require AOT (`<RunAOTCompilation>`/`<RunAOTCompilationAfterBuild>` set to `false` or removed from the preceding properity group).
+Setting WebAssembly profilers with `<WasmProfilers>browser;</WasmProfilers>` doesn't require AOT (`<RunAOTCompilation>`/`<RunAOTCompilationAfterBuild>` set to `false` or removed from the preceding property group).
 
 The browser developer tools profiler can be used with AOT (`<RunAOTCompilation>`/`<RunAOTCompilationAfterBuild>` set to `true`) and without WebAssembly profilers (`<WasmProfilers>browser;</WasmProfilers>` removed from the preceding property group).
 

aspnetcore/blazor/performance/event-pipe-profiling.md renamed to aspnetcore/blazor/performance/webassembly-event-pipe-diagnostics.md

@@ -1,22 +1,22 @@
 ---
-title: ASP.NET Core Blazor WebAssembly Event Pipe diagnostic profiling
+title: ASP.NET Core Blazor WebAssembly Event Pipe diagnostics
 author: guardrex
-description: Learn about Event Pipe diagnostic profiling, counters, and how to get a Garbage Collector heap dump in ASP.NET Core Blazor WebAssembly apps.
+description: Learn about Event Pipe diagnostics and how to get a Garbage Collector heap dump in ASP.NET Core Blazor WebAssembly apps.
 monikerRange: '>= aspnetcore-10.0'
 ms.author: riande
 ms.custom: mvc
 ms.date: 04/30/2025
-uid: blazor/performance/event-pipe
+uid: blazor/performance/webassembly-event-pipe
 ---
-# ASP.NET Core Blazor WebAssembly Event Pipe diagnostic profiling
+# ASP.NET Core Blazor WebAssembly Event Pipe diagnostics
 
 <!-- UPDATE 10.0 - Activate ...
 
 [!INCLUDE[](~/includes/not-latest-version.md)]
 
 -->
 
-This article describes Event Pipe diagnostic profiling tools, counters, and how to get a Garbage Collector heap dump in Blazor WebAssembly apps.
+This article describes Event Pipe diagnostic tools, counters, and how to get a Garbage Collector heap dump in Blazor WebAssembly apps.
 
 ## Prerequisite
 

aspnetcore/performance/diagnostic-tools.md

@@ -13,7 +13,7 @@ By [Mike Rousos](https://github.com/mjrousos)
 
 This article lists tools for diagnosing performance issues in ASP.NET Core.
 
-For information on Blazor WebAssembly performance diagnostic tools and counters, see <xref:blazor/performance/browser-developer-tools> and <xref:blazor/performance/event-pipe>.
+For information on Blazor WebAssembly performance diagnostic tools and counters, see <xref:blazor/performance/webassembly-browser-developer-tools> and <xref:blazor/performance/webassembly-event-pipe>.
 
 ## Visual Studio Diagnostic Tools
 

aspnetcore/release-notes/aspnetcore-10/includes/blazor.md

@@ -350,7 +350,7 @@ For more information, see the following sections of the *Call JavaScript functio
 
 New performance profiling and diagnostic counters are available for Blazor WebAssembly apps. For more information, see the following articles:
 
-* <xref:blazor/performance/browser-developer-tools>
-* <xref:blazor/performance/event-pipe>
+* <xref:blazor/performance/webassembly-browser-developer-tools>
+* <xref:blazor/performance/webassembly-event-pipe>
 
 -->

aspnetcore/toc.yml

@@ -661,9 +661,9 @@ items:
               - name: JavaScript interop
                 uid: blazor/performance/js-interop
               - name: WebAssembly browser developer tools diagnostics
-                uid: blazor/performance/browser-developer-tools
+                uid: blazor/performance/webassembly-browser-developer-tools
               - name: WebAssembly Event Pipe diagnostics
-                uid: blazor/performance/event-pipe
+                uid: blazor/performance/webassembly-event-pipe
           - name: Test components
             uid: blazor/test
           - name: Progressive Web Applications