slight wording change per product team review

Author: mikeblome

docs/ide/determining-which-dlls-to-redistribute.md

@@ -1,7 +1,7 @@
 ---
 title: "Determining Which DLLs to Redistribute | Microsoft Docs"
 ms.custom: ""
-ms.date: "09/15/2017"
+ms.date: "09/21/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology:  
@@ -42,7 +42,7 @@ When you build an application that uses library DLLs supplied by Visual Studio,
 
 To make it easier to include the redistributable DLLs with your installer, they are available as stand-alone *redistributable packages*. These are architecture-specific executables that use central deployment to install the redistributable files on a user's computer. For example, vcredist\_x86.exe installs the 32-bit libraries for x86 computers, vcredist\_x64.exe installs the 32-bit and 64-bit libraries for x64 computers, and vcredist\_ARM.exe installs the libraries for ARM computers. We recommend central deployment because Microsoft can use the Windows Update service to independently update these libraries. In addition to the copy in your Visual Studio installation, the current redistributable packages are available for download on [VisualStudio.com/Downloads](https://www.visualstudio.com/downloads/) in the Other Tools and Frameworks section.
 
-The major version number of the redistributable package you deploy must match the version of the Visual Studio toolset used to create your application. Visual Studio 2017 and Visual Studio 2015 have compatible toolset version numbers, which means that the Visual Studio 2017 redistributable files may be used by apps built by using the 2015 toolset. While they may be compatible, we do not recommend using the 2015 redistributable files in apps built by using the 2017 toolset. We recommend you use the latest redistributable package update for your toolset version. For links to the latest supported redistributable packages for older toolsets, see [The latest supported Visual C++ downloads](https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads). Specific earlier versions of the redistributable packages may be found by searching the [Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=158431) for "Visual C++ Redistributable Packages".
+The major version number of the redistributable package you deploy must match the version of the Visual Studio toolset used to create your application. Visual Studio 2017 and Visual Studio 2015 have compatible toolset version numbers, which means that the Visual Studio 2017 redistributable files may be used by apps built by using the 2015 toolset. While they may be compatible, we do not support using the 2015 redistributable files in apps built by using the 2017 toolset. We only support using a redistributable package that is the same as or newer than your toolset version. For links to the latest supported redistributable packages for older toolsets, see [The latest supported Visual C++ downloads](https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads). Specific earlier versions of the redistributable packages may be found by searching the [Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkId=158431) for "Visual C++ Redistributable Packages".
 
 Another way to include the redistributable DLLs with your installer is to use *merge modules*. These Microsoft Installer modules are included in and installed by your application installer. Merge modules for the redistributable DLLs are found in your Visual Studio installation directory under \\VC\\Redist\MSVC\\*version*\\MergeModules\\. In earlier versions of Visual Studio, these files are found in your \\Program Files or \\Program Files (x86) directory in a Common Files\\Merge Modules subdirectory. For more information about use of these files, see [Redistributing Components by using Merge Modules](../ide/redistributing-components-by-using-merge-modules.md).