Merge branch 'mb-stdafx' of github.com:mikeblome/cpp-docs-pr into mb-stdafx

merge from remote

Author: mikeblome

docs/atl/creating-the-project-atl-tutorial-part-1.md

@@ -54,7 +54,7 @@ Visual Studio will create the project by generating several files. You can view
 |Polygon.rc|The resource file, which initially contains the version information and a string containing the project name.|
 |Resource.h|The header file for the resource file.|
 |Polygonps.def|This module definition file provides the linker with information about the exports required by the proxy and stub code that support calls across apartments.|
-|stdafx.cpp|The file that will `#include` *stfafx.h**.|
+|stdafx.cpp|The file that will `#include` *stdafx.h*.|
 |stdafx.h|The file that will `#include` and precompile the ATL header files.|
 
 ::: moniker-end

docs/build/walkthrough-creating-and-using-a-dynamic-link-library-cpp.md

@@ -202,7 +202,7 @@ When the **MATHLIBRARY_EXPORTS** macro is defined, the **MATHLIBRARY_API
 
    ```cpp
    // MathLibrary.cpp : Defines the exported functions for the DLL.
-   #include "pch.h" // use *stdafx.h* in Visual Studio 2017 and earlier
+   #include "pch.h" // use stdafx.h in Visual Studio 2017 and earlier
    #include <utility>
    #include <limits.h>
    #include "MathLibrary.h"

docs/data/oledb/implementing-a-simple-consumer.md

@@ -35,7 +35,7 @@ The following topics show how to edit the files created by the **MFC Application
     ```cpp
     // MyCons.cpp : Defines the entry point for the console application.
     //
-    #include "pch.h" // *stdafx.h* in Visual Studio 2017 and earlier
+    #include "pch.h" // "stdafx.h" in Visual Studio 2017 and earlier
     #include "Products.h"
     ...
     int main(int argc, char* argv[])

docs/get-started/tutorial-console-cpp.md

@@ -480,7 +480,7 @@ Now let's turn the code in this template into a calculator app.
    > Understanding the code:
    >
    > - The `#include` statements allow you to reference code located in other files. Sometimes, you may see a filename surrounded by angle brackets (**\<\>**); other times, it's surrounded by quotes (**" "**). In general, angle brackets are used when referencing the C++ Standard Library, while quotes are used for other files.
-   > - The `#include "pch.h"` (or Visual Studio 2017 and earlier, `#include "stdafx.h"`) line references something known as a precompiled header. These are often used by professional programmers to improve compilation times, but they are beyond the scope of this tutorial.
+   > - The `#include "pch.h"` (or in Visual Studio 2017 and earlier, `#include "stdafx.h"`) line references something known as a precompiled header. These are often used by professional programmers to improve compilation times, but they are beyond the scope of this tutorial.
    > - The `using namespace std;` line tells the compiler to expect stuff from the C++ Standard Library to be used in this file. Without this line, each keyword from the library would have to be preceded with a `std::`, to denote its scope. For instance, without that line, each reference to `cout` would have to be written as `std::cout`. The `using` statement is added to make the code look more clean.
    > - The `cout` keyword is used to print to standard output in C++. The **\<\<** operator tells the compiler to send whatever is to the right of it to the standard output.
    > - The **endl** keyword is like the Enter key; it ends the line and moves the cursor to the next line. It is a better practice to put a `\n` inside the string (contained by "") to do the same thing, as `endl` always flushes the buffer and can hurt the performance of the program, but since this is a very small app, `endl` is used instead for better readability.
