dotnet · mairaw · Dec 4, 2019 · Dec 3, 2019 · Dec 3, 2019 · Dec 4, 2019
diff --git a/docs/framework/data/adonet/how-to-create-a-linq-to-dataset-project-in-vs.md b/docs/framework/data/adonet/how-to-create-a-linq-to-dataset-project-in-vs.md
@@ -1,13 +1,13 @@
 ---
-title: Create a LINQ to DataSet project In Visual Studio
+title: Create a LINQ to DataSet project in Visual Studio
 ms.date: 08/15/2018
 ms.assetid: 49ba6cb0-cdd2-4571-aeaa-25bf0f40e9b3
 ---
-# How to: Create a LINQ to DataSet project In Visual Studio
+# How to: Create a LINQ to DataSet project in Visual Studio
 
 The different types of LINQ projects require certain assembly references and imported namespaces (Visual Basic) or [using](../../../csharp/language-reference/keywords/using-directive.md) directives (C#). The minimum requirement for LINQ is a reference to *System.Core.dll* and a `using` directive for <xref:System.Linq>.
 
-These requirements are supplied by default if you create a new C# console app project in Visual Studio 2017. If you're upgrading a project from an earlier version of Visual Studio, you might have to supply these LINQ-related references manually.
+These requirements are supplied by default if you create a new C# console app project in Visual Studio 2017 or a later version. If you're upgrading a project from an earlier version of Visual Studio, you might have to supply these LINQ-related references manually.
 
 LINQ to DataSet requires two additional references to *System.Data.dll* and *System.Data.DataSetExtensions.dll*.
 

diff --git a/docs/framework/data/wcf/create-a-data-service-using-an-adonet-ef-data-wcf.md b/docs/framework/data/wcf/create-a-data-service-using-an-adonet-ef-data-wcf.md
@@ -54,7 +54,7 @@ The Entity Framework also provides a command line tool that can generate an Enti
    ![WCF Data Service item template in Visual Studio 2015](./media/wcf-data-service-item-template.png)
 
    > [!NOTE]
-   > The **WCF Data Service** template is available in Visual Studio 2015, but not in Visual Studio 2017.
+   > The **WCF Data Service** template is available in Visual Studio 2015, but not in Visual Studio 2017 or later.
 
 5. Supply a name for the service, and then click **OK**.
 

diff --git a/docs/framework/data/wcf/create-a-data-service-using-linq-to-sql-wcf.md b/docs/framework/data/wcf/create-a-data-service-using-linq-to-sql-wcf.md
@@ -49,7 +49,7 @@ WCF Data Services exposes entity data as a data service. The reflection provider
    ![WCF Data Service item template in Visual Studio 2015](./media/wcf-data-service-item-template.png)
 
    > [!NOTE]
-   > The **WCF Data Service** template is available in Visual Studio 2015, but not in Visual Studio 2017.
+   > The **WCF Data Service** template is available in Visual Studio 2015, but not in Visual Studio 2017 or later.
 
 3. Supply a name for the service, and then click **OK**.
 

diff --git a/docs/framework/data/wcf/creating-the-data-service.md b/docs/framework/data/wcf/creating-the-data-service.md
@@ -65,7 +65,7 @@ In this topic, you create a sample data service that uses WCF Data Services to e
    ![WCF Data Service item template in Visual Studio 2015](./media/wcf-data-service-item-template.png)
 
    > [!NOTE]
-   > The **WCF Data Service** template is available in Visual Studio 2015, but not in Visual Studio 2017.
+   > The **WCF Data Service** template is available in Visual Studio 2015, but not in Visual Studio 2017 or later.
 
 3. For the name of the service, type `Northwind`.
 

diff --git a/docs/framework/data/wcf/how-to-develop-a-wcf-data-service-running-on-iis.md b/docs/framework/data/wcf/how-to-develop-a-wcf-data-service-running-on-iis.md
@@ -145,7 +145,7 @@ After you create the service, you must explicitly provide access to data service
    ![WCF Data Service item template in Visual Studio 2015](./media/wcf-data-service-item-template.png)
 
    > [!NOTE]
-   > The **WCF Data Service** template is available in Visual Studio 2015, but not in Visual Studio 2017.
+   > The **WCF Data Service** template is available in Visual Studio 2015, but not in Visual Studio 2017 or later.
 
 3. For the name of the service, enter `Northwind`.
 

diff --git a/docs/framework/data/wcf/quickstart-wcf-data-services.md b/docs/framework/data/wcf/quickstart-wcf-data-services.md
@@ -20,7 +20,7 @@ To complete this quickstart, you must install the following components:
 
 - Visual Studio
 
-- An instance of SQL Server. This includes SQL Server Express, which is included in a default installation of Visual Studio 2015, or as part of the **Data storage and processing** workload in Visual Studio 2017.
+- An instance of SQL Server. This includes SQL Server Express, which is included in a default installation of Visual Studio 2015, or as part of the **Data storage and processing** workload in Visual Studio 2017 or later.
 
 - The Northwind sample database. To download this sample database, see the download page, [Sample Databases for SQL Server](https://go.microsoft.com/fwlink/?linkid=24758).
 

diff --git a/docs/framework/debug-trace-profile/pinvokestackimbalance-mda.md b/docs/framework/debug-trace-profile/pinvokestackimbalance-mda.md
@@ -20,7 +20,7 @@ The `PInvokeStackImbalance` managed debugging assistant (MDA) is activated when
 The `PInvokeStackImbalance` MDA is implemented only for 32-bit x86 platforms.
 
 > [!NOTE]
-> The `PInvokeStackImbalance` MDA is disabled by default. In Visual Studio 2017, The `PInvokeStackImbalance` MDA appears in the **Managed Debugging Assistants** list in the **Exception Settings** dialog box (which is displayed when you select **Debug** > **Windows** > **Exception Settings**). However, selecting or clearing the **Break When Thrown** check box does not enable or disable the MDA; it only controls whether Visual Studio throws an exception when the MDA is activated.
+> The `PInvokeStackImbalance` MDA is disabled by default. In Visual Studio 2017 and later versions, the `PInvokeStackImbalance` MDA appears in the **Managed Debugging Assistants** list in the **Exception Settings** dialog box (which is displayed when you select **Debug** > **Windows** > **Exception Settings**). However, selecting or clearing the **Break When Thrown** check box does not enable or disable the MDA; it only controls whether Visual Studio throws an exception when the MDA is activated.
 
 ## Symptoms
 

diff --git a/docs/framework/whats-new/index.md b/docs/framework/whats-new/index.md
@@ -2125,5 +2125,6 @@ The Portable Class Library project in Visual Studio 2012 (and later versions) en
 - [The .NET Framework and Out-of-Band Releases](../get-started/the-net-framework-and-out-of-band-releases.md)
 - [What's new in accessibility in the .NET Framework](whats-new-in-accessibility.md)
 - [What's New in Visual Studio 2017](/visualstudio/ide/whats-new-visual-studio-2017)
+- [What's New in Visual Studio 2019](/visualstudio/ide/whats-new-visual-studio-2019)
 - [ASP.NET](/aspnet)
 - [What's New for C++ in Visual Studio](/cpp/what-s-new-for-visual-cpp-in-visual-studio)
diff --git a/docs/visual-basic/getting-started/breaking-changes-in-visual-studio.md b/docs/visual-basic/getting-started/breaking-changes-in-visual-studio.md
@@ -7,7 +7,7 @@ ms.assetid: 708fb176-35eb-4cbc-a6e7-a04c6e3bdaff
 ---
 # Visual Basic Breaking Changes in Visual Studio
 
-For the latest documentation on Visual Studio 2017, see [Visual Studio 2017 Documentation](https://docs.microsoft.com/visualstudio/).
+For the latest documentation on Visual Studio, see the [Visual Studio documentation](/visualstudio/).
 
 No changes in Visual Basic in Visual Studio 2015 will prevent an application that was created in Visual Basic in Visual Studio 2013 from compiling or change the run-time behavior of such an application.  
 

diff --git a/docs/visual-basic/getting-started/whats-new.md b/docs/visual-basic/getting-started/whats-new.md
@@ -286,3 +286,4 @@ Now the compiler will use normal overload resolution rules to choose the most ap
 ## See also
 
 - [What's New in Visual Studio 2017](/visualstudio/ide/whats-new-visual-studio-2017)
+- [What's New in Visual Studio 2019](/visualstudio/ide/whats-new-visual-studio-2019)
diff --git a/includes/net-standard-table.md b/includes/net-standard-table.md
@@ -9,7 +9,7 @@
 | Universal Windows Platform | 10.0   | 10.0   | 10.0  | 10.0  | 10.0  | 10.0.16299         | 10.0.16299         | 10.0.16299          | TBD |
 | Unity                      | 2018.1 | 2018.1 | 2018.1| 2018.1| 2018.1| 2018.1             |  2018.1            | 2018.1              | TBD |
 
-<sup>1 The versions listed for .NET Framework apply to .NET Core 2.0 SDK and later versions of the tooling. Older versions used a different mapping for .NET Standard 1.5 and higher. You can [download tooling for .NET Core tools for Visual Studio 2015](https://github.com/dotnet/core/blob/master/release-notes/download-archive.md) if you cannot upgrade to Visual Studio 2017.</sup>
+<sup>1 The versions listed for .NET Framework apply to .NET Core 2.0 SDK and later versions of the tooling. Older versions used a different mapping for .NET Standard 1.5 and higher. You can [download tooling for .NET Core tools for Visual Studio 2015](https://github.com/dotnet/core/blob/master/release-notes/download-archive.md) if you cannot upgrade to Visual Studio 2017 or a later version.</sup>
 
 <sup>2 The versions listed here represent the rules that NuGet uses to determine whether a given .NET Standard library is applicable. While NuGet considers .NET Framework 4.6.1 as supporting .NET Standard 1.5 through 2.0, there are several issues with consuming .NET Standard libraries that were built for those versions from .NET Framework 4.6.1 projects. For .NET Framework projects that need to use such libraries, we recommend that you upgrade the project to target .NET Framework 4.7.2 or higher.</sup>
Original file line number	Diff line number	Diff line change
Expand Up		@@ -286,3 +286,4 @@ Now the compiler will use normal overload resolution rules to choose the most ap
		## See also

		- [What's New in Visual Studio 2017](/visualstudio/ide/whats-new-visual-studio-2017)
		- [What's New in Visual Studio 2019](/visualstudio/ide/whats-new-visual-studio-2019)