Acrolinx edits

Author: Matthew Sebolt (Aquent LLC)

docs/atl/implementing-a-dialog-box.md

@@ -17,7 +17,7 @@ There are two ways to add a dialog box to your ATL project: use the ATL Dialog W
 
 ## Adding a Dialog Box with the ATL Dialog Wizard
 
-In the [Add Class dialog box](../ide/add-class-dialog-box.md), select the ATL Dialog object to add a dialog box to your ATL project. Fill in the ATL Dialog Wizard as appropriate and click **Finish**. The wizard adds a class derived from [CAxDialogImpl](../atl/reference/caxdialogimpl-class.md) to your project. Open the Resource View from the **View** menu, locate your dialog, and double-click it to open it in the resource editor.
+In the [Add Class dialog box](../ide/add-class-dialog-box.md), select the ATL Dialog object to add a dialog box to your ATL project. Fill in the ATL Dialog Wizard as appropriate and click **Finish**. The wizard adds a class derived from [CAxDialogImpl](../atl/reference/caxdialogimpl-class.md) to your project. Open Resource View from the **View** menu, locate your dialog, and double-click it to open it in the resource editor.
 
 > [!NOTE]
 >  If your dialog box is derived from `CAxDialogImpl`, it can host both ActiveX and Windows controls. If you don't want the overhead of ActiveX control support in your dialog box class, use [CSimpleDialog](../atl/reference/csimpledialog-class.md) or [CDialogImpl](../atl/reference/cdialogimpl-class.md) instead.

docs/dotnet/hosting-a-windows-form-user-control-as-an-mfc-dialog-box.md

