Update clang-support-msbuild.md

Updated for better visibility of LLVMToolsVersion property.

Note the text was also misleading because it kind of implies that LLVMToolsVersion supports side-by-side version of clang/LLVM in the same `LLVMInstallDir`, but that's not how clang/LLVM works. If you want to select a different version, you need to point it to a different path.

Author: walbourn

docs/build/clang-support-msbuild.md

@@ -9,23 +9,23 @@ helpviewer_keywords: ["Clang support for C++ MSBuild projects"]
 
 ::: moniker range="<=msvc-150"
 
-Clang support for both CMake and MSBuild projects is available in Visual Studio 2019.
+Clang/LLVM support for both CMake and MSBuild projects is available in Visual Studio 2019 and Visual Studio 2022.
 
 ::: moniker-end
 
 ::: moniker range=">=msvc-160"
 
-You can use Visual Studio 2019 version 16.2 and later with Clang to edit, build, and debug C++ Visual Studio projects (MSBuild) that target Windows or Linux.
+You can use Visual Studio 2019 version 16.2 and later with Clang/LLVM to edit, build, and debug C++ Visual Studio projects (MSBuild) that target Windows or Linux.
 
 ## Install
 
-For best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have the tools, you can install them by opening the Visual Studio Installer and choosing **C++ Clang tools for Windows** under **Desktop development with C++** optional components. You may prefer to use an existing Clang installation on your machine; if so, choose **C++ Clang-cl for v142 build tools**.
+For best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have the tools, you can install them by opening the Visual Studio Installer and choosing **C++ Clang tools for Windows** under **Desktop development with C++** optional components. You may prefer to use an existing Clang installation on your machine; if so, choose **C++ Clang-cl for v142 build tools** or **C++ Clang-cl for v143 build tools**.
 
 The Microsoft C++ Standard Library requires at least Clang 8.0.0.
 
 ![Screenshot of the Visual Studio installer with the Individual components tab selected and the C plus plus Clang components visible.](media/clang-install-vs2019.png)
 
-Later versions of Visual Studio provide newer versions of the Clang toolset. The bundled version of Clang gets updated automatically to stay current with updates in the Microsoft implementation of the Standard Library. For example, Visual Studio 2019 version 16.9 includes Clang v11.
+Later versions of Visual Studio provide newer versions of the Clang toolset. The bundled version of Clang gets updated automatically to stay current with updates in the Microsoft implementation of the Standard Library. For example, Visual Studio 2019 version 16.11 includes Clang v12.
 
 ## Configure a Windows project to use Clang tools
 
@@ -54,12 +54,13 @@ On Linux, Visual Studio by default uses the first Clang location that it finds i
 
 ## <a name="custom_llvm_location"></a> Set a custom LLVM location
 
-You can set a custom path to LLVM for one or more projects by creating a *Directory.build.props* file. Then, add that file to the root folder of any project. You can add it to the root solution folder to apply it to all projects in the solution. The file should look like this (but use your actual LLVM path):
+You can set a custom path to LLVM for one or more projects by creating a *Directory.build.props* file. Then, add that file to the root folder of any project. You can add it to the root solution folder to apply it to all projects in the solution. The file should look like this (but use your actual LLVM path and version number):
 
 ```xml
 <Project>
   <PropertyGroup>
     <LLVMInstallDir>C:\MyLLVMRootDir</LLVMInstallDir>
+    <LLVMToolsVersion>15.0.0</LLVMToolsVersion>
   </PropertyGroup>
 </Project>
 ```
@@ -82,23 +83,13 @@ Starting in Visual Studio 2019 version 16.9, you can set a custom toolset versio
 
 The **LLVM Toolset Version** property only appears when the LLVM platform toolset is selected.
 
-You can set the toolset version for one or more projects by creating a *Directory.build.props* file. Then, add that file to the root folder of any project. Add it to the root solution folder to apply it to all projects in the solution. The file should look like this (but use your actual LLVM path):
-
-```xml
-<Project>
-  <PropertyGroup>
-    <LLVMToolsVersion>11.0.0</LLVMToolsVersion>
-  </PropertyGroup>
-</Project>
-```
-
-You can also combine this property with a custom LLVM location. For example, your *Directory.build.props* file could look like:
+You can set the toolset version for one or more projects by creating a *Directory.build.props* file. Then, add that file to the root folder of any project. Add it to the root solution folder to apply it to all projects in the solution. The file should look like this (but use your actual LLVM path and version number):
 
 ```xml
 <Project>
   <PropertyGroup>
     <LLVMInstallDir>C:\MyLLVMRootDir</LLVMInstallDir>
-    <LLVMToolsVersion>11.0.0</LLVMToolsVersion>
+    <LLVMToolsVersion>15.0.0</LLVMToolsVersion>
   </PropertyGroup>
 </Project>
 ```