Merge pull request #2532 from mikeblome/mb-offline-review

a few misc updates per offline review. also fixes #1057

Author: GitHubber17

docs/cpp/fundamental-types-cpp.md

@@ -2,7 +2,7 @@
 title: "Fundamental Types  (C++)"
 ms.date: "11/04/2016"
 f1_keywords: ["__int128_cpp", "__wchar_t_cpp", "char_cpp", "double_cpp", "float_cpp", "int_cpp", "long_cpp", "long_double_cpp", "short_cpp", "signed_cpp", "unsigned_cpp", "unsigned_int_cpp", "wchar_t_cpp"]
-helpviewer_keywords: ["specifiers [C++], type", "float keyword [C++]", "char keyword [C++]", "__wchar_t keyword [C++]", "signed types [C++], summary of data types", "Integer data type [C++], C++ data types", "arithmetic operations [C++], types", "int data type", "unsigned types [C++], summary of data types", "short data type [C++]", "double data type [C++], summary of types", "long long keyword [C++]", "long double keyword [C++]", "unsigned types [C++]", "signed types [C++]", "void keyword [C++]", "storage [C++], basic type", "integral types, C++", "wchar_t keyword [C++]", "floating-point numbers [C++], C++ data types", "long keyword [C++]", "type specifiers [C++]", "integral types", "long keyword [C++], C++ data types", "storing types [C++]", "data types [C++], void"]
+helpviewer_keywords: ["specifiers [C++], type", "float keyword [C++]", "char keyword [C++]", "__wchar_t keyword [C++]", "signed types [C++], summary of data types", "Integer data type [C++], C++ data types", "arithmetic operations [C++], types", "int data type", "unsigned types [C++], summary of data types", "short data type [C++]", "double data type [C++], summary of types", "long long keyword [C++]", "long double keyword [C++]", "unsigned types [C++]", "signed types [C++]", "void keyword [C++]", "storage [C++], basic type", "integral types, C++", "wchar_t keyword [C++]", "floating-point numbers [C++], C++ data types", "long keyword [C++]", "type specifiers [C++]", "integral types", "long keyword [C++]", "storing types [C++]", "data types [C++], void"]
 ms.assetid: 58b0106a-0406-4b74-a430-7cbd315c0f89
 ---
 # Fundamental Types  (C++)
@@ -28,7 +28,7 @@ The following table explains the restrictions on type sizes. These restrictions
 ||**short**|Type **short int** (or simply **short**) is an integral type that is larger than or equal to the size of type **char**, and shorter than or equal to the size of type **int**.<br /><br /> Objects of type **short** can be declared as **signed short** or **unsigned short**. **Signed short** is a synonym for **short**.|
 ||**int**|Type **int** is an integral type that is larger than or equal to the size of type **short int**, and shorter than or equal to the size of type **long**.<br /><br /> Objects of type **int** can be declared as **signed int** or **unsigned int**. **Signed int** is a synonym for **int**.|
 ||**__int8**, **__int16**, **__int32**, **__int64**|Sized integer `__int n`, where `n` is the size, in bits, of the integer variable. **__int8**, **__int16**, **__int32** and **__int64** are Microsoft-specific keywords. Not all types are available on all architectures. (**__int128** is not supported.)|
-||**long**|Type **long** (or **long int**) is an integral type that is larger than or equal to the size of type **int**.<br /><br /> Objects of type **long** can be declared as **signed long** or **unsigned long**. **Signed long** is a synonym for **long**.|
+||**long**|Type **long** (or **long int**) is an integral type that is larger than or equal to the size of type **int**. (On Windows **long** is the same size as **int**.)<br /><br /> Objects of type **long** can be declared as **signed long** or **unsigned long**. **Signed long** is a synonym for **long**.|
 ||**long long**|Larger than an unsigned **long**.<br /><br /> Objects of type **long long** can be declared as **signed long long** or **unsigned long long**. **signed long long** is a synonym for **long long**.|
 ||**wchar_t**, **__wchar_t**|A variable of type **wchar_t** designates a wide-character or multibyte character type. By default, **wchar_t** is a native type, but you can use [/Zc:wchar_t-](../build/reference/zc-wchar-t-wchar-t-is-native-type.md) to make **wchar_t** a typedef for **unsigned short**. The **__wchar_t** type is a Microsoft-specific synonym for the native **wchar_t** type.<br /><br /> Use the L prefix before a character or string literal to designate the wide-character type.|
 |Floating point|**float**|Type **float** is the smallest floating point type.|

