Tweak grammar, trademarks

Also update date.

Author: Colin Robertson

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

@@ -1,7 +1,7 @@
 ---
 description: "Learn more about: Determining Which DLLs to Redistribute"
 title: "Determining Which DLLs to Redistribute"
-ms.date: "07/15/2019"
+ms.date: 03/10/2021
 helpviewer_keywords: ["redistributing DLLs", "DLLs [C++], redistributing", "dependencies [C++], application deployment and", "application deployment [C++], DLL redistribution", "deploying applications [C++], DLL redistribution"]
 ms.assetid: f7a2cb42-fb48-42ab-abd2-b35e2fd5601a
 ---
@@ -11,7 +11,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 both x86 and x64 computers, vcredist\_x64.exe installs the 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. For links to the latest supported redistributable packages for both current and older toolsets, see [The latest supported Visual C++ downloads](https://support.microsoft.com/help/2977003/the-latest-supported-visual-c-downloads). Specific earlier versions of the redistributable packages may be found by searching the [Microsoft Download Center](https://go.microsoft.com/fwlink/p/?LinkId=158431) for "Visual C++ Redistributable Packages".
 
-We only support using a redistributable package that is the same as or newer than your toolset version. The major version number of the redistributable package you deploy must match the version of the Visual Studio toolset used to create your application, and the minor version must be the same or higher. Visual Studio 2019, 2017 and 2015 all have compatible toolset version numbers, which means that newer Visual Studio redistributable files may be used by apps built by a toolset from an older VS version. Example: Visual Studio 2019 redistributable files may be used by apps built by using the VS 2017 or 2015 toolset. While they may be compatible, we do not support using older redistributable files in apps built by using a newer toolset. Example: using the 2017 redistributable files in apps built by using the 2019 toolset is not supported.
+We only support using a redistributable package that's the same as or newer than your toolset version. The major version number of the redistributable package you deploy must match the version of the Visual Studio toolset used to create your application, and the minor version must be the same or higher. Visual Studio 2019, 2017 and 2015 all have compatible toolset version numbers, which means that newer Visual Studio redistributable files may be used by apps built by a toolset from an older version. For example, Visual Studio 2019 redistributable files may be used by apps built by using the Visual Studio 2017 or 2015 toolset. While they may be compatible, we don't support using older redistributable files in apps built by using a newer toolset. For example, using the 2017 redistributable files in apps built by using the 2019 toolset isn't supported.
 
 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](redistributing-components-by-using-merge-modules.md).