minor fixes

Author: lindalu-MSFT

Library-Reference/Concepts/customize-the-office-fluent-ribbon-by-using-an-open-xml-formats-file.md

@@ -8,14 +8,14 @@ ms.localizationpriority: medium
 
 # Customize the Office Fluent ribbon by using an Open XML formats file
 
-The ribbon component of the Microsoft Office Fluent user interface gives users a flexible way to work with Office applications. Ribbon Extensibility (RibbonX) uses a simple, text-based, declarative XML markup to create and customize the ribbon. 
+The ribbon component of the Microsoft Office Fluent user interface gives users a flexible way to work with Office applications. Ribbon Extensibility (RibbonX) uses a simple, text-based, declarative XML markup to create and customize the ribbon.
 
-The code example in this topic shows how to add custom components to the ribbon for a single document, as opposed to adding application-level customizations. In the following steps, you add a custom tab, a custom group, and a custom button to the existing ribbon in Word. You also implement a callback procedure for the button that inserts a company name into the document. 
+The code example in this topic shows how to add custom components to the ribbon for a single document, as opposed to adding application-level customizations. In the following steps, you add a custom tab, a custom group, and a custom button to the existing ribbon in Word. You also implement a callback procedure for the button that inserts a company name into the document.
 
 1. Create the customization file in any text editor and save the file with the name **customUI.xml**.
-    
-2. Add the following XML markup to the file and then close and save the file. 
-    
+
+2. Add the following XML markup to the file and then close and save the file.
+
    ```xml
     <customUI xmlns="http://schemas.microsoft.com/office/2006/01/customui"> 
       <ribbon> 
@@ -31,16 +31,16 @@ The code example in this topic shows how to add custom components to the ribbon
    ```
 
 3. Create a folder on your desktop named **customUI** and copy the XML customization file to the folder.
-    
-4. Validate the XML markup with a custom schema. 
-    
-   > [!NOTE] 
+
+4. Validate the XML markup with a custom schema.
+
+   > [!NOTE]
    > This step is optional.
 
 5. Create a document in Word and save it with the name **RibbonSample.docm**.
-    
+
 6. Open the Visual Basic Editor, and add the following procedure to the **ThisDocument** code module. Close and save the document.
-    
+
     ```vb
       Sub InsertCompanyName(ByVal control As IRibbonControl) 
       ' Inserts the specified text at the beginning of a range or selection. 
@@ -58,29 +58,29 @@ The code example in this topic shows how to add custom components to the ribbon
     ```
 
 7. Add a **.zip** extension to the document file name and then double-click it to open the file.
-    
+
 8. Add the customization file to the container by dragging the customUI folder from the desktop to the .zip file.
-    
+
 9. Extract the **.rels** file to your desktop. A **_rels** folder that contains the .rels file is copied to your desktop.
-    
+
 10. Open the **.rels** file and add the following line between the last **Relationship** tag and the **Relationships** tag. This creates a relationship between the document file and the customization file.
-    
+
     ```xml
      <Relationship Id="someID" Type="http://schemas.microsoft.com/office/2006/relationships/ui/extensibility" Target="customUI/customUI.xml" />
     ```
 
 11. Close and save the file.
-    
+
 12. Add the **.rels** folder back to the container file by dragging it from the desktop, overwriting the existing file.
-    
+
 13. Rename the document file to its original name by removing the .zip extension.
-    
+
 14. Open the document and notice that the ribbon now displays the **My Tab** tab.
-    
+
 15. Choose the tab and notice the **Sample Group** group with a button control.
-    
+
 16. Choose the button to insert the company name into the document.
-    
+
 ## See also
 
 - [Overview of the Office Fluent ribbon](overview-of-the-office-fluent-ribbon.md)

Library-Reference/Concepts/getting-started-with-vba-in-office.md

@@ -7,7 +7,7 @@ ms.localizationpriority: medium
 
 # How AutoSave impacts add-ins and macros
 
-Learn about how AutoSave works in Excel, PowerPoint, and Word, and how it can impact add-ins or macros. 
+Learn about how AutoSave works in Excel, PowerPoint, and Word, and how it can impact add-ins or macros.
 
 ## Overview of AutoSave
 
@@ -48,17 +48,17 @@ You may need to handle one or more of the following issues regarding the interac
 
 ### Issue 1: Code in BeforeSave or AfterSave events runs too long
 
-In general, Word, Excel and PowerPoint are not responsive to user interaction while add-in or macro code is being run. Therefore, if your code in a **BeforeSave** or **AfterSave** event handler takes too long to run, it may significantly degrade the user experience. 
+In general, Word, Excel and PowerPoint are not responsive to user interaction while add-in or macro code is being run. Therefore, if your code in a **BeforeSave** or **AfterSave** event handler takes too long to run, it may significantly degrade the user experience.
 
