Remove section and apply further updates (#35451)

Author: guardrex

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

@@ -5,7 +5,7 @@ description: Learn about browser developer tools diagnostics in ASP.NET Core Bla
 monikerRange: '>= aspnetcore-10.0'
 ms.author: riande
 ms.custom: mvc
-ms.date: 05/02/2025
+ms.date: 05/13/2025
 uid: blazor/performance/webassembly-browser-developer-tools
 ---
 # ASP.NET Core Blazor WebAssembly browser developer tools diagnostics
@@ -40,8 +40,10 @@ The MSBuild properties in the following table enable profiler integration.
 Property | Default | Set value to… | Description
 --- | :---: | :---: | ---
 `<WasmProfilers>` | No value | `browser` | Mono profilers to use. Potential values are "`browser`" and "`log`". To use both, separate the values with a semicolon. The `browser` profiler enables integration with the browser's developer tools profiler.
-`<WasmNativeStrip>` | `true` | `false` | Controls stripping the native executable.
-`<WasmNativeDebugSymbols>` | `true` | `true` | Controls building with native debug symbols.
+`<WasmNativeStrip>` | `true` | `false` | Enables stripping the native executable.
+`<WasmNativeDebugSymbols>` | `true` | `true` | Enables building with native debug symbols.
+
+Setting the [`Timing-Allow-Origin` HTTP header](https://developer.mozilla.org/docs/Web/HTTP/Reference/Headers/Timing-Allow-Origin) allows for more precise time measurements.
 
 Enabling profilers has negative size and performance impact, so don't publish an app for production with profilers enabled. In the following example, a condition is set on a property group section that only enables profiling when the app is built with `/p:BlazorSampleProfilingEnabled=true` (.NET CLI) or `<BlazorSampleProfilingEnabled>true</BlazorSampleProfilingEnabled>` in a Visual Studio publish profile, where "`BlazorSampleProfilingEnabled`" is a custom symbol name that you choose and doesn't conflict with other symbol names.
 
@@ -61,9 +63,9 @@ Alternatively, enable features when the app is built with the .NET CLI. The foll
 /p:WasmProfilers=browser /p:WasmNativeStrip=false /p:WasmNativeDebugSymbols=true
 ```
 
-Setting WebAssembly profilers with `<WasmProfilers>browser;</WasmProfilers>` doesn't require AOT.
+Setting WebAssembly profilers with `<WasmProfilers>` doesn't require [ahead-of-time (AOT) compilation](xref:blazor/tooling/webassembly).
 
-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).
+The browser developer tools profiler can be used with AOT (`<RunAOTCompilation>`/`<RunAOTCompilationAfterBuild>` set to `true`) and without WebAssembly profilers (`<WasmProfilers>` removed).
 
 To see AOT method names in the developer tools console, install [DWARF chrome extension](https://chromewebstore.google.com/detail/cc++-devtools-support-dwa/pdcpmagijalfljmkmjngeonclgbbannb).
 
@@ -92,7 +94,6 @@ Permissiable `{FILTER}` placeholder values are shown in the following table.
 Filter | Description
 --- | ---
 `all` | All assemblies
-`none` |	No assemblies
 `program` | Entry point assembly
 `{ASSEMBLY}` | Specifies an assembly (`{ASSEMBLY}`)
 `M:Type:{METHOD}` | Specifies a method (`{METHOD}`)
@@ -107,18 +108,6 @@ In the following example, profiled methods are filtered to the app's namespace,
 <WasmProfilers>browser:callspec=N:{APP NAMESPACE};</WasmProfilers>
 ```
 
-## .NET Core Diagnostics Client Library example
-
-In the project file (`.csproj`), use the `<WasmProfilers>` property set to `browser` to enable integration with the Mono profiler. Currently, only "`browser`" is supported. The `browser` profiler enables integration with the browser's developer tools profiler.
-
-```xml
-<PropertyGroup>
-  <WasmProfilers>browser</WasmProfilers>
-</PropertyGroup>
-```
-
-The [`Timing-Allow-Origin` HTTP header](https://developer.mozilla.org/docs/Web/HTTP/Reference/Headers/Timing-Allow-Origin) allows for more precise time measurements.
-
 ## Additional resources
 
 * [What diagnostic tools are available in .NET Core?](/dotnet/core/diagnostics/)