Merge pull request #2128 from msebolt/v-masebo-vsto-pr7

[VSTO] V masebo vsto pr7

Author: TrishaMc

docs/vsto/microsoft-office-excel-keyboard-microsoft-office-keyboard-settings-options-dialog-box.md

@@ -1,5 +1,5 @@
 ---
-title: "Microsoft Office Excel Keyboard, Microsoft Office Keyboard Settings, Options Dialog Box | Microsoft Docs"
+title: "Microsoft Office Excel Keyboard, Microsoft Office Keyboard Settings, Options dialog box"
 ms.custom: ""
 ms.date: "02/02/2017"
 ms.technology: 
@@ -20,14 +20,14 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Microsoft Office Excel Keyboard, Microsoft Office Keyboard Settings, Options Dialog box
+# Microsoft Office Excel Keyboard, Microsoft Office Keyboard Settings, Options dialog box
   Microsoft Office Excel and Visual Studio both handle shortcut keys. The same shortcut key combination can stand for different commands in Excel and in Visual Studio. When Excel is open in a document-level project in Visual Studio, only one application at a time receives the shortcut key commands. By default, Visual Studio receives all shortcut key commands, but you can make Excel receive them when the document has focus by selecting **Dynamic keyboard scheme**.  
 
  If you use a shortcut key that is not assigned to a command in the application that is currently handling the shortcut keys, the shortcut key is passed on to the other application.  
 
  The option that you select will remain in effect for Excel projects until you change it. The selection does not affect Microsoft Office Word projects; you must make any change for Word using the Microsoft Office Word Keyboard options.  
 
-## UIElement List  
+## UIElement list  
  **Visual Studio keyboard scheme**  
  Visual Studio receives all shortcut key commands, even if Excel has focus. For example, if you press the function key **F5** while Excel has focus, Visual Studio starts debugging your solution.  
 

docs/vsto/microsoft-office-is-not-installed-on-this-computer.md

@@ -1,5 +1,5 @@
 ---
-title: "Microsoft Office is not installed on this computer | Microsoft Docs"
+title: "Microsoft Office is not installed on this computer"
 ms.custom: ""
 ms.date: "02/02/2017"
 ms.technology: 

docs/vsto/office-primary-interop-assemblies.md

@@ -67,7 +67,7 @@ ms.workload:
 ##  <a name="usingfeatures"></a> Use features of multiple Microsoft Office applications in a single project  
  Every Office project template in Visual Studio is designed to work with a single Microsoft Office application. To use features in multiple Microsoft Office applications, or to use features in an application or component that does not have a project in Visual Studio, you must add a reference to the required PIAs.  
 
- In most cases, you should add references to the PIAs that are installed by Visual Studio under the *%ProgramFiles%\Microsoft Visual Studio 12.0\Visual Studio Tools for Office\PIA\* directory. These versions of the assemblies appear on the **Framework** tab of the **Reference Manger** dialog box. For more information, see [How to: Target Office applications through Primary interop assemblies](../vsto/how-to-target-office-applications-through-primary-interop-assemblies.md).  
+ In most cases, you should add references to the PIAs that are installed by Visual Studio under the *%ProgramFiles%\Microsoft Visual Studio 12.0\Visual Studio Tools for Office\PIA\* directory. These versions of the assemblies appear on the **Framework** tab of the **Reference Manger** dialog box. For more information, see [How to: Target Office applications through primary interop assemblies](../vsto/how-to-target-office-applications-through-primary-interop-assemblies.md).  
 
  If you have installed and registered the PIAs in the global assembly cache, these versions of the assemblies appear on the **COM** tab of the **Reference Manager** dialog box. You should avoid adding references to these versions of the assemblies, because there are some development issues that can occur when you use them. For example, if you have registered different versions of the PIAs in the global assembly cache, your project will automatically bind to the version of the assembly that was registered last—even if you specify a different version of the assembly on the **COM** tab of the **Reference Manager** dialog box.  
 

docs/vsto/office-project-templates-overview.md

@@ -1,5 +1,5 @@
 ---
-title: "Office Project Templates Overview | Microsoft Docs"
+title: "Office project templates overview"
 ms.custom: ""
 ms.date: "02/02/2017"
 ms.technology: 

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

@@ -88,7 +88,7 @@ ms.workload:
  For more information, see [Host items and host controls overview](../vsto/host-items-and-host-controls-overview.md) and [Windows forms controls on Office documents overview](../vsto/windows-forms-controls-on-office-documents-overview.md).  
 
 ### Excel worksheets and workbooks in the Designer  
