Addressed PR review feedback and added MDD/Embedded to deprecation list

Author: AugP

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

@@ -25,7 +25,7 @@ There are three important restrictions on binary compatibility between the v140,
 
 We've kept the Microsoft Visual C++ Redistributable major version number the same for Visual Studio 2015, 2017, 2019, 2022, and 2026. That means only one instance of the Redistributable can be installed at a time. A newer version overwrites any older version that's already installed. For example, one app may install the Redistributable from Visual Studio 2015. Then, another app installs the Redistributable from Visual Studio 2026. The 2026 version overwrites the older version, but because they're binary-compatible, the earlier app still works fine. We make sure the latest version of the Redistributable has all the newest features, security updates, and bug fixes. That's why we always recommend you upgrade to the latest available version.
 
-Similarly, you can't install an older Redistributable when a newer version is already installed. The installer reports an error if you try. You'll see an error like this if you install the 2019 or 2022 Redistributable on a machine that already has the 2026 version:
+Similarly, you can't install an older Redistributable when a newer version is already installed. The installer reports an error if you try. For example, you'll see an error like this if you install the 2022 Redistributable on a machine that already has the 2026 version:
 
 ```Output
 0x80070666 - Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.

docs/porting/features-deprecated-in-visual-studio.md

@@ -1,12 +1,12 @@
 ---
-description: "Learn more about: C++ features deprecated or removed in Visual Studio"
-title: "C++ features deprecated or removed in Visual Studio"
+description: "Learn more about: C++ features deprecated or removed from Visual Studio"
+title: "C++ features deprecated or removed from Visual Studio"
 ms.date: 10/29/2025
-helpviewer_keywords: ["Features deprecated or removed in Visual Studio"]
+helpviewer_keywords: ["Features deprecated or removed from Visual Studio"]
 ---
-# C++ features deprecated or removed in Visual Studio
+# C++ features deprecated or removed from Visual Studio
 
-This article is a non-exhaustive list of C++ features deprecated in Visual Studio 2019 and 2022. For information on breaking changes and conformance improvements for C++ in the latest version of Visual Studio, see [C++ conformance improvements in Visual Studio](../overview/cpp-conformance-improvements.md).
+This article is a non-exhaustive list of C++ features deprecated or removed from Visual Studio 2019 and later. For information on breaking changes and conformance improvements for C++ in the latest version of Visual Studio, see [C++ conformance improvements in Visual Studio](../overview/cpp-conformance-improvements.md).
 
 ## Visual Studio 2019
 
@@ -26,9 +26,9 @@ Visual Studio 2022 and later versions don't support upgrades from Visual C++ 6 W
 
 Visual Studio 2026 and later versions don't support C++AMP, the ARM32 toolchain, and /DEBUG:FASTLINK. If you're utilizing `/DEBUG:FASTLINK`, it's recommended to switch to [`/DEBUG:FULL`](https://learn.microsoft.com/cpp/build/reference/debug-generate-debug-info) for improved debugging support. Developers needing to target ARM32 can continue using the Visual Studio 2022 v143 build tools as detailed in this [Microsoft blog post](https://devblogs.microsoft.com/cppblog/side-by-side-minor-version-msvc-toolsets-in-visual-studio-2019/).
 
-### Deprecation of /await
+### Deprecation of `/await`
 
-Visual Studio 2026 deprecated the `/await` switch, which will be removed in a future release. Developers are encouraged to use Standard C++ coroutines, available by default in C++20 or later. For projects in earlier language modes, consider using `/await:strict` to maintain compatibility until the switch is removed.
+The MSVC compiler switch `/await` is being deprecated and will be removed in a future release. This switch enabled an early draft implementation of C++ coroutines using the `<experimental/coroutine>` header. Developers should transition to standard C++ coroutines by using the `<coroutine>` header available in C++20 and later. For C++14/17 projects, use `/await:strict` (which isn't being deprecated) to access the standard `<coroutine>` header without enabling other C++20 features.
 
 ### Support for Windows 7, 8, and 8.1 for Microsoft C++ Build Tools
 
@@ -40,4 +40,12 @@ In Visual Studio 2026, the Microsoft C++ (MSVC) Build Tools have updated their m
 
 To build applications using the latest C++ tools, your target platform must be **Windows 10** or **Windows Server 2016** (or later).
 
-These changes allow for better performance, enhanced security, and alignment with the most recent Windows platform capabilities.
+These changes allow for better performance, enhanced security, and alignment with the most recent Windows platform capabilities.
+
+### Support for Mobile development with C++ workload
+
+The Mobile development with C++ workload for iOS and Android targeting in the Visual Studio installer is no longer being supported and will be removed in a future Visual Studio update. This includes new projects, building, and debugging.
+
+### Support for Embedded and IoT tools
+
+The Embedded and IoT tools component in the Visual Studio installer is no longer being supported and will be removed in a future Visual Studio update. This includes the RTOS Viewer, Serial Monitor, Peripheral Viewer, and ST Project Import.

docs/porting/ide-tools-for-upgrading-code.md

@@ -26,7 +26,7 @@ If your legacy projects are based on an older version of Visual Studio, you can
 
 To retarget projects to the Visual Studio 2026 format, you can use the setup assistant which appears the first time you open a solution with older projects. You can also access it by right-clicking the solution in Solution Explorer and selecting *Retarget solution*.
 
-![Screenshot of the Visual Studio 2026 setup assistant.](media/vs-2026-setup-assistant.png "Upgrade projects")
+![Screenshot of the Visual Studio 2026 setup assistant showing a list of projects selected for retargeting to the latest MSVC Build Tools and v145 Platform Toolset.](media/vs-2026-setup-assistant.png "Upgrade projects")
 
 The setup assistant then gives you the choice to either stay on the older version and install any missing build tools or Windows SDKs to be able to build, or retarget the projects to upgrade them. You can make retargeting selections for each project in the solution or click *Retarget all*, then click *Apply* to perform the upgrade.
 

docs/porting/upgrade-your-code-to-the-universal-crt.md

@@ -27,7 +27,9 @@ The retail and debug UCRT DLLs are found in separate locations. The retail DLLs
 
 The C and C++ compiler-specific runtime support library, `vcruntime`, contains the code required to support program startup and features such as exception handling and intrinsics. The library and its header files are still found in the version-specific Microsoft Visual Studio folder in your *Program Files* or *Program Files (x86)* directory.
 
-In Visual Studio 2017 and later, the header files are found under `Microsoft Visual Studio\[version]\[edition]\VC\Tools\MSVC\[lib-version]\include`. Here, `[version]` is the year (Visual Studio 2017 - 2022) or major version number (Visual Studio 2026 or later), `[edition]` is the edition or nickname for Visual Studio, and `[lib-version]` is the build version of the libraries.
+In Visual Studio 2017-2022, the header files are found under `Microsoft Visual Studio\[year]\[edition]\VC\Tools\MSVC\[lib-version]\include`. Here, `[year]` is the version of Visual Studio, `[edition]` is the edition or nickname for Visual Studio, and `[lib-version]` is the build version of the libraries.
+
+In Visual Studio 2026, the header files are found under `Microsoft Visual Studio\[version]\[channel]\VC\Tools\MSVC\[lib-version]\include`. Here, `[version]` is the major version number, `[channel]` is Insiders or Stable (depending on your Visual Studio build), and `[lib-version]` is the build version of the libraries.
 
 The link libraries are found under `Microsoft Visual Studio\[version]\[edition]\VC\Tools\MSVC\[lib-version]\lib\[architecture]`, where `[version]` is the year (Visual Studio 2017 - 2022) or major version number (Visual Studio 2026 or later), `[edition]` is the edition or nickname for Visual Studio, `[lib-version]` is the build version of the libraries, and `[architecture]` is the target processor architecture. Link libraries for OneCore and Store are also found in the libraries folder.