second pass changes

Author: v-masebo

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/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.  
 
@@ -110,7 +110,7 @@ ms.workload:
  [Outlook object model overview](../vsto/outlook-object-model-overview.md)   
  [PowerPoint solutions](../vsto/powerpoint-solutions.md)   
  [Project solutions](../vsto/project-solutions.md)   
- [Visio Object model overview](../vsto/visio-object-model-overview.md)   
+ [Visio object model overview](../vsto/visio-object-model-overview.md)   
  [Word object model overview](../vsto/word-object-model-overview.md)   
  [General reference &#40;Office development in Visual Studio&#41;](../vsto/general-reference-office-development-in-visual-studio.md)  
 

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

@@ -1,5 +1,5 @@
 ---
-title: "Office Projects in the Visual Studio Environment | Microsoft Docs"
+title: "Office projects in the Visual Studio environment"
 ms.custom: ""
 ms.date: "02/02/2017"
 ms.technology: 
@@ -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.  
 
@@ -104,7 +104,7 @@ ms.workload:
 
  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.  
 
-## Code editor  
+## 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.  
 
  For more information about the Code Editor, see [Write code in the code and text editor](/visualstudio/ide/writing-code-in-the-code-and-text-editor). For more information about how to write code in Office projects, see [Write code in Office solutions](../vsto/writing-code-in-office-solutions.md).  

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: 
@@ -33,7 +33,7 @@ ms.workload:
 
  The types of projects you can create depend on which Office applications you have installed on the development computer. For more information, see [Features available by Office application and project type](../vsto/features-available-by-office-application-and-project-type.md).  
 
-### Document-Level customizations  
+### Document-level customizations  
  Document-level customizations consist of an assembly that is associated with a single document, workbook, or template in Microsoft Office Word or Microsoft Office Excel. The assembly is loaded when the associated document is opened. Features in customizations that you create are available only when the associated document is open. Customizations cannot make application-wide changes, such as displaying a new menu item or ribbon tab when any document is open.  
 
  [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] includes tools to help you create document-level customizations. The document that you customize is hosted as a design surface in [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)], which enables you to design the document by dragging and dropping controls onto it. Many other [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] features are available in document-level projects, such as Windows Forms controls, drag-and-drop data binding, and an integrated debugger.  

docs/vsto/office-ui-customization-walkthroughs.md

@@ -1,5 +1,5 @@
 ---
-title: "Office UI Customization Walkthroughs | Microsoft Docs"
+title: "Office UI customization walkthroughs"
 ms.custom: ""
 ms.date: "02/02/2017"
 ms.technology: 
@@ -19,7 +19,7 @@ manager: douge
 ms.workload: 
   - "office"
 ---
-# Office UI Customization Walkthroughs
+# Office UI customization walkthroughs
   The following walkthroughs demonstrate ways that you can customize the user interface (UI) of Microsoft Office applications by using document-level customizations and VSTO Add-ins.  
 
 ## Actions pane walkthroughs  
@@ -49,10 +49,10 @@ ms.workload:
  [Walkthrough: Update the controls on a Ribbon at runtime](../vsto/walkthrough-updating-the-controls-on-a-ribbon-at-run-time.md)  
  Demonstrates how to use the Ribbon object model to update the controls on a ribbon after the ribbon is loaded into the Office application.  
 
- [Walkthrough: Create a custom tab by Using Ribbon XML](../vsto/walkthrough-creating-a-custom-tab-by-using-ribbon-xml.md)  
+ [Walkthrough: Create a custom tab by using Ribbon XML](../vsto/walkthrough-creating-a-custom-tab-by-using-ribbon-xml.md)  
  Demonstrates how to create a custom ribbon tab by using ribbon XML instead of using the Ribbon Designer.  
 
