changes per @TerryGLee

Author: v-masebo

docs/vsto/office-projects-in-the-visual-studio-environment.md

@@ -99,10 +99,10 @@ ms.workload:
 
  The document has an associated code file. The code file contains a generated *host item* class that represents the document. For more information, see [Document host item](../vsto/document-host-item.md).  
 
-### Design mode vs. run time mode  
+### Design mode vs. runtime mode  
  When a document is open in the Visual Studio environment, it is always in *design mode*. Some tasks, such as dragging a host control to the document surface, can be performed only design mode.  
 
- To view the document in *run-time mode*, you must open the application and the document outside Visual Studio. You can also build and run the project, which will automatically open the document and application outside Visual Studio.  
+ To view the document in *runtime mode*, you must open the application and the document outside Visual Studio. You can also build and run the project, which will automatically open the document and application outside Visual Studio.  
 
 ## Code Editor  
  The Code Editor enables you to view and modify the visible code files in your solution. These files contain the code that defines the behavior of your solution.  
@@ -112,7 +112,7 @@ ms.workload:
 ## Properties window  
  The **Properties** window displays properties for project items that are selected in **Solution Explorer**, and for UI elements that are selected in the designer, such as controls or the document in a document-level project. Some properties are specific to the application and document, and some properties are the same across all projects.  
 
-## Data sources window  
+## Data Sources window  
  You can use the **Data Sources** window in document-level Office projects to drag a data source onto your document and create a control that is bound to the data source. For more information, see [Bind controls to data in Visual Studio](/visualstudio/data-tools/bind-controls-to-data-in-visual-studio).  
 
 ## See also  

docs/vsto/office-solutions-development-overview-vsto.md

@@ -70,7 +70,7 @@ ms.workload:
 
 -   [Office primary interop assemblies](../vsto/office-primary-interop-assemblies.md)  
 
-## Run Microsoft VSTO Office solutions on end user computers  
+## Run Microsoft VSTO Office solutions on end-user computers  
  When you create a VSTO Office solution, consider how the deployment requirements might affect your development choices.  
 
 ### Deployment options  

docs/vsto/one-or-more-properties-in-the-dot-ofs-file-are-not-valid-for-the-message-class-selected.md

@@ -18,10 +18,12 @@ ms.workload:
 ---
 # One or more properties in the .ofs file are not valid for the message class selected
   This error appears when you import a form region that is designed in Outlook, but one or more fields on the form region are not compatible with the message classes that you select on the final page of the **New Form Region** wizard.  
+
+For example, you might select **Task (IPM.Task)** on the final page of the **New Form Region** wizard. If the form region contains a **Business Address** field, you will receive this error because a task does not have a business address. Therefore, the **Business Address** field is not compatible with the `IPM.Task` message class.  
 
  You might select **Task (IPM.Task)** on the final page of the **New Form Region** wizard. If the form region contains a **Business Address** field, you will receive this error because a task does not have a business address. Therefore, the **Business Address** field is not compatible with the `IPM.Task` message class.  
 
-### To correct this error  
+## To correct this error  
 
 -   On the final page of the **New Form Region** wizard, select a message class that is compatible with the fields on the form region.  
 

docs/vsto/outlook-object-model-overview.md

@@ -59,7 +59,7 @@ ms.workload:
 
 -   The <xref:Microsoft.Office.Interop.Outlook._Application.Inspectors%2A> property, which you can use to access the windows that display the contents of a single item, such as an e-mail message or meeting request.  
 
- To get an instance of the <xref:Microsoft.Office.Interop.Outlook.Application> object, use the Application field of the `ThisAddIn` class in your project. For more information, see [Program VSTO add-ins](../vsto/programming-vsto-add-ins.md).  
+ To get an instance of the <xref:Microsoft.Office.Interop.Outlook.Application> object, use the Application field of the `ThisAddIn` class in your project. For more information, see [Program VSTO Add-ins](../vsto/programming-vsto-add-ins.md).  
 
 > [!NOTE]  
 >  To help avoid security warnings when you use properties and methods that are blocked by the Outlook object model guard, get Outlook objects from the Application field of the `ThisAddIn` class. For more information, see [Specific security considerations for Office solutions](../vsto/specific-security-considerations-for-office-solutions.md).  

docs/vsto/powerpoint-solutions.md

@@ -74,9 +74,9 @@ ms.workload:
  [Walkthrough: Create your first VSTO Add-in for PowerPoint](../vsto/walkthrough-creating-your-first-vsto-add-in-for-powerpoint.md)   
  [Get started programming VSTO Add-ins](../vsto/getting-started-programming-vsto-add-ins.md)   
  [Office solutions development overview (VSTO)](../vsto/office-solutions-development-overview-vsto.md)   
- [Architecture of VSTO add-ins](../vsto/architecture-of-vsto-add-ins.md)   
+ [Architecture of VSTO Add-ins](../vsto/architecture-of-vsto-add-ins.md)   
  [How to: Create Office projects in Visual Studio](../vsto/how-to-create-office-projects-in-visual-studio.md)   
- [Program VSTO Add-Ins](../vsto/programming-vsto-add-ins.md)   
+ [Program VSTO Add-ins](../vsto/programming-vsto-add-ins.md)   
  [Write code in Office solutions](../vsto/writing-code-in-office-solutions.md)   
  [Office primary interop assemblies](../vsto/office-primary-interop-assemblies.md)   
  [Office UI customization](../vsto/office-ui-customization.md)