- When you open a worksheet in the designer, you can modify the worksheet in the same way that you can when it is open directly in Excel. If you double-click a worksheet cell, the cell changes to edit mode. If you double-click a cell that contains a host control, the code editor opens and Visual Studio generates the default event handler for the control. To navigate to other worksheets, you can click the worksheet tabs at the bottom of the designer.  
+ When you open a worksheet in the designer, you can modify the worksheet in the same way that you can when it is open directly in Excel. If you double-click a worksheet cell, the cell changes to edit mode. If you double-click a cell that contains a host control, the Code Editor opens and Visual Studio generates the default event handler for the control. To navigate to other worksheets, you can click the worksheet tabs at the bottom of the designer.  
 
  When you open the workbook in the designer, there is no design surface. The design view for the workbook is a large component tray that fills the designer.  
 
@@ -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

@@ -1,5 +1,5 @@
 ---
-title: "Office Solutions Development Overview (VSTO) | Microsoft Docs"
+title: "Office solutions development overview (VSTO)"
 ms.custom: ""
 ms.date: "02/02/2017"
 ms.technology: 
@@ -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/office-ui-customization-walkthroughs.md

@@ -53,7 +53,7 @@ ms.workload:
  Demonstrates how to create a custom ribbon tab by using ribbon XML instead of using the Ribbon Designer.  
 
 ## Controls on Word documents  
- [Walkthrough: Add controls to a document at runtime in a VSTO add-In](../vsto/walkthrough-adding-controls-to-a-document-at-run-time-in-a-vsto-add-in.md)  
+ [Walkthrough: Add controls to a document at runtime in a VSTO Add-In](../vsto/walkthrough-adding-controls-to-a-document-at-run-time-in-a-vsto-add-in.md)  
  Demonstrates how to add controls to a document by using an VSTO Add-in.  
 
  [Walkthrough: Change document formatting using CheckBox controls](../vsto/walkthrough-changing-document-formatting-using-checkbox-controls.md)  

docs/vsto/office-ui-customization.md

@@ -1,5 +1,5 @@
 ---
-title: "Office UI Customization | Microsoft Docs"
+title: "Office UI customization"
 ms.custom: ""
 ms.date: "02/02/2017"
 ms.technology: 

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

@@ -17,15 +17,17 @@ ms.workload:
   - "office"
 ---
 # 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.  
+  This error appears when you import a form region that is designed in Outlook, but one or more fields on the form region aren't 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 has a **Business Address** field, you'll receive this error because a task doesn't 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.  
+ You might select **Task (IPM.Task)** on the final page of the **New Form Region** wizard. If the form region has a **Business Address** field, you'll receive this error because a task doesn't 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.  
 
--   In the Forms Designer in Outlook, remove fields that are not compatible with the message classes that you plan to select on the final page of the **New Form Region** wizard.  
+-   In the Forms Designer in Outlook, remove fields that aren't compatible with the message classes. Remove fields that you plan to select on the final page of the **New Form Region** wizard.  
 
 ## See also  
  [Walkthrough: Import a form region that is designed in Outlook](../vsto/walkthrough-importing-a-form-region-that-is-designed-in-outlook.md)  

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/persisting-dynamic-controls-in-office-documents.md