@@ -748,4 +748,4 @@ Congratulations! You've completed the code for the calculator app, and built and
 
 [Learn more about Visual Studio for C++](https://blogs.msdn.microsoft.com/vcblog/2017/04/21/getting-started-with-visual-studio-for-c-and-cpp-development/)
 
-::: moniker-end
+::: moniker-end

docs/mfc/tn065-dual-interface-support-for-ole-automation-servers.md

@@ -256,7 +256,7 @@ To modify a project's build settings so that a header file containing **UUID** d
 
 To add the **UUID** definitions from the MkTypLib-generated header file to your project:
 
-1. Include the MkTypLib-generated header file in your standard includes header file,*stdafx.h*.
+1. Include the MkTypLib-generated header file in your standard includes header file, *stdafx.h*.
 
 2. Create a new file, INITIIDS.CPP, and add it to your project. In this file, include your MkTypLib-generated header file after including OLE2.H and INITGUID.H:
 

docs/mfc/using-cmonthcalctrl.md

@@ -10,7 +10,7 @@ ms.assetid: 2be0e8c2-ed03-4853-aea1-4461eba18611
 The month calendar control ([CMonthCalCtrl](../mfc/reference/cmonthcalctrl-class.md)) implements a calendar-like user interface. This provides the user with a very intuitive and recognizable method of entering or selecting a date. The control also provides the application with the means to obtain and set the date information in the control using existing data types. By default, the month calendar control displays the current day and month. However, the user is able to scroll to the previous and next months and select a specific month and/or year.
 
 > [!NOTE]
->  To use the `CMonthCalCtrl` class in your project, you must include AFXDTCTL.H, usually in*stdafx.h*.
+>  To use the `CMonthCalCtrl` class in your project, you must include AFXDTCTL.H, usually in *stdafx.h*.
 
 ## What do you want to know more about
 

docs/parallel/concrt/creating-asynchronous-operations-in-cpp-for-windows-store-apps.md

@@ -153,7 +153,7 @@ Update the `Grid` element in MainPage.xaml to include a `ProgressRing` element a
 
 [!code-xml[concrt-windowsstore-commonwords#1](../../parallel/concrt/codesnippet/xaml/creating-asynchronous-operations-in-cpp-for-windows-store-apps_6.xaml)]
 
-Add the following `#include` statements to*pch.h*.
+Add the following `#include` statements to *pch.h*.
 
 [!code-cpp[concrt-windowsstore-commonwords#2](../../parallel/concrt/codesnippet/cpp/creating-asynchronous-operations-in-cpp-for-windows-store-apps_7.h)]
 

docs/porting/how-to-use-existing-cpp-code-in-a-universal-windows-platform-app.md

@@ -145,7 +145,7 @@ The following procedure applies to the case where you have a native DLL that exp
 
    **Solution Explorer** now identifies the project as a Universal Windows project.
 
-5. Make sure your precompiled header file name is correct. In the **Precompiled Headers** section, change **Precompiled Header File** from *pch.h* to*stdafx.h*. If you don't do this, you see the following error.
+5. Make sure your precompiled header file name is correct. In the **Precompiled Headers** section, change **Precompiled Header File** from *pch.h* to *stdafx.h*. If you don't do this, you see the following error.
 
    > error C2857: '#include' statement specified with the /Ycpch.h command-line option was not found in the source file
 
@@ -213,7 +213,7 @@ If you want to consume native APIs in a static library from a UWP app, and you h
 
 5. Select all the files to add from your original project, and choose **OK**. Repeat if necessary for subfolders.
 
-6. You might now have some duplicated code. If you have more than one precompiled header (say *stdafx.h* and*pch.h*), choose one to keep. Copy any required code, such as include statements, into the one you're keeping. Then, delete the other, and in the project properties, under **Precompiled Headers**, make sure that the name of the header file is correct.
+6. You might now have some duplicated code. If you have more than one precompiled header (say *stdafx.h* and *pch.h*), choose one to keep. Copy any required code, such as include statements, into the one you're keeping. Then, delete the other, and in the project properties, under **Precompiled Headers**, make sure that the name of the header file is correct.
 
    If you changed the file to use as the precompiled header, make sure that the precompiled header options are correct for each file. Select each .cpp file in turn, open its properties window, and make sure that all are set to **Use (/Yu)**, except for the desired precompiled header, which should be set to **Create (/Yc)**.