edits

Author: TylerMSFT

docs/mfc/changing-the-styles-of-a-window-created-by-mfc.md

@@ -12,7 +12,7 @@ In its version of the `WinMain` function, MFC registers several standard window
 
 ## <a name="_core_changing_styles_in_a_new_mfc_application"></a> Changing Styles in a New MFC Application
 
-If you're using Microsoft C++ 2.0 or later, you can change the default window styles in the Application Wizard when you create your application. In the Application Wizard's User Interface Features page, you can change styles for your main frame window and MDI child windows. For either window type, you can specify its frame thickness (thick or thin) and any of the following:
+If you're using Visual C++ 2.0 or later, you can change the default window styles in the Application Wizard when you create your application. In the Application Wizard's User Interface Features page, you can change styles for your main frame window and MDI child windows. For either window type, you can specify its frame thickness (thick or thin) and any of the following:
 
 - Whether the window has Minimize or Maximize controls.
 

docs/mfc/containers-for-activex-controls.md

@@ -21,7 +21,7 @@ Applications that support ActiveX control containment include:
 
 - Visual Basic 4.x and greater
 
-- Microsoft C++ 4.x and greater
+- Visual C++ 4.x and greater
 
 - Access 95 and greater
 

docs/mfc/creating-an-active-document-container-application.md

@@ -14,7 +14,7 @@ The simplest and most recommended way to create an active document container app
 
 1. From the **File** menu, click **Project**from the **New** submenu.
 
-1. From the left pane, click **MicrosoftVisual Studio** project type.
+1. From the left pane, click **Visual C++** project type.
 
 1. Select **MFC Application** from the right pane.
 

docs/mfc/docking-and-floating-toolbars.md

@@ -57,7 +57,7 @@ The MFC implementation of dockable toolbars does not provide some of the extende
 
 ## <a name="_core_dynamically_resizing_the_toolbar"></a> Dynamically Resizing the Toolbar
 
-As of Visual Studio version 4.0, you can make it possible for users of your application to resize floating toolbars dynamically. Typically, a toolbar has a long, linear shape, displayed horizontally. But you can change the toolbar's orientation and its shape. For example, when the user docks a toolbar against one of the vertical sides of the frame window, the shape changes to a vertical layout. It's also possible to reshape the toolbar into a rectangle with multiple rows of buttons.
+As of Visual C++ version 4.0, you can make it possible for users of your application to resize floating toolbars dynamically. Typically, a toolbar has a long, linear shape, displayed horizontally. But you can change the toolbar's orientation and its shape. For example, when the user docks a toolbar against one of the vertical sides of the frame window, the shape changes to a vertical layout. It's also possible to reshape the toolbar into a rectangle with multiple rows of buttons.
 
 You can:
 

docs/mfc/form-views-mfc.md

@@ -7,7 +7,7 @@ ms.assetid: efbe73c1-4ca4-4613-aac2-30d916e92c0e
 ---
 # Form Views (MFC)
 
-You can add forms to any Visual Studio application that supports the MFC libraries, including a [forms-based application](reference/creating-a-forms-based-mfc-application.md) (one whose view class is derived from `CFormView`). If you did not initially create your application to support forms, Visual Studio will add this support for you when you insert a new form. In an SDI or MDI application, which implements the default [document/view architecture](document-view-architecture.md), when the user chooses the **New** command (by default, on the **File** menu), Visual Studio prompts the user to choose from the available forms.
+You can add forms to any Visual C++ application that supports the MFC libraries, including a [forms-based application](reference/creating-a-forms-based-mfc-application.md) (one whose view class is derived from `CFormView`). If you did not initially create your application to support forms, Visual Studio will add this support for you when you insert a new form. In an SDI or MDI application, which implements the default [document/view architecture](document-view-architecture.md), when the user chooses the **New** command (by default, on the **File** menu), Visual Studio prompts the user to choose from the available forms.
 
 With an SDI application, when the user chooses the **New** command, the current instance of the form continues to run but a new instance of the application with the selected form is created if one is not found. In an MDI application, the current instance of the form continues to run when the user chooses the **New** command.
 

docs/mfc/framework-mfc.md

@@ -7,7 +7,7 @@ ms.assetid: 3be0fec8-9843-4119-ae42-ece993ef500b
 ---
 # Framework (MFC)
 
