Updates

Author: guardrex

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

@@ -87,24 +87,6 @@ Add `callspec` to the `browser` WebAssembly profiler in the `<WasmProfilers>` el
 <WasmProfilers>browser:callspec=N:{APP NAMESPACE};</WasmProfilers>
 ```
 
-Alternatively, configure `callSpec` in `browserProfilerOptions`. Replace the `{APP NAMESPACE}` placeholder in the following example with the app's namespace:
-
-```html
-<script src="_framework/blazor.webassembly#[.{fingerprint}].js" 
-    autostart="false"></script>
-<script>
-  Blazor.start({
-    configureRuntime: function (builder) {
-      builder.withConfig({
-        browserProfilerOptions: {
-          callSpec: "N:{APP NAMESPACE}",
-        }
-      });
-    }
-  });
-</script>
-```
-
 ## .NET Core Diagnostics Client Library example
 
 Parse and validate NetTrace (`.nettrace`) messages using the .NET Core Diagnostics Client Library:
@@ -126,13 +108,11 @@ In the project file (`.csproj`), the properties in the following table enable in
 Property | Default | Set value to&hellip; | 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.
-`<WasmPerfTracing>` | `false` | `true` | Controls diagnostic server tracing.
 `<WasmPerfInstrumentation>` | `false` | `true` | Controls CPU sampling instrumentation for diagnostic server.
 
 ```xml
 <PropertyGroup>
   <WasmProfilers>browser</WasmProfilers>
-  <WasmPerfTracing>true</WasmPerfTracing>
   <WasmPerfInstrumentation>true</WasmPerfInstrumentation>
 </PropertyGroup>
 ```

aspnetcore/blazor/performance/webassembly-event-pipe-diagnostics.md

@@ -37,25 +37,19 @@ dotnet workload install wasm-tools
   * Upload the file via HTTP.
   * Parse and validate that the trace contains the expected method calls.
 
-Built-in diagnostic counters are available to track [Ahead-of-time (AOT) compilation](xref:blazor/tooling/webassembly#ahead-of-time-aot-compilation).
-
 ## GC (Garbage Collector) dumps
 
-* Manual testing
-  * Browser developer tools: Download the `.json` output file, open the file in Visual Studio, and find the expected classes.
-  * [`dotnet-gcdump` (`collect`/convert` options)](/dotnet/core/diagnostics/dotnet-gcdump): To view the captured GC dump files, see [View the GC dump captured from dotnet-gcdump](/dotnet/core/diagnostics/dotnet-gcdump#view-the-gc-dump-captured-from-dotnet-gcdump).
-* Web-based testing
-  * Upload the file via HTTP.
-  * Parse and validate that the trace contains the expected classes.
+* Manual testing:
+
+* Browser developer tools: Download the `.json` output file, open the file in Visual Studio, and find the expected classes.
+* [`dotnet-gcdump` (`collect`/convert` options)](/dotnet/core/diagnostics/dotnet-gcdump): To view the captured GC dump files, see [View the GC dump captured from dotnet-gcdump](/dotnet/core/diagnostics/dotnet-gcdump#view-the-gc-dump-captured-from-dotnet-gcdump).
 
 ## Counters trace
 
-* Manual testing
-  * Browser developer tools: Download the `.json` output file, open the file in Visual Studio, and find the expected counters.
-  * [`dotnet-counters collect`](/dotnet/core/diagnostics/dotnet-counters): Open the `.csv`/`.json` output file in Visual Studio and find the expected counters.
-* Web-based testing
-  * Upload the file via HTTP.
-  * Parse and validate that the trace contains the expected counters.
+Manual testing:
+
+* Browser developer tools: Download the `.json` output file, open the file in Visual Studio, and find the expected counters.
+* [`dotnet-counters collect`](/dotnet/core/diagnostics/dotnet-counters): Open the `.csv`/`.json` output file in Visual Studio and find the expected counters.
 
 ## .NET Core Diagnostics Client Library example
 
@@ -107,14 +101,22 @@ The [`Timing-Allow-Origin` HTTP header](https://developer.mozilla.org/docs/Web/H
 Browser developer tools console calls in the following example that trigger profiling:
 
 * `collectGcDump`: Collect a GC (Garbage Collector) dump.
+
+  ```javascript
+  globalThis.getDotnetRuntime(0).collectGcDump();
+  ```
+
 * `collectPerfCounters(durationSeconds)`: Collect general diagnostic counters.
+
+    ```javascript
+  globalThis.getDotnetRuntime(0).collectPerfCounters({durationSeconds: 60});
+  ```
+
 * `collectCpuSamples(durationSeconds)`: Collect CPU diagnostic counters.
 
-```javascript
-globalThis.getDotnetRuntime(0).collectGcDump();
-globalThis.getDotnetRuntime(0).collectPerfCounters({durationSeconds: 60});
-globalThis.getDotnetRuntime(0).collectCpuSamples({durationSeconds: 60});
-```
+  ```javascript
+  globalThis.getDotnetRuntime(0).collectCpuSamples({durationSeconds: 60});
+  ```
 
 ## Additional resources