@@ -64,15 +64,15 @@ ms.workload:
 
  In VSTO Add-ins, the controls are removed, but the ActiveX wrappers remain in the document. The next time the user opens the document, the ActiveX wrappers are visible. In Excel, the ActiveX wrappers display images of the controls as they appeared the last time the document was saved. In Word, the ActiveX wrappers are invisible unless the user clicks on them, in which case they display a dotted line that represents the border of the controls. There are several ways you can remove the ActiveX wrappers. For more information, see [Remove ActiveX Wrappers in an Add-in](#removingActiveX).  
 
-### Re-create Windows forms controls when documents are opened  
+### Re-create Windows Forms controls when documents are opened  
  You can re-create deleted Windows Forms controls when the user reopens the document. To do this, your solution must perform the following tasks:  
 
 1.  Store information about the size, location, and state of the controls when the document is saved or closed. In a document-level customization, you can save the data to the data cache in the document. In a VSTO Add-in, you can save the data to a custom XML part in the document.  
 
 2.  Re-create the controls in an event that is raised when the document is opened. In document-level projects, you can do this in the `Sheet`*n*`_Startup` or `ThisDocument_Startup` event handlers. In VSTO Add-in projects, you can do this in the event handlers for the <xref:Microsoft.Office.Interop.Excel.AppEvents_Event.WorkbookOpen> or <xref:Microsoft.Office.Interop.Word.ApplicationEvents4_Event.DocumentOpen> events.  
 
-###  <a name="removingActiveX"></a> Remove ActiveX Wrappers in an Add-in  
- When you add dynamic Windows Forms controls to documents by using a VSTO Add-in, you can prevent the ActiveX wrappers for the controls from appearing in the document the next time it is opened in the following ways.  
+###  <a name="removingActiveX"></a> Remove ActiveX wrappers in an Add-in  
+ When you add dynamic Windows Forms controls to documents by using an VSTO Add-in, you can prevent the ActiveX wrappers for the controls from appearing in the document the next time it is opened in the following ways.  
 
 #### Remove ActiveX wrappers when the document is opened  
  To remove all ActiveX wrappers, call the `GetVstoObject` method to generate a host item for the <xref:Microsoft.Office.Interop.Word.Document> or <xref:Microsoft.Office.Interop.Excel.Workbook> that represents the newly opened document. For example, to remove all ActiveX wrappers from a Word document, you can call the `GetVstoObject` method to generate a host item for the <xref:Microsoft.Office.Interop.Word.Document> object that is passed to the event handler for the <xref:Microsoft.Office.Interop.Word.ApplicationEvents4_Event.DocumentOpen> event.  

docs/vsto/postaction-element-office-development-in-visual-studio.md

@@ -1,5 +1,5 @@
 ---
-title: "<postAction> Element (Office Development in Visual Studio) | Microsoft Docs"
+title: "<postAction> element (Office development in Visual Studio)"
 ms.custom: ""
 ms.date: "02/02/2017"
 ms.technology: 
@@ -18,12 +18,12 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# <postAction> Element (Office Development in Visual Studio)
+# <postAction> element (Office development in Visual Studio)
   The `postAction` element of the `vstav3` namespace contains the `entrypoint` elements and all `postActionData` elements that are associated with post-deployment actions, which run after Office solutions are installed.  
 
 ## Syntax  
 
-```  
+```xml  
 <postAction>  
   <entryPoint>  
   </entryPoint>  
@@ -32,27 +32,27 @@ ms.workload:
 </postAction>  
 ```  
 
-## Elements and Attributes  
+## Elements and attributes  
  The `postAction` element is optional and it is in the `vstav3` namespace. There is one `postAction` element defined in an application manifest for each post-deployment action.  
 
  The `postAction` element has no attributes.  
 
  `postAction` has the following elements.  
 
 ### entryPoint  
- Optional. The role of the `entryPoint` element in the `vstav3` namespace is defined in [&#60;entryPoints&#62; Element &#40;Office Development in Visual Studio&#41;](../vsto/entrypoints-element-office-development-in-visual-studio.md).  
+ Optional. The role of the `entryPoint` element in the `vstav3` namespace is defined in [&#60;entryPoints&#62; element &#40;Office development in Visual Studio&#41;](../vsto/entrypoints-element-office-development-in-visual-studio.md).  
 
 ### postActionData  
- Optional. The role of the `postActionData` element in the `vstav3` namespace is defined in [&#60;postActionData&#62; Element &#40;Office Development in Visual Studio&#41;](../vsto/postactiondata-element-office-development-in-visual-studio.md).  
+ Optional. The role of the `postActionData` element in the `vstav3` namespace is defined in [&#60;postActionData&#62; element &#40;Office development in Visual Studio&#41;](../vsto/postactiondata-element-office-development-in-visual-studio.md).  
 
-## Post-Deployment Action Example  
+## Post-deployment action example  
 
 ### Description  
- The following code example illustrates the `postAction` element in an application manifest for an Office solution that is deployed by using [!INCLUDE[ndptecclick](../vsto/includes/ndptecclick-md.md)]. This code example is part of a larger example provided in [Application Manifests for Office Solutions](../vsto/application-manifests-for-office-solutions.md).  
+ The following code example illustrates the `postAction` element in an application manifest for an Office solution that is deployed by using [!INCLUDE[ndptecclick](../vsto/includes/ndptecclick-md.md)]. This code example is part of a larger example provided in [Application manifests for Office solutions](../vsto/application-manifests-for-office-solutions.md).  
 
 ### Code  
 
-```  
+```xml
 <vstav3:postAction>  
   <vstav3:entryPoint   
     class="PostDeploymentAction.PostDeploymentActionSample">  
@@ -67,9 +67,9 @@ ms.workload:
 </vstav3:postAction>  
 ```  
 
-## See Also  
- [Application Manifests for Office Solutions](../vsto/application-manifests-for-office-solutions.md)   
- [Deployment Manifests for Office Solutions](../vsto/deployment-manifests-for-office-solutions.md)   
- [ClickOnce Application Manifest](/visualstudio/deployment/clickonce-application-manifest)  
+## See also  
+ [Application manifests for Office solutions](../vsto/application-manifests-for-office-solutions.md)   
+ [Deployment manifests for Office solutions](../vsto/deployment-manifests-for-office-solutions.md)   
+ [ClickOnce application manifest](/visualstudio/deployment/clickonce-application-manifest)  
 
 

docs/vsto/postactiondata-element-office-development-in-visual-studio.md

@@ -1,5 +1,5 @@
 ---
-title: "<postActionData> Element (Office Development in Visual Studio) | Microsoft Docs"
+title: "<postActionData> element (Office development in Visual Studio)"
 ms.custom: ""
 ms.date: "02/02/2017"
 ms.technology: