Updates

Author: guardrex

.openpublishing.redirection.json

@@ -1397,6 +1397,11 @@
             "source_path": "aspnetcore/blazor/host-and-deploy/webassembly/integrity-check-failures.md",
             "redirect_url": "/aspnet/core/blazor/host-and-deploy/webassembly/bundle-caching-and-integrity-check-failures",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/performance.md",
+            "redirect_url": "/aspnet/core/blazor/performance/",
+            "redirect_document_id": false
         }
     ]
 }

aspnetcore/blazor/performance/profiling.md

@@ -10,13 +10,13 @@ uid: blazor/performance/profiling
 ---
 # ASP.NET Core Blazor WebAssembly performance profiling and diagnostic counters
 
-[!INCLUDE[](~/includes/not-latest-version.md)]
+[!INCLUDE[](~/includes/not-latest-version-without-not-supported-content.md)]
 
 This article describes performance profiling tools and diagnostic counters for Blazor WebAssembly apps.
 
 ## Prerequisite
 
-Install the [.NET WebAssembly build tools](xref:blazor/webassembly-build-tools-and-aot#net-webassembly-build-tools):
+Install the [.NET WebAssembly build tools](xref:blazor/tooling/webassembly#net-webassembly-build-tools):
 
 ```dotnetcli
 dotnet workload install wasm-tools

aspnetcore/blazor/performance/rendering.md

@@ -219,7 +219,7 @@ To reduce parameter load, bundle multiple parameters in a custom class. For exam
 
 However, keep in mind that bundling primitive parameters into a class isn't always an advantage. While it can reduce parameter count, it also impacts how change detection and rendering behave. Passing non-primitive parameters always triggers a re-render, because Blazor can't know whether arbitrary objects have internally mutable state, whereas passing primitive parameters only triggers a re-render if their values have actually changed.
 
-Also, consider that it might be an improvement not to have a table cell component, as shown in the preceding example, and instead [inline its logic into the parent component](#inline-child-components-into-their-parents).
+Also, consider that it might be an improvement not to have a table cell component, as shown in the preceding example, and instead [inline its logic into the parent component](#avoid-thousands-of-component-instances).
 
 > [!NOTE]
 > When multiple approaches are available for improving performance, benchmarking the approaches is usually required to determine which approach yields the best results.