docs/mfc/mfc-mbcs-dll-add-on.md

@@ -1,6 +1,6 @@
 ---
 title: "MFC MBCS DLL Add-on"
-ms.date: "05/08/2019"
+ms.date: "12/02/2019"
 helpviewer_keywords: ["MBCS", "MFC"]
 ---
 # MFC MBCS DLL Add-on
@@ -11,7 +11,7 @@ Support for MFC and its multibyte character set (MBCS) libraries requires an add
 
 **Visual Studio 2015**: Both Unicode and MBCS MFC DLLs are included in the Visual C++ setup components, but support for MFC is not installed by default. Visual C++ and MFC are optional install configurations in Visual Studio setup. To make sure that MFC is installed, choose **Custom** in setup, and under **Programming Languages**, make sure that **Visual C++** and **Microsoft Foundation Classes for C++** are selected. If you have already installed Visual Studio, you will be prompted to install Visual C++ and/or MFC when you attempt to create an MFC project.
 
-**Visual Studio 2017 and later**: The Unicode and MBCS MFC DLLs are installed with the **Desktop development with C++** workload when you select **MFC and ATL support** from the **Optional Components** pane. If your installation does not include these components, navigate to the **File | New Projects** dialog and click the **Open Visual Studio Installer** link.
+**Visual Studio 2017 and later**: The Unicode and MBCS MFC DLLs are installed with the **Desktop development with C++** workload when you select **MFC and ATL support** from the **Optional Components** pane in the Visual Studio Installer program. If your installation does not include these components, navigate to the **File | New Projects** dialog and click the **Open Visual Studio Installer** link. For more information, see [Install Visual Studio](/visualstudio/install/install-visual-studio).
 
 ## See also
 

docs/overview/overview-of-cpp-development.md

@@ -1,7 +1,7 @@
 ---
 title: "Overview of C++ development in Visual Studio"
 description: "The Visual Studio IDE supports C++ development on Windows, Linux, Android and iOS with a code editor, debugger, test frameworks, static analyzers, and other programming tools."
-ms.date: "03/08/2019"
+ms.date: "12/02/2019"
 helpviewer_keywords: ["Visual C++, development tools"]
 author: "corob-msft"
 ms.author: "corob"
@@ -66,7 +66,7 @@ If your program has a user interface, you can use a designer to quickly populate
 
 ![Designer and Toolbox](media/vs2017-toolbox-designer.png "Visual Studio 2017 Toolbox and designer")
 