-When AutoSave is disabled, this code is only run when the user explicitly chooses to save, so a delay is not as noticeable and can be avoided by the user until he or she is ready to save. 
+When AutoSave is disabled, this code is only run when the user explicitly chooses to save, so a delay is not as noticeable and can be avoided by the user until he or she is ready to save.
 
 When AutoSave is enabled, this code runs automatically on a periodic basis, which has the potential to interrupt the user, especially if the code takes a long time.
 
 #### Example scenario
 
-Imagine an add-in that allows the user to create custom maps based on data in an Excel workbook. Such an add-in might have **BeforeSave** code that serializes any maps that the user has created and stores them in the workbook in a CustomXML part. This process might take a second to complete, and Excel could be unresponsive while this is happening. 
+Imagine an add-in that allows the user to create custom maps based on data in an Excel workbook. Such an add-in might have **BeforeSave** code that serializes any maps that the user has created and stores them in the workbook in a CustomXML part. This process might take a second to complete, and Excel could be unresponsive while this is happening.
 
-When AutoSave is off, the user gets to choose when he or she wants to save, and therefore, even though the add-in slows down the save process slightly, the user does not notice. 
+When AutoSave is off, the user gets to choose when he or she wants to save, and therefore, even though the add-in slows down the save process slightly, the user does not notice.
 
 When AutoSave is enabled, this **BeforeSave** code runs automatically on a periodic basis even if the user is in the middle of something else (such as typing data into a cell), which could be extremely annoying.
 
@@ -97,14 +97,14 @@ An add-in might have code that runs in response to the **BeforeSave** event that
 Consider removing code that writes to the workbook in **BeforeSave** or **AfterSave** events. For example, the add-in described in the example scenario might be modified to store the change log in a separate file or database.
 
 <a name="Issue4"></a>
- 
+
 ### Issue 4: Code in **AfterSave** dirties the workbook (Excel only)
 
 When AutoSave is on, the **BeforeSave** and **AfterSave** events will only trigger if there has been a change in the workbook since the last time they were triggered. If code in the **AfterSave** event dirties the workbook (that is, makes additional changes), that could potentially trigger events to fire again for the same change, and then queue up the events to fire again indefinitely. This could waste system resources and affect battery life.
 
 #### Workaround
 