-## Controls on Word Documents  
+## 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)  
  Demonstrates how to add controls to a document by using an VSTO Add-in.  
 

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: 
@@ -29,7 +29,7 @@ ms.workload:
 
 -   [Custom Ribbon UI](#Ribbon)  
 
--   [Backstage View](#Backstage)  
+-   [Backstage view](#Backstage)  
 
 -   [Outlook form regions](#FormRegion)  
 
@@ -68,7 +68,7 @@ ms.workload:
 
  For more information, see [Ribbon overview](../vsto/ribbon-overview.md).  
 
-##  <a name="Backstage"></a> Backstage View  
+##  <a name="Backstage"></a> Backstage view  
  In Office applications, clicking the **File** tab opens the Backstage view. The Backstage view provides a UI that combines file-level tasks and actions, and replaces similar functionality available from the Microsoft Office button in the 2007 Microsoft Office system. The Backstage view is fully extensible by using XML.  
 
  Visual Studio does not provide a designer or APIs for customizing the Backstage view. However, if you add a **Ribbon (XML)** item to your Office project, you can add XML to the Ribbon XML file to customize the Backstage view. For more information about **Ribbon (XML)** items, see [Ribbon XML](../vsto/ribbon-xml.md).  

docs/vsto/persisting-dynamic-controls-in-office-documents.md

@@ -23,7 +23,7 @@ ms.workload:
   - "office"
 ---
 # Persist dynamic controls in Office documents
-  Controls that are added at run time are not persisted when the document or workbook is saved and closed. The exact behavior is different for host controls and Windows Forms controls. In both cases, you can add code to your solution to re-create the controls when the user reopens the document.  
+  Controls that are added at runtime are not persisted when the document or workbook is saved and closed. The exact behavior is different for host controls and Windows Forms controls. In both cases, you can add code to your solution to re-create the controls when the user reopens the document.  
 
  Controls that you add to documents at run time are called *dynamic controls*. For more information about dynamic controls, see [Add controls to Office documents at runtime](../vsto/adding-controls-to-office-documents-at-run-time.md).  
 
@@ -57,21 +57,21 @@ ms.workload:
 
  If you do not first delete the native <xref:Microsoft.Office.Interop.Excel.Chart>, then you will create a second, duplicate chart when you re-create the <xref:Microsoft.Office.Tools.Excel.Chart>.  
 
-## Persist Windows Forms ontrols in documents  
+## Persist Windows Forms controls in documents  
  When a document is saved and then closed, the [!INCLUDE[vsto_runtime](../vsto/includes/vsto-runtime-md.md)] automatically removes all dynamically created Windows Forms controls from the document. However, the behavior is different for document-level and VSTO Add-in projects.  
 
  In document-level customizations, the controls and their underlying ActiveX wrappers (which are used to host the controls on the document) are removed the next time the document is opened. There is no indication that the controls were ever there.  
 
  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 this data to the data cache in the document. In an VSTO Add-in, you can save this 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  
+###  <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  
@@ -84,7 +84,7 @@ ms.workload:
  [!code-vb[Trin_WordAddInDynamicControls#11](../vsto/codesnippet/VisualBasic/trin_wordaddindynamiccontrols/ThisAddIn.vb#11)]
  [!code-csharp[Trin_WordAddInDynamicControls#11](../vsto/codesnippet/CSharp/Trin_WordAddInDynamicControls/ThisAddIn.cs#11)]  
 
- Although the GetVstoObject method is used primarily to generate a new host item at runtime, this method also clears all ActiveX wrappers from the document the first time it is called for a specific document. For more information about how to use the GetVstoObject method, see [Extend Word documents and Excel workbooks in VSTO Add-ins at runtime](../vsto/extending-word-documents-and-excel-workbooks-in-vsto-add-ins-at-run-time.md).  
+ Although the GetVstoObject method is used primarily to generate a new host item at runtime, this method also clears all ActiveX wrappers from the document the first time it is called for a specific document. For more information about how to use the `GetVstoObject` method, see [Extend Word documents and Excel workbooks in VSTO Add-ins at runtime](../vsto/extending-word-documents-and-excel-workbooks-in-vsto-add-ins-at-run-time.md).  
 
  Note that if your VSTO Add-in creates dynamic controls when the document is opened, your VSTO Add-in will already call the `GetVstoObject` method as part of the process to create the controls. You do not need to add a separate call to the `GetVstoObject` method to remove the ActiveX wrappers in this scenario.  
 

docs/vsto/programmatic-limitations-of-host-items-and-host-controls.md

@@ -44,9 +44,9 @@ ms.workload:
 ## Programmatically create host items  
  When you programmatically create or open a document, workbook, or worksheet at run time by using the Word or Excel object model, the item is not a host item. Instead, the new object is a native Office object. For example, if you use the <xref:Microsoft.Office.Interop.Word.Documents.Add%2A> method to create a new Word document at run time, it will be a native <xref:Microsoft.Office.Interop.Word.Document> object rather than a <xref:Microsoft.Office.Tools.Word.Document> host item. Similarly, when you create a new worksheet at run time using the <xref:Microsoft.Office.Interop.Excel.Worksheets.Add%2A> method, you get a native <xref:Microsoft.Office.Interop.Excel.Worksheet> object rather than a <xref:Microsoft.Office.Tools.Excel.Worksheet> host item.  
 
- In document-level projects, you cannot create host items at run time. Host items can be created only at design time in document-level projects. For more information, see [Document host item](../vsto/document-host-item.md), [Workbook host item](../vsto/workbook-host-item.md), and [Worksheet host item](../vsto/worksheet-host-item.md).  
+ In document-level projects, you cannot create host items at runtime. Host items can be created only at design time in document-level projects. For more information, see [Document host item](../vsto/document-host-item.md), [Workbook host item](../vsto/workbook-host-item.md), and [Worksheet host item](../vsto/worksheet-host-item.md).  
 
- In VSTO Add-in projects, you can create <xref:Microsoft.Office.Tools.Word.Document>, <xref:Microsoft.Office.Tools.Excel.Workbook>, or <xref:Microsoft.Office.Tools.Excel.Worksheet> host items at run time. For more information, see [Extend Word documents and Excel workbooks in VSTO Add-ins at runtime](../vsto/extending-word-documents-and-excel-workbooks-in-vsto-add-ins-at-run-time.md).  
+ In VSTO Add-in projects, you can create <xref:Microsoft.Office.Tools.Word.Document>, <xref:Microsoft.Office.Tools.Excel.Workbook>, or <xref:Microsoft.Office.Tools.Excel.Worksheet> host items at runtime. For more information, see [Extend Word documents and Excel workbooks in VSTO Add-ins at runtime](../vsto/extending-word-documents-and-excel-workbooks-in-vsto-add-ins-at-run-time.md).  
 
 ## Programmatically create host controls  
  You can programmatically add host controls to a <xref:Microsoft.Office.Tools.Word.Document> or <xref:Microsoft.Office.Tools.Excel.Worksheet> host item at runtime. For more information, see [Add controls to Office documents at runtime](../vsto/adding-controls-to-office-documents-at-run-time.md).