wording

Author: TylerMSFT

docs/porting/binary-compat-2015-2017.md

@@ -14,7 +14,7 @@ We've changed this behavior in Visual Studio 2015 and later versions. The runtim
 
 There are three important restrictions on binary compatibility between the v140, v141, v142, and v143 toolsets and minor numbered version updates:
 
-- Binaries created with different versions of the v140, v141, v142, and v143 toolsets can be combined. The key rule is that the linker should only work with inputs built by toolsets that are the same version, or earlier, as itself. This linking applies to apps, libraries, import libraries, and static libraries. In some cases, an import library for [implicitly linked](../build/linking-an-executable-to-a-dll.md#implicit-linking) DLLs built using a later version of the toolset can be linked using an earlier version of the toolset, especially if the import library strictly uses `extern "C"` for the imports/exports. Here are some examples of what this means:
+- Binaries created with different versions of the v140, v141, v142, and v143 toolsets can be combined. The key rule is that the linker should only work with inputs built by toolsets that are the same version (or earlier) as itself. This linking applies to apps, libraries, import libraries, and static libraries. In some cases, an import library for an [implicitly linked](../build/linking-an-executable-to-a-dll.md#implicit-linking) DLL built using a later version of the toolset can be linked using an earlier version of the toolset--especially if the import library strictly uses `extern "C"` for the imports/exports. Here are some examples of what this means:
     - An app compiled with a 2017 toolset (v141, versions 15.0 to 15.9) can be linked to a static library compiled with Visual Studio 2019 version 16.2 (v142), but the linking must be done using a version 16.2 or later toolset.
     - A version 16.2 library can be linked to a version 16.4 app, but only if you use the 16.4 or later toolset.
     - Apps and libraries built using VS 2015, 2017, or 2019 can be linked together, but the linking must be done using a version of the toolset that is as recent as, or more recent than, the most recent toolset used to build any of the binaries.