-Your work with the Microsoft Foundation Class (MFC) Library framework is based largely on a few major classes and several Visual Studio tools. Some classes encapsulate a large portion of the Win32 application programming interface (API). Other classes encapsulate application concepts such as documents, views, and the application itself. Still others encapsulate OLE features and ODBC and DAO data-access functionality.  (DAO is supported through Office 2013. DAO 3.6 is the final version, and it is considered obsolete.)
+Your work with the Microsoft Foundation Class (MFC) Library framework is based largely on a few major classes and several Visual C++ tools. Some classes encapsulate a large portion of the Win32 application programming interface (API). Other classes encapsulate application concepts such as documents, views, and the application itself. Still others encapsulate OLE features and ODBC and DAO data-access functionality.  (DAO is supported through Office 2013. DAO 3.6 is the final version, and it is considered obsolete.)
 
 For example, Win32's concept of window is encapsulated by MFC class `CWnd`. That is, a C++ class called `CWnd` encapsulates or "wraps" the `HWND` handle that represents a Windows window. Likewise, class `CDialog` encapsulates Win32 dialog boxes.
 

docs/mfc/how-wininet-makes-it-easier-to-create-internet-client-applications.md

@@ -9,7 +9,7 @@ ms.assetid: dc0f9f47-3184-4e7a-8074-2c63e0359885
 
 The Win32 Internet Extensions, or WinInet, provide access to common Internet protocols, including gopher, FTP, and HTTP. Using WinInet, you can write Internet client applications at a higher level of programming, without having to deal with WinSock, TCP/IP, or the details of specific Internet protocols. WinInet provides a consistent set of functions for all three protocols, with a familiar Win32 API interface. This consistency minimizes code changes you need to make if the underlying protocol changes (for example, from FTP to HTTP).
 
-Visual Studio provides two ways for you to use WinInet. You can call the Win32 Internet functions directly (see the OLE documentation in the Windows SDK for more information) or you can use WinInet through the [MFC WinInet classes](mfc-classes-for-creating-internet-client-applications.md).
+Visual C++ provides two ways for you to use WinInet. You can call the Win32 Internet functions directly (see the OLE documentation in the Windows SDK for more information) or you can use WinInet through the [MFC WinInet classes](mfc-classes-for-creating-internet-client-applications.md).
 
 **You can use WinInet to:**
 

docs/mfc/methods-of-creating-a-status-bar.md

@@ -11,7 +11,7 @@ MFC provides two classes to create status bars: [CStatusBar](reference/cstatusba
 
 `CStatusBarCtrl` usually results in a smaller executable, and you may prefer to use `CStatusBarCtrl` if you do not intend to integrate the status bar into the MFC architecture. If you plan to use `CStatusBarCtrl` and integrate the status bar into the MFC architecture, you must take additional care to communicate status bar control manipulations to MFC. This communication is not difficult; however, it is additional work that is unneeded when you use `CStatusBar`.
 
-Visual Studio provides two ways to take advantage of the status bar common control.
+Visual C++ provides two ways to take advantage of the status bar common control.
 
 - Create the status bar using `CStatusBar`, and then call [CStatusBar::GetStatusBarCtrl](reference/cstatusbar-class.md#getstatusbarctrl) to get access to the `CStatusBarCtrl` member functions.
 

docs/mfc/methods-of-creating-a-toolbar.md

@@ -11,7 +11,7 @@ MFC provides two classes to create toolbars: [CToolBar](reference/ctoolbar-class
 
 `CToolBarCtrl` usually results in a smaller executable, and you may prefer to use `CToolBarCtrl` if you do not intend to integrate the toolbar into the MFC architecture. If you plan to use `CToolBarCtrl` and integrate the toolbar into the MFC architecture, you must take additional care to communicate toolbar control manipulations to MFC. This communication is not difficult; however, it is additional work that is unneeded when you use `CToolBar`.
 
-Visual Studio provides two ways to take advantage of the toolbar common control.
+Visual C++ provides two ways to take advantage of the toolbar common control.
 
 - Create the toolbar using `CToolBar`, and then call [CToolBar::GetToolBarCtrl](reference/ctoolbar-class.md#gettoolbarctrl) to get access to the `CToolBarCtrl` member functions.
 

docs/mfc/mfc-and-atl.md

@@ -12,7 +12,7 @@ The Microsoft Foundation Classes (MFC) provide a C++ object-oriented wrapper ove
 
 You can create MFC or ATL programs with Visual Studio Community Edition or higher. The Express editions do not support MFC or ATL.
 
-In Visual Studio 2015, Microsoft C++ is an optional component, and MFC and ATL components are optional sub-components under Microsoft C++. If you do not select these components when you first install Visual Studio, you will be prompted to install them the first time you attempt to create or open an MFC or ATL project.
+In Visual Studio 2015, Visual C++ is an optional component, and MFC and ATL components are optional sub-components under Visual C++. If you do not select these components when you first install Visual Studio, you will be prompted to install them the first time you attempt to create or open an MFC or ATL project.
 
 In Visual Studio 2017 and later, MFC and ATL are optional sub-components under the **Desktop development with C++** workload in the Visual Studio Installer program. You can install ATL support without MFC, or combined MFC and ATL support (MFC depends on ATL). For more information about workloads and components, see [Install Visual Studio](/visualstudio/install/install-visual-studio).