-Code that dirties the workbook in **AfterSave** should be moved to **BeforeSave** or to another location entirely (see [Issue 3](#Issue3)). This isn't a good practice today, even without AutoSave, because it leaves the workbook in a perpetual "dirty" state, which causes a prompt to appear on close that asks the user to save their changes even if they made no additional changes. 
+Code that dirties the workbook in **AfterSave** should be moved to **BeforeSave** or to another location entirely (see [Issue 3](#Issue3)). This isn't a good practice today, even without AutoSave, because it leaves the workbook in a perpetual "dirty" state, which causes a prompt to appear on close that asks the user to save their changes even if they made no additional changes.
 
 <a name="Issue5"></a>
 
@@ -118,7 +118,7 @@ Private Sub Workbook_BeforeSave(ByVal SaveAsUI As Boolean, Cancel As Boolean) 
 End Sub
 ```
 
-When AutoSave is enabled, the application (that is, Excel, Word, or PowerPoint) triggers saves automatically on a continuous basis until the file has no more unsaved changes. After the user makes a single change to the file, the application attempts to save it. 
+When AutoSave is enabled, the application (that is, Excel, Word, or PowerPoint) triggers saves automatically on a continuous basis until the file has no more unsaved changes. After the user makes a single change to the file, the application attempts to save it.
 
 If the developer chooses to cancel the save in the manner described earlier, the application continually determines that there are unsaved changes, which causes the save to (eventually) be attempted again. Because the same event code that cancelled the first save will also cancel this second save attempt, the process will continue for as long as the file is open, potentially degrading performance and battery life.
 

Library-Reference/Concepts/how-autosave-impacts-addins-and-macros.md

@@ -10,10 +10,10 @@ ms.localizationpriority: medium
 
 The **Document Inspector** gives users an easy way to examine documents for personal or sensitive information, text phrases, and other document contents. For example, before distributing a document, they can use the **Document Inspector** to remove unwanted information.
 
-> [!NOTE] 
+> [!NOTE]
 > Microsoft does not support the automatic removal of hidden information for signed or protected documents, or for documents that use Information Rights Management (IRM). We recommend that you run the **Document Inspector** before you sign a document or invoke IRM on a document.
 
-As a developer, you can use the Document Inspector framework to extend the built-in modules and integrate your extensions into the standard user interface. 
+As a developer, you can use the Document Inspector framework to extend the built-in modules and integrate your extensions into the standard user interface.
 
 The **Document Inspector** in Word, Excel, and PowerPoint includes the following enhancements.
 
@@ -23,45 +23,45 @@ The **Document Inspector** has modules that help users inspect and fix specific
 
 ### For all Office documents
 
-- Embedded documents   
-- OLE objects and packages 
-- Data models 
-- Content apps 
-- Task Pane apps 
+- Embedded documents
+- OLE objects and packages
+- Data models
+- Content apps
+- Task Pane apps
 - Macros and VBA modules
 - Legacy macros (XLM and WordBasic)
-    
+
 ### For Excel documents
 
-- PivotTables and slicers 
+- PivotTables and slicers
 - PivotCharts
 - Cube formulas
 - Timelines (cache)
 - Custom XML data
 - Comments and annotations
 - Document properties and personal information
 - Headers and footers
-- Hidden rows and columns   
-- Hidden worksheets and names   
-- Invisible content   
-- External links and data functions   
-- Excel surveys   
+- Hidden rows and columns
+- Hidden worksheets and names
+- Invisible content
+- External links and data functions
+- Excel surveys
 - Custom worksheet properties
-    
+
 ### For PowerPoint documents
 
-- Comments and annotations   
-- Document properties and personal information   
-- Invisible on-slide content   
-- Off-slide content 
+- Comments and annotations
+- Document properties and personal information
+- Invisible on-slide content
+- Off-slide content
 - Presentation notes
-    
+
 ### For Word documents
 
-- Comments, revisions, versions, and annotations 
+- Comments, revisions, versions, and annotations
 - Document properties and personal information; this includes metadata, SharePoint properties, custom properties, and other content information  
-- Custom XML data   
-- Headers, footers, and watermarks   
+- Custom XML data
+- Headers, footers, and watermarks
 - Invisible content  
 - Hidden text
 
@@ -70,11 +70,11 @@ The **Document Inspector** has modules that help users inspect and fix specific
 To open the **Document Inspector**:
 
 1. Choose the **File** tab, and then choose **Info**.
-    
+
 2. Choose **Check for Issues**.
-    
+
 3. Choose **Inspect Document**.
-    
+
 Use the **Document Inspector** dialog box to select the type or types of data to find in the document.
 
 After the modules complete the inspection, the **Document Inspector** displays the results for each module in a dialog box. If a given module finds data, the dialog box includes a **Remove All** button that you can click to remove that data. If the module does not find data, the dialog box displays a message to that effect.

Library-Reference/Concepts/using-the-document-inspector.md

@@ -10,16 +10,15 @@ ms.localizationpriority: medium
 
 Use this procedure to add a control from the [Control Toolbox](../Customizing-Forms/control-toolbox-overview.md) to your form. You can also use this procedure to insert a control in a **[Frame](../../../api/Outlook.frame.md)**, **[TabStrip](../../../api/Outlook.tabstrip.md)**, or **[MultiPage](../../../api/Outlook.multipage.md)** on the form.
 
-
 1. In an open form on the **Developer** tab, in the **Tools** group, click **Control Toolbox**.
-    
+
   **Note** f you don't see the **Developer** tab in the open form, see the topic [Run in Developer Mode in Outlook](../../How-to/Using-Visual-Basic-to-Customize-Outlook-Forms/run-in-developer-mode-in-outlook.md).
 2. Do one of the following:
-    
-  - Click a control in the **Control Toolbox** and then click in the form. The control appears in its default size. You can then drag the border of the control to change its size.
-    
-  - Drag a control from the **Control Toolbox** to the form. The control appears in its default size.
-    
-  - Double-click the control in the **Control Toolbox**, and then click in the form once for each control that you want to create. For example, to create four command buttons, double-click the [CommandButton](../../../api/Outlook.commandbutton.md) control in the **Control Toolbox**, and then click four times in the form.
+
+- Click a control in the **Control Toolbox** and then click in the form. The control appears in its default size. You can then drag the border of the control to change its size.
+
+- Drag a control from the **Control Toolbox** to the form. The control appears in its default size.
+
+- Double-click the control in the **Control Toolbox**, and then click in the form once for each control that you want to create. For example, to create four command buttons, double-click the [CommandButton](../../../api/Outlook.commandbutton.md) control in the **Control Toolbox**, and then click four times in the form.
 
 [!include[Support and feedback](~/includes/feedback-boilerplate.md)]

outlook/Concepts/Specifying-Form-Behavior/add-a-control-to-a-form.md

@@ -8,17 +8,13 @@ ms.localizationpriority: medium
 
 # Add a Modified Control to the Control Toolbox
 
-1. In an open form on the **Developer** tab, in the **Tools** group, click
-![Control Toolbox icon](../../../images/0548_ZA06045100.gif) **Control Toolbox**.
-    
-  **Note** If you don't see the **Developer** tab in the open form, see the topic [Run in Developer Mode in Outlook](../../How-to/Using-Visual-Basic-to-Customize-Outlook-Forms/run-in-developer-mode-in-outlook.md).
-2. Drag a control from the **Control Toolbox** to your form and customize it. For example, to create an **OK** button, drag a **CommandButton** control onto the form, set its **Caption** property to **OK**, and set its **Default** property to **True**. 
-    
-3. Select the customized control. 
-    
-4. Drag the control to the **Control Toolbox**.
-    
+1. In an open form on the **Developer** tab, in the **Tools** group, select **Control Toolbox**.
+![Control Toolbox icon](../../../images/0548_ZA06045100.gif)
+**Note** If you don't see the **Developer** tab in the open form, see the [Run in Developer Mode in Outlook](../../How-to/Using-Visual-Basic-to-Customize-Outlook-Forms/run-in-developer-mode-in-outlook.md).
+1. Drag a control from the **Control Toolbox** to your form and customize it. For example, to create an **OK** button, drag a **CommandButton** control onto the form, set its **Caption** property to **OK**, and set its **Default** property to **True**.
+1. Select the customized control.
+1. Drag the control to the **Control Toolbox**.
 
- **Note** When you drag a control onto the **Control Toolbox**, you only transfer the advanced property values. Any lines of code or Outlook property values that you have written for that control don't transfer with the control. You must write new code or copy code from the control on the form to the control on the **Control Toolbox**.
+**Note** When you drag a control onto the **Control Toolbox**, you only transfer the advanced property values. Any lines of code or Outlook property values that you have written for that control don't transfer with the control. You must write new code or copy code from the control on the form to the control on the **Control Toolbox**.
 
-[!include[Support and feedback](~/includes/feedback-boilerplate.md)]
+[!include[Support and feedback](~/includes/feedback-boilerplate.md)]

outlook/Concepts/Specifying-Form-Behavior/add-a-modified-control-to-the-control-toolbox.md

@@ -9,11 +9,11 @@ ms.localizationpriority: medium
 # Add Items to a List in Design Mode
 
 1. In Forms Designer, drag the **[ListBox](../../../api/Outlook.listbox.md)** or **[ComboBox](../../../api/Outlook.combobox.md)** control from the [Control Toolbox](show-or-hide-the-control-toolbox.md) to the form.
-    
+
 2. Right-click the control, then click **Properties** on the shortcut menu.
-    
+
 3. In the **Properties** dialog box, on the **Value** tab, click **Choose Field**, point to the **User-defined** field set, and then click the custom field to which you want the control bound.
-    
+
 4. In the **Possible values** box, type the values for the items that you want to appear in the list, separated by semicolons.
 
-[!include[Support and feedback](~/includes/feedback-boilerplate.md)]
+[!include[Support and feedback](~/includes/feedback-boilerplate.md)]

outlook/Concepts/Specifying-Form-Behavior/add-items-to-a-list-in-design-mode.md

@@ -8,13 +8,10 @@ ms.localizationpriority: medium
 
 # Add Other Custom Controls to the Control Toolbox
 
-
-
-
 1. In Forms Designer, on the **Developer** tab, in the **Tools** group, click [Control Toolbox](../Customizing-Forms/control-toolbox-overview.md).
-    
+
 2. Right-click any control or an empty area on any page of the **Control Toolbox**, and then click **Custom Controls** on the shortcut menu.
-    
+
 3. In the **Available Controls** box, select the check box next to the controls that you want to add.
 
-[!include[Support and feedback](~/includes/feedback-boilerplate.md)]
+[!include[Support and feedback](~/includes/feedback-boilerplate.md)]

outlook/Concepts/Specifying-Form-Behavior/add-other-custom-controls-to-the-control-toolbox.md

@@ -8,15 +8,14 @@ ms.localizationpriority: medium
 
 # Adding Items to a List
 
-You can add items to a list box or a combo box at design time or at run time. 
+You can add items to a list box or a combo box at design time or at run time.
 
 To save contents in an item, **[ListBox](../../../api/Outlook.listbox.md)** and **[ComboBox](../../../api/Outlook.combobox.md)** controls must be bound to a field.
 
 For more information, see the following topics:
 
-
 - [How to: Add Items to a List at Design Time](add-items-to-a-list-in-design-mode.md)
-    
+
 - [How to: Add Items to a List at Run Time](../../How-to/General/how-to-add-items-to-a-list-or-combo-box-at-run-time.md)
 
-[!include[Support and feedback](~/includes/feedback-boilerplate.md)]
+[!include[Support and feedback](~/includes/feedback-boilerplate.md)]