fix suggestions

Author: twsouthwick

.openpublishing.redirection.json

@@ -989,7 +989,72 @@
             "source_path": "aspnetcore/migration/proper-to-2x/mvc2.md",
             "redirect_url": "migration/mvc/",
             "redirect_document_id": false
-        },        
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/abtesting.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/inc/ab-testing",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/adapters.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/systemweb-adapters",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/blazor.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/inc/blazor",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/http-modules.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/areas/http-modules",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/overview.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/inc/overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/remote-app-setup.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/inc/remote-app-setup",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/remote-authentication.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/inc/remote-authentication",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/remote-session.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/inc/remote-session",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/session.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/inc/session",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/start.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/inc/start",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/unit-testing.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/inc/unit-testing",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/usage_guidance.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/inc/usage_guidance",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/migration/inc/wrapped.md",
+            "redirect_url": "/aspnet/core/migration/fx-to-core/inc/wrapped",
+            "redirect_document_id": false
+        },
         {
             "source_path": "aspnetcore/security/blazor/server-side.md",
             "redirect_url": "/aspnet/core/blazor/security/server/",

aspnetcore/migration/fx-to-core/inc/abtesting.md renamed to aspnetcore/migration/fx-to-core/inc/ab-testing.md

@@ -68,7 +68,7 @@ The `Microsoft.AspNetCore.SystemWebAdapters` namespace is a collection of runtim
 * `Microsoft.AspNetCore.SystemWebAdapters.CoreServices`: This package only targets .NET 6+ and is intended to provide services to ASP.NET Core applications to configure behavior of `System.Web` APIs as well as opting into any behaviors for incremental migration. This is generally not expected to be referenced from libraries, but rather from the applications themselves.
 * `Microsoft.AspNetCore.SystemWebAdapters.Abstractions`: This package is a supporting package that provides abstractions for services used by both the ASP.NET Core and ASP.NET Framework application such as session state serialization.
 
-For examples of scenarios where this is useful, see [the adapters article](xref:migration/fx-to-core/inc/adapters).
+For examples of scenarios where this is useful, see [the adapters article](xref:migration/fx-to-core/systemweb-adapters).
 
 For guidance around usage, see the [usage guidance article](xref:migration/fx-to-core/inc/usage_guidance).
 

aspnetcore/migration/fx-to-core/inc/overview.md

@@ -26,7 +26,7 @@ For ASP.NET Framework Web Forms apps, see <xref:migration/web_forms>.
 
 If you have supporting libraries in your solution that you will need to use, they should be upgraded to .NET Standard 2.0, if possible.  [Upgrade Assistant](https://github.com/dotnet/upgrade-assistant) is a great tool for this. If libraries are unable to target .NET Standard, you can target .NET 6 or later either along with the .NET Framework target in the original project or in a new project alongside the original.
 
-The [adapters](xref:migration/fx-to-core/inc/adapters) can be used in these libraries to enable support for `System.Web.HttpContext` usage in class libraries. In order to enable `System.Web.HttpContext` usage in a library:
+The [adapters](xref:migration/fx-to-core/systemweb-adapters) can be used in these libraries to enable support for `System.Web.HttpContext` usage in class libraries. In order to enable `System.Web.HttpContext` usage in a library:
 
 1. Remove reference to `System.Web` in the project file
 1. Add the `Microsoft.AspNetCore.SystemWebAdapters` package

aspnetcore/migration/fx-to-core/inc/start.md

@@ -14,7 +14,7 @@ This article shows how to upgrade an ASP.NET Framework MVC or Web API app to ASP
 
 ## Upgrade using  the .NET Upgrade Assistant
 
-If your .NET Framework project has supporting libraries in the solution that are required, they should be upgraded to .NET Standard 2.0, if possible. For more information, see [Upgrade supporting libraries](/aspnet/core/migration/fx-to-core/inc/start#upgrade-supporting-libraries).
+If your .NET Framework project has supporting libraries in the solution that are required, they should be upgraded to .NET Standard 2.0, if possible. For more information, see [Upgrade supporting libraries](xref:migration/fx-to-core/inc/start#upgrade-supporting-libraries).
 
 1. Install the [.NET Upgrade Assistant](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant) Visual Studio extension.
 1. Open the ASP.NET MVC or Web API solution in Visual Studio.

aspnetcore/migration/mvc.md

@@ -12,7 +12,7 @@ uid: migration/web_forms
 
 This article shows how to upgrade an ASP.NET Framework Web Forms to ASP.NET Core using the Visual Studio [.NET Upgrade Assistant](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant) and the [incremental update](xref:migration/fx-to-core/inc/overview) approach.
 
-If your .NET Framework project has supporting libraries in its solution that are required, they should be upgraded to .NET Standard 2.0, if possible. For more information, see [Upgrade supporting libraries](/aspnet/core/migration/fx-to-core/inc/start#upgrade-supporting-libraries).
+If your .NET Framework project has supporting libraries in its solution that are required, they should be upgraded to .NET Standard 2.0, if possible. For more information, see [Upgrade supporting libraries](xref:migration/fx-to-core/inc/start#upgrade-supporting-libraries).
 
 1. Install the [.NET Upgrade Assistant](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.upgradeassistant) Visual Studio extension.
 1. Open the ASP.NET Web Forms solution in Visual Studio.

aspnetcore/migration/web_forms.md

@@ -2106,7 +2106,7 @@ items:
             - name: Get started
               uid: migration/fx-to-core/inc/start
             - name: System.Web adapters
-              uid: migration/fx-to-core/inc/adapters
+              uid: migration/fx-to-core/systemweb-adapters
             - name: Remote app setup
               uid: migration/fx-to-core/inc/remote-app-setup
             - name: Usage Guidance