Fix broken bookmark links by updating anchor references to match changed headings

Copilot · guardrex · Copilot · commit 4e55f768d852 · 2025-07-22T22:42:15.000Z
Co-authored-by: guardrex &lt;1622880+guardrex@users.noreply.github.com&gt;
diff --git a/aspnetcore/grpc/client.md b/aspnetcore/grpc/client.md
@@ -47,7 +47,7 @@ To configure a gRPC channel to use TLS, ensure the server address starts with `h
 > [!TIP]
 > gRPC supports client certificate authentication over TLS. For information on configuring client certificates with a gRPC channel, see <xref:grpc/authn-and-authz#client-certificate-authentication>.
 
-To call unsecured gRPC services, ensure the server address starts with `http`. For example, `GrpcChannel.ForAddress("http://localhost:5000")` uses HTTP protocol. In .NET Core 3.1, additional configuration is required to [call insecure gRPC services with the .NET client](xref:grpc/troubleshoot#call-insecure-grpc-services-with-net-core-client).
+To call unsecured gRPC services, ensure the server address starts with `http`. For example, `GrpcChannel.ForAddress("http://localhost:5000")` uses HTTP protocol. In .NET Core 3.1, additional configuration is required to [call insecure gRPC services with the .NET client](xref:grpc/troubleshoot#call-insecure-grpc-services-with-net-client).
 
 ### Client performance
 
diff --git a/aspnetcore/grpc/troubleshoot.md b/aspnetcore/grpc/troubleshoot.md
@@ -67,7 +67,7 @@ The .NET gRPC client can call insecure gRPC services by specifing `http` in the
 There are some additional requirements to call insecure gRPC services depending on the .NET version an app is using:
 
 * .NET 5 or later requires [Grpc.Net.Client](https://www.nuget.org/packages/Grpc.Net.Client) version 2.32.0 or later.
-* .NET 3.x requires additional configuration. The app must set the `System.Net.Http.SocketsHttpHandler.Http2UnencryptedSupport` switch to `true`. For more information see [Asp.Net Core 3.x: Call insecure gRPC services with the .NET client](xref:grpc/troubleshoot?view=aspnetcore-3.1#call-insecure-grpc-services-with-net-core-client-2):
+* .NET 3.x requires additional configuration. The app must set the `System.Net.Http.SocketsHttpHandler.Http2UnencryptedSupport` switch to `true`. For more information see [Asp.Net Core 3.x: Call insecure gRPC services with the .NET client](xref:grpc/troubleshoot?view=aspnetcore-3.1#call-insecure-grpc-services-with-net-client-2):
 
 > [!IMPORTANT]
 > Insecure gRPC services must be hosted on a HTTP/2-only port. For more information, see [ASP.NET Core protocol negotiation](xref:grpc/aspnetcore#protocol-negotiation).
diff --git a/aspnetcore/grpc/troubleshoot/includes/troubleshoot3-7.md b/aspnetcore/grpc/troubleshoot/includes/troubleshoot3-7.md
@@ -124,7 +124,7 @@ builder.WebHost.ConfigureKestrel(options =>
 
 When an HTTP/2 endpoint is configured without TLS, the endpoint's [ListenOptions.Protocols](xref:fundamentals/servers/kestrel/endpoints#listenoptionsprotocols) must be set to `HttpProtocols.Http2`. `HttpProtocols.Http1AndHttp2` can't be used because TLS is required to negotiate HTTP/2. Without TLS, all connections to the endpoint default to HTTP/1.1, and gRPC calls fail.
 
-The gRPC client must also be configured to not use TLS. For more information, see [Call insecure gRPC services with .NET client](#call-insecure-grpc-services-with-net-core-client).
+The gRPC client must also be configured to not use TLS. For more information, see [Call insecure gRPC services with .NET client](#call-insecure-grpc-services-with-net-client).
 
 > [!WARNING]
 > HTTP/2 without TLS should only be used during app development. Production apps should always use transport security. For more information, see [Security considerations in gRPC for ASP.NET Core](xref:grpc/security#transport-security).
@@ -466,7 +466,7 @@ public static IHostBuilder CreateHostBuilder(string[] args) =>
 
 When an HTTP/2 endpoint is configured without TLS, the endpoint's [ListenOptions.Protocols](xref:fundamentals/servers/kestrel/endpoints#listenoptionsprotocols) must be set to `HttpProtocols.Http2`. `HttpProtocols.Http1AndHttp2` can't be used because TLS is required to negotiate HTTP/2. Without TLS, all connections to the endpoint default to HTTP/1.1, and gRPC calls fail.
 
-The gRPC client must also be configured to not use TLS. For more information, see [Call insecure gRPC services with .NET client](#call-insecure-grpc-services-with-net-core-client).
+The gRPC client must also be configured to not use TLS. For more information, see [Call insecure gRPC services with .NET client](#call-insecure-grpc-services-with-net-client).
 
 > [!WARNING]
 > HTTP/2 without TLS should only be used during app development. Production apps should always use transport security. For more information, see [Security considerations in gRPC for ASP.NET Core](xref:grpc/security#transport-security).
@@ -715,7 +715,7 @@ public static IHostBuilder CreateHostBuilder(string[] args) =>
 
 When an HTTP/2 endpoint is configured without TLS, the endpoint's [ListenOptions.Protocols](xref:fundamentals/servers/kestrel#listenoptionsprotocols) must be set to `HttpProtocols.Http2`. `HttpProtocols.Http1AndHttp2` can't be used because TLS is required to negotiate HTTP/2. Without TLS, all connections to the endpoint default to HTTP/1.1, and gRPC calls fail.
 
-The gRPC client must also be configured to not use TLS. For more information, see [Call insecure gRPC services with .NET client](#call-insecure-grpc-services-with-net-core-client).
+The gRPC client must also be configured to not use TLS. For more information, see [Call insecure gRPC services with .NET client](#call-insecure-grpc-services-with-net-client).
 
 > [!WARNING]
 > HTTP/2 without TLS should only be used during app development. Production apps should always use transport security. For more information, see [Security considerations in gRPC for ASP.NET Core](xref:grpc/security#transport-security).
diff --git a/aspnetcore/host-and-deploy/aspnet-core-module.md b/aspnetcore/host-and-deploy/aspnet-core-module.md
@@ -143,7 +143,7 @@ The ASP.NET Core Module can also:
 
 ## How to install and use the ASP.NET Core Module (ANCM)
 
-For instructions on how to install the ASP.NET Core Module, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle). The ASP.NET Core Module is forward and backward compatible with [in-support releases of .NET](https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle).
+For instructions on how to install the ASP.NET Core Module, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle). The ASP.NET Core Module is forward and backward compatible with [in-support releases of .NET](https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle).
 
 [!INCLUDE[](~/includes/announcements.md)]
 
@@ -560,7 +560,7 @@ The ASP.NET Core Module can also:
 
 ## How to install and use the ASP.NET Core Module (ANCM)
 
-For instructions on how to install the ASP.NET Core Module, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle). The ASP.NET Core Module is forward and backward compatible with [in-support releases of .NET](https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle).
+For instructions on how to install the ASP.NET Core Module, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle). The ASP.NET Core Module is forward and backward compatible with [in-support releases of .NET](https://dotnet.microsoft.com/platform/support/policy/dotnet-core#lifecycle).
 
 [!INCLUDE[](~/includes/announcements.md)]
 
@@ -877,7 +877,7 @@ The ASP.NET Core Module can also:
 
 ## How to install and use the ASP.NET Core Module (ANCM)
 
-For instructions on how to install the ASP.NET Core Module, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle).
+For instructions on how to install the ASP.NET Core Module, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle).
 
 ## Configuration with web.config
 
diff --git a/aspnetcore/host-and-deploy/azure-apps/index.md b/aspnetcore/host-and-deploy/azure-apps/index.md
@@ -146,7 +146,7 @@ For more information, see <xref:security/data-protection/implementation/key-stor
 
 To deploy an app that uses a preview release of .NET, see the following resources. These approaches are also used when the runtime is available but the SDK hasn't been installed on Azure App Service.
 
-* [Specify the .NET SDK Version using Azure Pipelines](#specify-the-net-core-sdk-version-using-azure-pipelines)
+* [Specify the .NET SDK Version using Azure Pipelines](#specify-the-net-sdk-version-using-azure-pipelines)
 * [Deploy a self-contained preview app](#deploy-a-self-contained-preview-app)
 * [Use Docker with Web Apps for containers](#use-docker-with-web-apps-for-containers)
 * [Install the preview site extension](#install-the-preview-site-extension)
diff --git a/aspnetcore/host-and-deploy/azure-iis-errors-reference.md b/aspnetcore/host-and-deploy/azure-iis-errors-reference.md
@@ -42,7 +42,7 @@ The list of errors in this topic isn't exhaustive. If you encounter an error not
 
 Troubleshooting:
 
-Non-OS files in the **C:\Windows\SysWOW64\inetsrv** directory aren't preserved during an OS upgrade. If the ASP.NET Core Module is installed prior to an OS upgrade and then any app pool is run in 32-bit mode after an OS upgrade, this issue is encountered. After an OS upgrade, repair the ASP.NET Core Module. See [Install the .NET Hosting bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle). Select **Repair** when the installer is run.
+Non-OS files in the **C:\Windows\SysWOW64\inetsrv** directory aren't preserved during an OS upgrade. If the ASP.NET Core Module is installed prior to an OS upgrade and then any app pool is run in 32-bit mode after an OS upgrade, this issue is encountered. After an OS upgrade, repair the ASP.NET Core Module. See [Install the .NET Hosting bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle). Select **Repair** when the installer is run.
 
 ## Missing site extension, 32-bit (x86) and 64-bit (x64) site extensions installed, or wrong process bitness set
 
@@ -159,7 +159,7 @@ Troubleshooting:
 
   [Current .NET Hosting Bundle installer (direct download)](https://dotnet.microsoft.com/permalink/dotnetcore-current-windows-runtime-bundle-installer)
 
-  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle).
+  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle).
 
 * Make sure that the **Application Pool** > **Process Model** > **Identity** is set to **ApplicationPoolIdentity** or the custom identity has the correct permissions to access the app's deployment folder.
 
@@ -197,7 +197,7 @@ Troubleshooting:
 
   [Current .NET Hosting Bundle installer (direct download)](https://dotnet.microsoft.com/permalink/dotnetcore-current-windows-runtime-bundle-installer)
 
-  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle).
+  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle).
 
   If a specific runtime is required, download the runtime from the [.NET Downloads](https://dotnet.microsoft.com/download/dotnet) page and install it on the system. Complete the installation by restarting the system or restarting IIS by executing **net stop was /y** followed by **net start w3svc** from a command prompt.
 
diff --git a/aspnetcore/host-and-deploy/azure-iis-errors-reference/includes/azure-iis-errors-reference2-2.md b/aspnetcore/host-and-deploy/azure-iis-errors-reference/includes/azure-iis-errors-reference2-2.md
@@ -28,7 +28,7 @@ The list of errors in this topic isn't exhaustive. If you encounter an error not
 
 Troubleshooting:
 
-Non-OS files in the **C:\Windows\SysWOW64\inetsrv** directory aren't preserved during an OS upgrade. If the ASP.NET Core Module is installed prior to an OS upgrade and then any app pool is run in 32-bit mode after an OS upgrade, this issue is encountered. After an OS upgrade, repair the ASP.NET Core Module. See [Install the .NET Hosting bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle). Select **Repair** when the installer is run.
+Non-OS files in the **C:\Windows\SysWOW64\inetsrv** directory aren't preserved during an OS upgrade. If the ASP.NET Core Module is installed prior to an OS upgrade and then any app pool is run in 32-bit mode after an OS upgrade, this issue is encountered. After an OS upgrade, repair the ASP.NET Core Module. See [Install the .NET Hosting bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle). Select **Repair** when the installer is run.
 
 ## Missing site extension, 32-bit (x86) and 64-bit (x64) site extensions installed, or wrong process bitness set
 
@@ -145,7 +145,7 @@ Troubleshooting:
 
   [Current .NET Hosting Bundle installer (direct download)](https://dotnet.microsoft.com/permalink/dotnetcore-current-windows-runtime-bundle-installer)
 
-  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle).
+  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle).
 
 * Make sure that the **Application Pool** > **Process Model** > **Identity** is set to **ApplicationPoolIdentity** or the custom identity has the correct permissions to access the app's deployment folder.
 
@@ -183,7 +183,7 @@ Troubleshooting:
 
   [Current .NET Hosting Bundle installer (direct download)](https://dotnet.microsoft.com/permalink/dotnetcore-current-windows-runtime-bundle-installer)
 
-  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle).
+  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle).
 
   If a specific runtime is required, download the runtime from the [.NET Downloads](https://dotnet.microsoft.com/download/dotnet) page and install it on the system. Complete the installation by restarting the system or restarting IIS by executing **net stop was /y** followed by **net start w3svc** from a command prompt.
 
@@ -316,7 +316,7 @@ The list of errors in this topic isn't exhaustive. If you encounter an error not
 
 Troubleshooting:
 
-Non-OS files in the **C:\Windows\SysWOW64\inetsrv** directory aren't preserved during an OS upgrade. If the ASP.NET Core Module is installed prior to an OS upgrade and then any app pool is run in 32-bit mode after an OS upgrade, this issue is encountered. After an OS upgrade, repair the ASP.NET Core Module. See [Install the .NET Hosting bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle). Select **Repair** when the installer is run.
+Non-OS files in the **C:\Windows\SysWOW64\inetsrv** directory aren't preserved during an OS upgrade. If the ASP.NET Core Module is installed prior to an OS upgrade and then any app pool is run in 32-bit mode after an OS upgrade, this issue is encountered. After an OS upgrade, repair the ASP.NET Core Module. See [Install the .NET Hosting bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle). Select **Repair** when the installer is run.
 
 ## Missing site extension, 32-bit (x86) and 64-bit (x64) site extensions installed, or wrong process bitness set
 
@@ -423,7 +423,7 @@ Troubleshooting:
 
   [Current .NET Hosting Bundle installer (direct download)](https://dotnet.microsoft.com/permalink/dotnetcore-current-windows-runtime-bundle-installer)
 
-  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle).
+  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle).
 
 * Make sure that the **Application Pool** > **Process Model** > **Identity** is set to **ApplicationPoolIdentity** or the custom identity has the correct permissions to access the app's deployment folder.
 
@@ -459,7 +459,7 @@ Troubleshooting:
 
   [Current .NET Hosting Bundle installer (direct download)](https://dotnet.microsoft.com/permalink/dotnetcore-current-windows-runtime-bundle-installer)
 
-  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-core-hosting-bundle).
+  For more information, see [Install the .NET Hosting Bundle](xref:host-and-deploy/iis/index#install-the-net-hosting-bundle).
 
   If a specific runtime is required, download the runtime from the [.NET Downloads](https://dotnet.microsoft.com/download/dotnet) page and install it on the system. Complete the installation by restarting the system or restarting IIS by executing **net stop was /y** followed by **net start w3svc** from a command prompt.
 
diff --git a/aspnetcore/host-and-deploy/iis/hosting-bundle.md b/aspnetcore/host-and-deploy/iis/hosting-bundle.md
@@ -19,7 +19,7 @@ The .NET Hosting bundle is an installer for the .NET Runtime and the [ASP.NET Co
 > [!IMPORTANT]
 > If the Hosting Bundle is installed before IIS, the bundle installation must be repaired. Run the Hosting Bundle installer again after installing IIS.
 >
-> If the Hosting Bundle is installed after installing the 64-bit (x64) version of .NET, SDKs might appear to be missing ([No .NET SDKs were detected](xref:test/troubleshoot#no-net-core-sdks-were-detected)). To resolve the problem, see <xref:test/troubleshoot#missing-sdk-after-installing-the-net-core-hosting-bundle>.
+> If the Hosting Bundle is installed after installing the 64-bit (x64) version of .NET, SDKs might appear to be missing ([No .NET SDKs were detected](xref:test/troubleshoot#no-net-sdks-were-detected)). To resolve the problem, see <xref:test/troubleshoot#missing-sdk-after-installing-the-net-hosting-bundle>.
 
 [!INCLUDE[](~/includes/announcements.md)]
 
diff --git a/aspnetcore/host-and-deploy/iis/index.md b/aspnetcore/host-and-deploy/iis/index.md
@@ -83,7 +83,7 @@ For information on apps that must protect a subset of the app with a certificate
 
 For a tutorial experience on publishing an ASP.NET Core app to an IIS server, see <xref:tutorials/publish-to-iis>.
 
-[Install the .NET Hosting Bundle](#install-the-net-core-hosting-bundle)
+[Install the .NET Hosting Bundle](#install-the-net-hosting-bundle)
 
 ## Supported operating systems
 
@@ -316,7 +316,7 @@ Install the *.NET Hosting Bundle* on the hosting system. The bundle installs the
 > [!IMPORTANT]
 > If the Hosting Bundle is installed before IIS, the bundle installation must be repaired. Run the Hosting Bundle installer again after installing IIS.
 >
-> If the Hosting Bundle is installed after installing the 64-bit (x64) version of .NET, SDKs might appear to be missing ([No .NET SDKs were detected](xref:test/troubleshoot#no-net-core-sdks-were-detected)). To resolve the problem, see <xref:test/troubleshoot#missing-sdk-after-installing-the-net-core-hosting-bundle>.
+> If the Hosting Bundle is installed after installing the 64-bit (x64) version of .NET, SDKs might appear to be missing ([No .NET SDKs were detected](xref:test/troubleshoot#no-net-sdks-were-detected)). To resolve the problem, see <xref:test/troubleshoot#missing-sdk-after-installing-the-net-hosting-bundle>.
 
 ### Direct download (current version)
 
@@ -711,7 +711,7 @@ To prevent apps hosted [out-of-process](#out-of-process-hosting-model) from timi
 
 For a tutorial experience on publishing an ASP.NET Core app to an IIS server, see <xref:tutorials/publish-to-iis>.
 
-[Install the .NET Hosting Bundle](#install-the-net-core-hosting-bundle)
+[Install the .NET Hosting Bundle](#install-the-net-hosting-bundle)
 
 ## Supported operating systems
 
@@ -895,7 +895,7 @@ Install the *.NET Hosting Bundle* on the hosting system. The bundle installs the
 > [!IMPORTANT]
 > If the Hosting Bundle is installed before IIS, the bundle installation must be repaired. Run the Hosting Bundle installer again after installing IIS.
 >
-> If the Hosting Bundle is installed after installing the 64-bit (x64) version of .NET, SDKs might appear to be missing ([No .NET SDKs were detected](xref:test/troubleshoot#no-net-core-sdks-were-detected)). To resolve the problem, see <xref:test/troubleshoot#missing-sdk-after-installing-the-net-core-hosting-bundle>.
+> If the Hosting Bundle is installed after installing the 64-bit (x64) version of .NET, SDKs might appear to be missing ([No .NET SDKs were detected](xref:test/troubleshoot#no-net-sdks-were-detected)). To resolve the problem, see <xref:test/troubleshoot#missing-sdk-after-installing-the-net-hosting-bundle>.
 
 ### Download
 
diff --git a/aspnetcore/test/troubleshoot-azure-iis.md b/aspnetcore/test/troubleshoot-azure-iis.md
diff --git a/aspnetcore/test/troubleshoot-azure-iis/includes/troubleshoot-azure-iis7.md b/aspnetcore/test/troubleshoot-azure-iis/includes/troubleshoot-azure-iis7.md
diff --git a/aspnetcore/test/troubleshoot.md b/aspnetcore/test/troubleshoot.md
diff --git a/aspnetcore/test/troubleshoot/includes/troubleshoot5.md b/aspnetcore/test/troubleshoot/includes/troubleshoot5.md

Original file line number	Diff line number	Diff line change
`@@ -19,7 +19,7 @@ The .NET Hosting bundle is an installer for the .NET Runtime and the [ASP.NET Co`
`19`	`19`	`> [!IMPORTANT]`
`20`	`20`	`> If the Hosting Bundle is installed before IIS, the bundle installation must be repaired. Run the Hosting Bundle installer again after installing IIS.`
`21`	`21`	`>`
`22`		`-> If the Hosting Bundle is installed after installing the 64-bit (x64) version of .NET, SDKs might appear to be missing ([No .NET SDKs were detected](xref:test/troubleshoot#no-net-core-sdks-were-detected)). To resolve the problem, see <xref:test/troubleshoot#missing-sdk-after-installing-the-net-core-hosting-bundle>.`
	`22`	`+> If the Hosting Bundle is installed after installing the 64-bit (x64) version of .NET, SDKs might appear to be missing ([No .NET SDKs were detected](xref:test/troubleshoot#no-net-sdks-were-detected)). To resolve the problem, see <xref:test/troubleshoot#missing-sdk-after-installing-the-net-hosting-bundle>.`
`23`	`23`
`24`	`24`	`[!INCLUDE[](~/includes/announcements.md)]`
`25`	`25`