add Platform Compat link for VS2022

Author: TerryGLee

docs/porting/port-migrate-and-upgrade-visual-studio-projects.md

@@ -73,7 +73,7 @@ If you don't see a project or file type listed here that should be, consult the
 | SQL - Redgate | Redgate's SQL Change Automation Core (previously called ReadyRoll Core), SQL Prompt Core, and SQL Search are no longer shipping in the Visual Studio installer.<br/><br/>You can continue using Visual Studio 2017 for these features. In Visual Studio 2019, you can upgrade to the paid SQL Change Automation and SQL Prompt products that are available in Redgate's SQL Toolbelt.|
 | SQL Server Reporting Services and SQL Server Analysis Services (SSRS, SSDT, SSAS, MSAS) | Support for these project types is provided through two extensions in the Visual Studio Gallery:  [Microsoft Analysis Services Projects](https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftAnalysisServicesModelingProjects) and [Microsoft Reporting Services Projects](https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio). SSDT support is also included with the Data Storage and Processing workload in Visual Studio 2019. For more information, see the [Download and install SQL Server Data Tools (SSDT) for Visual Studio](/sql/ssdt/download-sql-server-data-tools-ssdt) page. |
 | SQL Server Integration Services (SSIS) | Support for Visual Studio 2019 is available. For more information, see the [Download and install SQL Server Data Tools (SSDT) for Visual Studio](/sql/ssdt/download-sql-server-data-tools-ssdt) page, the [SQL Server Integration Services (SSIS)](https://techcommunity.microsoft.com/t5/SQL-Server-Integration-Services/bg-p/SSIS) team blog, and the [SQL Server Integration Services Projects](https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects&ssr=false#overview) page on the Marketplace. |
-| Test Window Extension | In Visual Studio 2019, some test window APIs that were previously marked public but were never officially documented have been removed. Widely visible APIs were marked deprecated in Visual Studio 2017 to give extension maintainers an early warning. To our knowledge, few extensions have taken a dependency on these APIs. For more info and updates, view the [complete list of deprecated test-related APIs](https://github.com/Microsoft/vstest/issues/1830). If this affects your scenario, please let us know on [Visual Studio Developer Community](https://aka.ms/feedback/suggest?space=8). |
+| Test Window Extension | In Visual Studio 2019, some test window APIs that were previously marked public but were never officially documented have been removed. Widely visible APIs were marked deprecated in Visual Studio 2017 to give extension maintainers an early warning. To our knowledge, few extensions have taken a dependency on these APIs. For more info and updates, view the [complete list of deprecated test-related APIs](https://github.com/Microsoft/vstest/issues/1830). If this affects your scenario, let us know via the [Visual Studio Developer Community](https://aka.ms/feedback/suggest?space=8). |
 | Visual C++ | You can use Visual Studio 2019 to work in projects that were created in earlier versions of Visual Studio back to Visual Studio 2010. When you first open the project, you have the option to upgrade to the latest compiler and toolset or to continue using the original ones. If you choose to keep using the original ones, Visual Studio 2019 doesn't modify the project file, and uses the toolset from the earlier Visual Studio installation to build your project. Keeping the original options means you can still open the project in the original version of Visual Studio if necessary. For more information, see [Use native multi-targeting in Visual Studio to build old projects](/cpp/porting/use-native-multi-targeting). |
 | Visual Studio Extensibility/VSIX | Projects with MinimumVersion 14.0 or less are updated to declare MinimumVersion 15.0, which prevents the project from being opened in earlier versions of Visual Studio. To allow a project to open in earlier versions, set MinimumVersion to `$(VisualStudioVersion)`. See also [How to: Migrate Extensibility Projects to Visual Studio 2017](../extensibility/how-to-migrate-extensibility-projects-to-visual-studio-2017.md). |
 | Visual Studio Lab Management | You can use Microsoft Test Manager or Visual Studio 2010 SP1 and later to open environments created in any of these versions. However, for Visual Studio 2010 SP1 the version of Microsoft Test Manager must match the version of Team Foundation Server before you can create environments. (Important: Team Foundation Server, or TFS, is now known as [Azure DevOps Server](/azure/devops/user-guide/about-azure-devops-services-tfs?view=azure-devops&preserve-view=true).) |
@@ -89,7 +89,7 @@ If you don't see a project or file type listed here that should be, consult the
 
 While we try to maintain compatibility with previous versions, there can be changes that aren't compatible with previous versions. (See [Platform Targeting and Compatibility](/visualstudio/releases/2019/compatibility) for which project types are supported in Visual Studio 2019.) When this happens, a newer version of Visual Studio won't load the project or offer a migration path. You might have to maintain that project in a previous version of Visual Studio.
 
-Sometimes, the newer version of Visual Studio can open a project, but it must update or migrate the project in a way that might render it incompatible with previous versions. Visual Studio uses a number of criteria to determine whether such migration is necessary:
+Sometimes, the newer version of Visual Studio can open a project, but it must update or migrate the project in a way that might render it incompatible with previous versions. Visual Studio uses the following criteria to determine whether such migration is necessary:
 
 - Compatibility with the target versions of platforms, back to Visual Studio 2013 RTM.​
 
@@ -167,7 +167,7 @@ If you don't see a project or file type listed here that should be, consult the
 | SQL - Redgate | Redgate's SQL Change Automation Core (previously called ReadyRoll Core), SQL Prompt Core, and SQL Search are no longer shipping in the Visual Studio installer.<br/><br/>You can continue using Visual Studio 2017 for these features. In Visual Studio 2019, you can upgrade to the paid SQL Change Automation and SQL Prompt products that are available in Redgate's SQL Toolbelt.|
 | SQL Server Reporting Services and SQL Server Analysis Services (SSRS, SSDT, SSAS, MSAS) | Support for these project types is provided through two extensions in the Visual Studio Gallery:  [Microsoft Analysis Services Projects](https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftAnalysisServicesModelingProjects) and [Microsoft Reporting Services Projects](https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio). SSDT support is also included with the Data Storage and Processing workload in Visual Studio 2019. For more information, see the [Download and install SQL Server Data Tools (SSDT) for Visual Studio](/sql/ssdt/download-sql-server-data-tools-ssdt) page. |
 | SQL Server Integration Services (SSIS) | Support for Visual Studio 2019 is available. For more information, see the [Download and install SQL Server Data Tools (SSDT) for Visual Studio](/sql/ssdt/download-sql-server-data-tools-ssdt) page, the [SQL Server Integration Services (SSIS)](https://techcommunity.microsoft.com/t5/SQL-Server-Integration-Services/bg-p/SSIS) team blog, and the [SQL Server Integration Services Projects](https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects&ssr=false#overview) page on the Marketplace. |
-| Test Window Extension | In Visual Studio 2019, some test window APIs that were previously marked public but were never officially documented have been removed. Widely visible APIs were marked deprecated in Visual Studio 2017 to give extension maintainers an early warning. To our knowledge, few extensions have taken a dependency on these APIs. For more info and updates, view the [complete list of deprecated test-related APIs](https://github.com/Microsoft/vstest/issues/1830). If this affects your scenario, please let us know on [Visual Studio Developer Community](https://aka.ms/feedback/suggest?space=8). |
+| Test Window Extension | In Visual Studio 2019, some test window APIs that were previously marked public but were never officially documented have been removed. Widely visible APIs were marked deprecated in Visual Studio 2017 to give extension maintainers an early warning. To our knowledge, few extensions have taken a dependency on these APIs. For more info and updates, view the [complete list of deprecated test-related APIs](https://github.com/Microsoft/vstest/issues/1830). If this affects your scenario, let us know via the [Visual Studio Developer Community](https://aka.ms/feedback/suggest?space=8). |
 | TypeScript | The TypeScript SDK has been deprecated in Visual Studio 2022 and is no longer installed by default in any workload. Projects that compile TypeScript should install the [Microsoft.TypeScript.MSBuild](https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild/) NuGet package. To support projects that can't be upgraded immediately, the TypeScript SDK is still available as an optional component in the Visual Studio installer, as well as in [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.typescript-442). |
 | Visual C++ | You can use Visual Studio 2022 to work in projects that were created in earlier versions of Visual Studio back to Visual Studio 2010. When you first open the project, you have the option to upgrade to the latest compiler and toolset or to continue using the original ones. If you choose to keep using the original ones, Visual Studio 2022 doesn't modify the project file, and uses the toolset from the earlier Visual Studio installation to build your project. Keeping the original options means you can still open the project in the original version of Visual Studio if necessary. For more information, see [Use native multi-targeting in Visual Studio to build old projects](/cpp/porting/use-native-multi-targeting). |
 | Visual Studio Extensibility/VSIX | Projects with MinimumVersion 14.0 or less are updated to declare MinimumVersion 15.0, which prevents the project from being opened in earlier versions of Visual Studio. To allow a project to open in earlier versions, set MinimumVersion to `$(VisualStudioVersion)`. See also [How to: Migrate Extensibility Projects to Visual Studio 2017](../extensibility/how-to-migrate-extensibility-projects-to-visual-studio-2017.md). |
@@ -182,9 +182,9 @@ If you don't see a project or file type listed here that should be, consult the
 
 ## Migrate a project
 
-While we try to maintain compatibility with previous versions, there can be changes that aren't compatible with previous versions. <!--(See [Platform Targeting and Compatibility](/visualstudio/releases/2019/compatibility) for which project types are supported in Visual Studio 2022.)--> When this happens, a newer version of Visual Studio won't load the project or offer a migration path. You might have to maintain that project in a previous version of Visual Studio.
+While we try to maintain compatibility with previous versions, there can be changes that aren't compatible with previous versions. When this happens, a newer version of Visual Studio won't load the project or offer a migration path. You might have to maintain that project in a previous version of Visual Studio. For more information about the project types that are supported in Visual Studio 2022, see the [Platform Targeting and Compatibility](/visualstudio/releases/2022/compatibility) page.
 
-Sometimes, the newer version of Visual Studio can open a project, but it must update or migrate the project in a way that might render it incompatible with previous versions. Visual Studio uses a number of criteria to determine whether such migration is necessary:
+Sometimes, a newer version of Visual Studio can open a project, but it must update or migrate the project in a way that might render it incompatible with previous versions. Visual Studio uses the following criteria to determine whether such migration is necessary:
 
 - Compatibility with the target versions of platforms, back to Visual Studio 2013 RTM.​