-For more information about designing a user interface for a Universal Windows Platform app, see  [Design and UI](https://developer.microsoft.com/windows/design).
+For more information about designing a user interface for a Universal Windows Platform app, see [Design and UI](https://developer.microsoft.com/windows/design).
 
 For more information about creating a user interface for an MFC application, see [MFC Desktop Applications](../mfc/mfc-desktop-applications.md). For information about Win32 Windows programs, see [Windows Desktop Applications](../windows/windows-desktop-applications-cpp.md).
 
@@ -80,13 +80,11 @@ The code editor is a specialized word processor for C++ source code. It color-co
 
 ## Add and edit resources
 
-The term *resource* includes things such as dialogs, icons, images, localizable strings, splash screens, database connection strings, or any arbitrary data that you want to include in the executable file.
-
-For more information on adding and editing resources in native desktop C++ projects, see [Working with Resource Files](../windows/working-with-resource-files.md).
+A Windows program or DLL usually includes some *resources*, such as dialogs, icons, images, localizable strings, splash screens, database connection strings, or any arbitrary data. Visual Studio includes tools for adding and editing resources. For more information, see [Working with Resource Files](../windows/working-with-resource-files.md).
 
 ## Build (compile and link)
 
-Choose **Build** > **Build Solution** on the menu bar, or enter the Ctrl+Shift+B key combination to compile and link a project. Build errors and warnings are reported in the Error List (Ctrl+\\, E). The **Output** Window (Alt+2) shows information about the build process.
+Choose **Build** > **Build Solution** on the menu bar, or enter the **Ctrl+Shift+B** key combination to compile and link a project. Build errors and warnings are reported in the Error List (**Ctrl+\\, E**). The **Output** Window (**Alt+2**) shows information about the build process.
 
 ![Output Window and Error List](media/vs2017-output-error-list.png "Visual Studio 2017 Output window and Error List")
 
@@ -96,7 +94,7 @@ You can also use the compiler (cl.exe) and many other build-related standalone t
 
 ## Debug
 
-You can start debugging by pressing **F5**. Execution pauses on any breakpoints you have set. You can also step through code one line at a time, view the values of variables or registers, and even in some cases make changes in code and continue debugging without re-compiling. The following illustration shows a debugging session in which execution is stopped on a breakpoint. The values of the data structure members are visible in the **Watch Window**.
+You can start debugging by pressing **F5**. Execution pauses on any breakpoints you have set (by pressing **F9**). You can also step through code one line at a time (**F10**), view the values of variables or registers, and even in some cases make changes in code and continue debugging without re-compiling. The following illustration shows a debugging session in which execution is stopped on a breakpoint. The values of the data structure members are visible in the **Watch Window**.
 
 ![Debugging session](media/vs2017-debug-watch.png "Visual Studio 2017 debugging session")
 
@@ -118,7 +116,7 @@ Visual Studio includes static code analysis tools that can detect potential prob
 
 You can deploy both traditional desktop applications and UWP apps to customers through the Microsoft Store. Deployment of the CRT is handled automatically behind the scenes. For more information, see [Publish Windows apps and games](/windows/uwp/publish/).
 
-You can also deploy a native C++ desktop to another computer  For more information, see [Deploying Desktop Applications](../windows/deploying-native-desktop-applications-visual-cpp.md).
+You can also deploy a native C++ desktop to another computer. For more information, see [Deploying Desktop Applications](../windows/deploying-native-desktop-applications-visual-cpp.md).
 
 For more information about deploying a C++/CLI program, see [Deployment Guide for Developers](/dotnet/framework/deployment/deployment-guide-for-developers),
 

docs/overview/supported-platforms-visual-cpp.md

@@ -1,6 +1,6 @@
 ---
 title: "Supported Platforms (Visual C++)"
-ms.date: "05/14/2019"
+ms.date: "12/02/2019"
 ms.technology: "cpp-tools"
 helpviewer_keywords: ["Visual C++, platforms supported", "platforms [C++]"]
 ms.assetid: 0d893056-4008-411a-b3d1-5f57fd7da95c
@@ -26,7 +26,7 @@ Apps built by using Visual Studio can be targeted to various platforms, as follo
 |iOS \*\*|X|X|X|X|
 |Linux \*\*\*|X|X|X|X|
 
-\* You can use the Windows XP platform toolset included in Visual Studio 2017, Visual Studio 2015, Visual Studio 2013, and Visual Studio 2012 Update 1 or later to build Windows XP and Windows Server 2003 projects. For information on how to use this platform toolset, see [Configuring Programs for Windows XP](../build/configuring-programs-for-windows-xp.md). For additional information on changing the platform toolset, see [How to: Modify the Target Framework and Platform Toolset](../build/how-to-modify-the-target-framework-and-platform-toolset.md).
+\* You can use the Windows XP platform toolset included in Visual Studio 2017, Visual Studio 2015, Visual Studio 2013, and Visual Studio 2012 Update 1 to build Windows XP and Windows Server 2003 projects. For information on how to use this platform toolset, see [Configuring Programs for Windows XP](../build/configuring-programs-for-windows-xp.md). For additional information on changing the platform toolset, see [How to: Modify the Target Framework and Platform Toolset](../build/how-to-modify-the-target-framework-and-platform-toolset.md).
 
 \*\* You can install the **Mobile development with C++** workload in the installer for Visual Studio 2017 and later. In Visual Studio 2015 setup, choose the optional **Visual C++ for Cross Platform Mobile Development** component to target iOS or Android platforms. For instructions, see [Install Visual C++ for Cross-Platform Mobile Development](/visualstudio/cross-platform/install-visual-cpp-for-cross-platform-mobile-development). To build iOS code, you must have a Mac computer and meet other requirements. For a list of prerequisites and installation instructions, see [Install And Configure Tools to Build using iOS](/visualstudio/cross-platform/install-and-configure-tools-to-build-using-ios). You can build x86 or ARM code to match the target hardware. Use x86 configurations to build for the iOS simulator, Microsoft Visual Studio Emulator for Android, and some Android devices. Use ARM configurations to build for iOS devices and most Android devices.