@@ -43,7 +43,7 @@ For a sample application that shows Windows Forms used with MFC, see [MFC and Wi
 
 1. Add a new class that subclasses `CDialog`.
 
-     Right click on project name and add an MFC class (called CHostForWinForm) that subclasses `CDialog`. Since you do not need the dialog box resource, you can delete the resource ID (select the Resource View, expand the Dialog folder and delete IDD_HOSTFORWINFORM resource.  Then, remove any references to the ID in code.).
+     Right click on project name and add an MFC class (called CHostForWinForm) that subclasses `CDialog`. Since you do not need the dialog box resource, you can delete the resource ID (select Resource View, expand the Dialog folder and delete IDD_HOSTFORWINFORM resource.  Then, remove any references to the ID in code.).
 
 1. Replace `CDialog` in CHostForWinForm.h and CHostForWinForm.cpp files with `CWinFormsDialog<WindowsControlLibrary1::UserControl1>`.
 

docs/dotnet/how-to-migrate-to-clr.md

@@ -102,7 +102,7 @@ Precompiled headers are supported under **/clr**. However, if you only compile s
 
 The easiest way to compile a project where some modules are compiled **/clr** is to disable precompiled headers entirely. (In the project Property Pages dialog, open the C/C++ node, and select Precompiled Headers. Then change the Create/Use Precompiled Headers property to "Not Using Precompiled Headers".)
 
-However, particularly for large projects, precompiled headers provide much better compilation speed, so disabling this feature is not desirable. In this case it's best to configure the **/clr** and non **/clr** files to use separate precompiled headers. This can be done in one step by multi-selecting the modules to be compiled **/clr** using the Solution Explorer, right-clicking on the group, and selecting Properties. Then change both the Create/Use PCH Through File and Precompiled Header File properties to use a different header file name and PCH file respectively.
+However, particularly for large projects, precompiled headers provide much better compilation speed, so disabling this feature is not desirable. In this case it's best to configure the **/clr** and non **/clr** files to use separate precompiled headers. This can be done in one step by multi-selecting the modules to be compiled **/clr** using Solution Explorer, right-clicking on the group, and selecting Properties. Then change both the Create/Use PCH Through File and Precompiled Header File properties to use a different header file name and PCH file respectively.
 
 ## Fixing Errors
 

docs/ide/walkthrough-building-a-project-cpp.md

@@ -19,29 +19,29 @@ In this walkthrough, you deliberately introduce a Visual C++ syntax error in you
 
 - This walkthrough assumes that you understand the fundamentals of the C++ language.
 
-- It also assumes that you have completed the earlier related walkthroughs that are listed in [Using the Visual Studio IDE for C++ Desktop Development](../ide/using-the-visual-studio-ide-for-cpp-desktop-development.md).
+- It also assumes that you've completed the earlier related walkthroughs that are listed in [Using the Visual Studio IDE for C++ Desktop Development](../ide/using-the-visual-studio-ide-for-cpp-desktop-development.md).
 
 ### To fix compilation errors
 
-1. In Game.cpp, delete the semicolon in the last line so that it resembles this:
+1. In Game.cpp, delete the semicolon in the last line so that it resembles the statement:
 
-     `return 0`
+    `return 0`
 
 1. On the menu bar, choose **Build** > **Build Solution**.
 
-1. A message in the **Error List** window indicates that there was an error in the building of the project. The description looks something like this:
+1. A message in the **Error List** window indicates that there was an error in the building of the project. The description looks something like the error message:
 
-     `error C2143: syntax error: missing ';' before '}'`
+    `error C2143: syntax error: missing ';' before '}'`
 
-   To view help information about this error, highlight it in the **Error List** window and then choose the **F1** key.
+  To view help information about this error, highlight it in the **Error List** window and then choose the **F1** key.
 
 1. Add the semicolon back to the end of the line that has the syntax error:
 
      `return 0;`
 
 1. On the menu bar, choose **Build** > **Build Solution**.
 
-   A message in the **Output** window indicates that the project compiled successfully.
+  A message in the **Output** window indicates that the project compiled successfully.
 
     ```Output
     1>------ Build started: Project: Game, Configuration: Debug Win32 ------

docs/ide/walkthrough-compiling-a-cpp-program-that-targets-the-clr-in-visual-studio.md

@@ -15,7 +15,7 @@ ms.workload: ["cplusplus"]
 
 You can create Visual C++ programs that use .NET classes and compile them by using the Visual Studio Development Environment.  
 
-For this procedure you can type your own Visual C++ program or use one of the sample programs. The sample program that we use in this procedure creates a text file named textfile.txt and saves it to the project directory.  
+For this procedure, you can type your own Visual C++ program or use one of the sample programs. The sample program that we use in this procedure creates a text file named textfile.txt, and saves it to the project directory.  
 
 ## Prerequisites  
 
@@ -32,41 +32,41 @@ These topics assume that you understand the fundamentals of the C++ language.
   
 1. Type a project name.  
 
-     By default, the solution that contains the project has the same name as the new project, but you can enter a different name. You can enter a different location for the project if you want.  
+    By default, the solution that contains the project has the same name as the new project, but you can enter a different name. You can enter a different location for the project if you want.  
 
-     Click **OK** to create the new project.  
+    Click **OK** to create the new project.  
 
-1. If **Solution Explorer** is not visible, click **Solution Explorer** on the **View** menu.  
+1. If **Solution Explorer** isn't visible, click **Solution Explorer** on the **View** menu.  
 
 1. Add a new source file to the project:  
 
-    - Right-click the **Source Files** folder in **Solution Explorer**, point to **Add** and click **New Item**.  
+    - Right-click the **Source Files** folder in **Solution Explorer**, point to **Add**, and click **New Item**.  
 
     - Click **C++ File (.cpp)** and type a file name and then click **Add**.  
 
-     The **.cpp** file appears in the **Source Files** folder in **Solution Explorer** and a tabbed window appears where you type the code you want in that file.  
+    The **.cpp** file appears in the **Source Files** folder in **Solution Explorer** and a tabbed window appears where you type the code you want in that file.  
 
 1. Click in the newly created tab in Visual Studio and type a valid Visual C++ program, or copy and paste one of the sample programs.  
 
-     For example, you can use the [How to: Write a Text File (C++/CLI)](../dotnet/how-to-write-a-text-file-cpp-cli.md) sample program (in the **File Handling and I/O** node of the Programming Guide).  
+    For example, you can use the [How to: Write a Text File (C++/CLI)](../dotnet/how-to-write-a-text-file-cpp-cli.md) sample program (in the **File Handling and I/O** node of the Programming Guide).  
 
-     If you use the sample program, notice that you use the `gcnew` keyword instead of `new` when creating a .NET object, and that `gcnew` returns a handle (`^`) rather than a pointer (`*`):  
+    If you use the sample program, notice that you use the `gcnew` keyword instead of `new` when creating a .NET object, and that `gcnew` returns a handle (`^`) rather than a pointer (`*`):  
 
-     `StreamWriter^ sw = gcnew StreamWriter(fileName);`  
+    `StreamWriter^ sw = gcnew StreamWriter(fileName);`  
 
-     For more information on the new Visual C++ syntax, see [Component Extensions for Runtime Platforms](../windows/component-extensions-for-runtime-platforms.md).  
+    For more information on the new Visual C++ syntax, see [Component Extensions for Runtime Platforms](../windows/component-extensions-for-runtime-platforms.md).  
 
 1. On the **Build** menu, click **Build Solution**.  
 
-     The **Output** window displays information about the compilation progress, such as the location of the build log and a message that indicates the build status.  
+    The **Output** window displays information about the compilation progress, such as the location of the build log and a message that indicates the build status.  
 
-     If you make changes and run the program without doing a build, a dialog box might indicate that the project is out of date. Select the checkbox on this dialog before you click **OK** if you want Visual Studio to always use the current versions of files instead of prompting you each time it builds the application.  
+    If you make changes and run the program without doing a build, a dialog box might indicate that the project is out of date. Select the checkbox on this dialog before you click **OK** if you want Visual Studio to always use the current versions of files instead of prompting you each time it builds the application.  
 
 1. On the **Debug** menu, click **Start without Debugging**.  
 
 1. If you used the sample program, when you run the program a command window is displayed that indicates the text file has been created.  
 
-     The **textfile.txt** text file is now located in your project directory. You can open this file by using Notepad.  
+    The **textfile.txt** text file is now located in your project directory. You can open this file by using Notepad.  
 
     > [!NOTE]
     > Choosing the empty CLR project template automatically set the `/clr` compiler option. To verify this, right-click the project in **Solution Explorer** and clicking **Properties**, and then check the **Common Language Runtime support** option in the **General** node of **Configuration Properties**.  

docs/ide/walkthrough-debugging-a-project-cpp.md

@@ -13,13 +13,13 @@ ms.workload: ["cplusplus"]
 ---
 # Walkthrough: Debugging a Project (C++)
 
-In this walkthrough, you modify the program to fix the problem that you discovered when you tested the project.
+In this walkthrough, you modify the program to fix the problem that you found when you tested the project.
 
 ## Prerequisites
 
 - This walkthrough assumes that you understand the fundamentals of the C++ language.
 
-- It also assumes that you have completed the earlier related walkthroughs that are listed in [Using the Visual Studio IDE for C++ Desktop Development](../ide/using-the-visual-studio-ide-for-cpp-desktop-development.md).
+- It also assumes that you've completed the earlier related walkthroughs that are listed in [Using the Visual Studio IDE for C++ Desktop Development](../ide/using-the-visual-studio-ide-for-cpp-desktop-development.md).
 
 ### To fix a program that has a bug
 
@@ -31,11 +31,11 @@ In this walkthrough, you modify the program to fix the problem that you discover
 
    Open the shortcut menu for the **~Cardgame(void)** destructor and then choose **Go To Definition**.
 
-1. To decrease the `totalParticipants` when a Cardgame terminates, add the following code between the opening and closing braces of the `Cardgame::~Cardgame` destructor.
+1. To decrease the `totalParticipants` when a Cardgame ends, add the following code between the opening and closing braces of the `Cardgame::~Cardgame` destructor.
 
      [!code-cpp[NVC_Walkthrough_Debugging_A_Project#110](../ide/codesnippet/CPP/walkthrough-debugging-a-project-cpp_1.cpp)]
 
-1. The Cardgame.cpp file should resemble this after you change it:
+1. The Cardgame.cpp file should resemble the code below after you change it:
 
      [!code-cpp[NVC_Walkthrough_Debugging_A_Project#111](../ide/codesnippet/CPP/walkthrough-debugging-a-project-cpp_2.cpp)]
 

docs/ide/walkthrough-deploying-a-visual-cpp-application-by-using-a-setup-project.md

@@ -21,7 +21,7 @@ You need the following components to complete this walkthrough:
 
 - A computer with Visual Studio installed.  
 
-- An additional computer that does not have the Visual C++ libraries.  
+- An additional computer that doesn't have the Visual C++ libraries.  
 
 ### To deploy an application by using a setup project  
 
@@ -36,9 +36,9 @@ You need the following components to complete this walkthrough:
   
 1. Change the active solution configuration to **Release**. From the **Build** menu, select **Configuration Manger**. From the **Configuration Manager** dialog box, select **Release** from the **Active solution configuration** drop-down box. Click **Close**.
 
-1. Press **Ctrl**+**Shift**+**B** to build the application. Or, on the **Build** menu, click **Build Solution**. This enables the setup project to use the output of this MFC application project.   
+1. Press **Ctrl**+**Shift**+**B** to build the application. Or, on the **Build** menu, click **Build Solution**. Building the application enables the setup project to use the output of this MFC application project.   
 
-1. If you haven’t already done so, download the Microsoft Visual Studio Installer Projects extension. The extension is free for Visual Studio developers and adds the functionality of the setup and deployment project templates to Visual Studio. When you are connected to the Internet, in Visual Studio, choose **Tools** > **Extensions and Updates**. Under the **Extensions and Updates** dialog, select the **Online** tab and type *Microsoft Visual Studio Installer Projects* in the search box. Hit **Enter**, select **Microsoft Visual Studio \<version> Installer Projects**, and click **Download**. Choose to run and install the extension, then restart Visual Studio. 
+1. If you haven’t already done so, download the Microsoft Visual Studio Installer Projects extension. The extension is free for Visual Studio developers and adds the functionality of the setup and deployment project templates to Visual Studio. When you're connected to the Internet, in Visual Studio, choose **Tools** > **Extensions and Updates**. Under the **Extensions and Updates** dialog, select the **Online** tab and type *Microsoft Visual Studio Installer Projects* in the search box. Hit **Enter**, select **Microsoft Visual Studio \<version> Installer Projects**, and click **Download**. Choose to run and install the extension, then restart Visual Studio. 
 
 1. On the menu bar, choose **File** > **Recent Projects and Solutions**, and then choose to reopen your project.   
 
@@ -48,15 +48,15 @@ You need the following components to complete this walkthrough:
 
 1. Right-click the **Application Folder** node and select **Add** > **Project Output** to open the **Add Project Output Group** dialog box. In the dialog box, select **Primary Output** and click **OK**. A new item named **Primary Output from ProjectName (Active)** appears.
 
-1. Right-click the **Application Folder** node and select **Add** > **Assembly** to open the **Select Component** dialog box. Select and add any required DLLs needed by the program, as described by the topic [Determining Which DLLs to Redistribute](determining-which-dlls-to-redistribute.md). 
+1. Right-click the **Application Folder** node and select **Add** > **Assembly** to open the **Select Component** dialog box. Select and add any required DLLs needed by the program, as described by the article [Determining Which DLLs to Redistribute](determining-which-dlls-to-redistribute.md). 
 
 1. Select the item **Primary Output from ProjectName (Active)**, right-click and choose **Create Shortcut to Primary Output from ProjectName (Active)**. A new item named **Shortcut to Primary Output from ProjectName (Active)** appears. You may rename the shortcut item, then drag and drop the item into the **User's Programs Menu** node on the left side of the window.
 
 1. On the menu bar, choose **Build** > **Configuration Manager**. In the **Project** table, under the **Build** column, check the box for the deployment project. Click **Close**.
 
 1. On the menu bar, choose **Build** > **Build Solution** to build the MFC project and the deployment project.  
 
-1. In the solution folder, locate the setup.exe program that was built from the deployment project. You can copy this file (and the .msi file) to install the application and its required library files on another computer. Run the setup program on a second computer that does not have the Visual C++ libraries.
+1. In the solution folder, locate the setup.exe program that was built from the deployment project. You can copy this file (and the .msi file) to install the application and its required library files on another computer. Run the setup program on a second computer that doesn't have the Visual C++ libraries.
 
 ## See Also  
 

docs/ide/walkthrough-deploying-a-visual-cpp-application-to-an-application-local-folder.md

@@ -19,15 +19,15 @@ Describes how to deploy a Visual C++ application by copying files to its folder.
 
 - A computer that has Visual Studio installed.  
 
-- Another computer that does not have the Visual C++ libraries.  
+- Another computer that doesn't have the Visual C++ libraries.  
 
 ### To deploy an application to an application-local folder  
 
 1. Create and build an MFC application by following the steps in [Walkthrough: Deploying a Visual C++ Application By Using a Setup Project](walkthrough-deploying-a-visual-cpp-application-by-using-a-setup-project.md).  
 
 1. Copy the appropriate MFC and C Run-Time (CRT) library files from the Visual Studio installation directory in the \\VC\\redist\\*version* folder, and then paste them in the \Release\ folder of your MFC project. For more information about other files that you might have to copy, see [Determining Which DLLs to Redistribute](determining-which-dlls-to-redistribute.md).  
 
-1. Run the MFC application on a second computer that does not have the Visual C++ libraries.  
+1. Run the MFC application on a second computer that doesn't have the Visual C++ libraries.  
 
    1. Copy the contents of the \Release\ folder and paste them in the application folder on the second computer.