Merge pull request #1447 from MicrosoftDocs/lindalu-loc-fix

fix build errors

Author: lindalu-MSFT

api/Access.Attachment.md

@@ -7,7 +7,7 @@ ms.prod: access
 api_name:
 - Access.Attachment
 ms.assetid: b0756145-9012-f9b9-7df9-e168defed3bf
-ms.date: 02/07/2019
+ms.date: 09/21/2021
 ms.localizationpriority: medium
 ---
 

api/PowerPoint.ParagraphFormat.FarEastLineBreakControl.md

@@ -7,34 +7,29 @@ ms.prod: powerpoint
 api_name:
 - PowerPoint.ParagraphFormat.FarEastLineBreakControl
 ms.assetid: ffc0cb13-b547-5a33-e661-8a2cc4237e88
-ms.date: 06/08/2017
+ms.date: 09/08/2021
 ms.localizationpriority: medium
 ---
 
-
 # ParagraphFormat.FarEastLineBreakControl property (PowerPoint)
 
 Returns or sets the line break control option if you have an Asian language setting specified. Read/write.
 
-
 ## Syntax
 
 _expression_. `FarEastLineBreakControl`
 
 _expression_ A variable that represents a [ParagraphFormat](PowerPoint.ParagraphFormat.md) object.
 
-
 ## Return value
 
 MsoTriState
 
-
 ## Remarks
 
-The value of the  **FarEastLineBreakControl** property can be one of these **MsoTriState** constants.
+The value of the **FarEastLineBreakControl** property can be one of these **MsoTriState** constants.
 
-
-|||
+|Value|Description|
 |:-----|:-----|
 |**msoFalse**|The line break control option is not selected.|
 |**msoTrue**|The line break control option is selected.|
@@ -48,10 +43,8 @@ This example selects the line break option for the text in shape one on the firs
 ActivePresentation.Slides(1).Shapes(1).TextFrame.TextRange.ParagraphFormat.FarEastLineBreakControl = msoTrue
 ```
 
-
 ## See also
 
-
 [ParagraphFormat Object](PowerPoint.ParagraphFormat.md)
 
-[!include[Support and feedback](~/includes/feedback-boilerplate.md)]
+[!include[Support and feedback](~/includes/feedback-boilerplate.md)]

api/Project.Application.ManageSiteColumns.md

@@ -7,7 +7,7 @@ ms.prod: project-server
 api_name:
 - Project.Application.ManageSiteColumns
 ms.assetid: 1900552c-6320-2ff5-4a07-bc6ebee60696
-ms.date: 06/08/2017
+ms.date: 09/08/2021
 ms.localizationpriority: medium
 ---
 
@@ -16,7 +16,6 @@ ms.localizationpriority: medium
 
 Displays the **Manage Fields** dialog box, which enables synchronizing built-in fields and custom fields in a local project with specified columns in a SharePoint 2013 tasks list.
 
-
 ## Syntax
 
 _expression_. `ManageSiteColumns`
@@ -28,17 +27,14 @@ _expression_. `ManageSiteColumns`
 
  **Boolean**
 
-
 ## Remarks
 
 The **ManageSiteColumns** method is available only in Project Professional, with a local project that has been saved to a SharePoint task list. For more information, see the **[SynchronizeWithSite](Project.Application.SynchronizeWithSite.md)** method.
 
 The following table shows the columns and default synchronized fields in the **Manage Fields** dialog box. By default, the **Priority** and **Task Status** SharePoint columns are not synchronized with any Project field, so those items are empty.
 
-
-||||
-|:-----|:-----|:-----|
 |**Sync**|**Project Field**|**SharePoint Column**|
+|:-----|:-----|:-----|
 |Yes|Name|Title|
 |Yes|Start|Start Date|
 |Yes|Finish|Due Date|
@@ -50,19 +46,12 @@ The following table shows the columns and default synchronized fields in the **M
 
 ## Example
 
-To add the **Priority** field in the Project Field column and synchronize with the **Priority** column in SharePoint, for example, you could do the following:
+To add the **Priority** field in the Project Field column and synchronize with the **Priority** column in SharePoint, try the following:
 
 
-1. Rename a text custom field in Project; for example, name  **Text1** as **SharePoint Priority**.
-    
-2. Run the **ManageSiteColumns** method, and then in the **Manage Fields** dialog box, select **SharePoint Priority (Text1)** in the **Project Field** drop-down list that corresponds to **Priority** in the SharePoint column.
-    
+1. Rename a text custom field in Project; for example, name  **Text1** as **SharePoint Priority**.    
+2. Run the **ManageSiteColumns** method, and then in the **Manage Fields** dialog box, select **SharePoint Priority (Text1)** in the **Project Field** drop-down list that corresponds to **Priority** in the SharePoint column.    
 3. Run the **SyncPriority** macro.
-    
-
-
-
-
 
 ```vb
 Sub SyncPriority() 
@@ -86,4 +75,4 @@ Sub SyncPriority()
 End Sub
 ```
 
-[!include[Support and feedback](~/includes/feedback-boilerplate.md)]
+[!include[Support and feedback](~/includes/feedback-boilerplate.md)]

api/Project.Task.Priority.md

@@ -45,7 +45,6 @@ Project uses the **Priority** property of the project summary task (task 0) to d
 
 The following example sets the tasks on the critical path to a very high priority in the active project.
 
-
 ```vb
 Sub SetPriorityOfCriticalTasks() 
     Dim T As Task ' Task object used in For Each loop 

outlook/Concepts/Configuring-Forms/specify-icons-to-be-displayed-for-a-form-region.md

@@ -1,13 +1,13 @@
 ---
-title: Specify Icons to be Displayed for a Form Region
+title: Specify icons to be displayed for a form region
 ms.prod: outlook
 ms.assetid: 9ffb9f46-a3b9-d90c-6771-9cd9f9b2e04a
-ms.date: 06/08/2019
+ms.date: 09/18/2021
 ms.localizationpriority: medium
 ---
 
 
-# Specify Icons to be Displayed for a Form Region
+# Specify icons to be displayed for a form region
 
 When you define a form region for a custom message class, such as **IPM.Note.Customer**, you can specify custom icons to be displayed in the explorer, inspector, and the ribbon for items belonging to that message class. 
 
@@ -20,11 +20,14 @@ Icons are specified as resources in a Win32 resource DLL file. You can refer to
 
 Note that you can specify environment variables in the file path names, but you cannot specify paths in Universal Naming Convention (UNC).
 By default, if you do not specify any custom icons, the icons assigned to the parent message class will be used. For example, if you do not specify any icons for a form region for **IPM.Note.Customer**, then the icons for **IPM.Note** will be used.
+
 Depending on the type of item, there are different states of the item that you can consider distinguishing with separate icons. For example, in the explorer, a task item can use a custom icon to identify itself as recurrent, and a mail item can use a custom icon to identify itself as having been replied to. You do not have to specify a separate icon for each state that the type of item can be in; you can choose to specify a default icon that will be displayed in all states in the explorer, inspector, and ribbon that apply for that item type.
+
 The following table shows the states of an item that you can consider to identify with custom icons in the explorer, inspector, or ribbon. All custom icons for a form region are specified under the **icons** element in the form region manifest XML file for that form region. Each state is mapped with an XML child element of the **icons** element. You will specify this form region manifest XML file when you register the form region in the Windows registry. For more information on registering a form region, see [Specifying Form Regions in the Windows Registry](../Creating-Form-Regions/specifying-form-regions-in-the-windows-registry.md).
 
 
 | **State of an Item**| **XML Child Element**| **Example**|
+|:-----|:-----|:-----|
 |Any state that applies to the item, if no other custom icon has been defined for that state.| **default**| `<default>c:\default.ico</default>`|
 |Icon to identify in the explorer that item has been encrypted.| **encrypted**| `<encrypted>c:\encryptedicon.ico</encrypted>`|
 |Icon to identify in the explorer that item has been forwarded.| **forwarded**| `<forwarded>c:\forwardedicon.ico</forwarded>`|
@@ -43,10 +46,9 @@ The following table shows the states of an item that you can consider to identif
 
 1. In the form region manifest XML file, under the **icons** element, specify the child element that maps to the state that you would like to customize.
 
-2. Depending on how you would like the custom icon file to be specified, do either of the following: 
-    
-      - If you want Outlook to load the icon from an icon file or a resource file, specify the location of the icon file or resource file in the child element.
-    
+2. Depending on how you would like the custom icon file to be specified, do either of the following:
+
+  - If you want Outlook to load the icon from an icon file or a resource file, specify the location of the icon file or resource file in the child element.
   - If you want an add-in to inform Outlook which icon to display, specify  `addin` in the child element.
 
 The following example specifies custom icons for several states of an item belonging to the message class supported by a form region: 
@@ -62,16 +64,12 @@ The following example specifies custom icons for several states of an item belon
 
 The four custom icons include:
 
-
-- A custom icon file for the read state
-    
-- A custom icon file for the unread state
-    
-- A location in a resource file for the encrypted state
-    
+- A custom icon file for the read state    
+- A custom icon file for the unread state    
+- A location in a resource file for the encrypted state    
 - A default icon file for all other states applicable to the item
 
+> [!NOTE]
+> The value of the child element can be expressed either as a file path to an icon file or a resource file, or as  `addin`. The file path can be expressed as a full path or a path relative to the location of the form region manifest XML file, and can involve system variables. For more information on specifying an icon using an add-in, see [How to: Use an Add-in to Specify Icons for a Form Region](../Specifying-Form-Behavior/use-an-add-in-to-specify-icons-for-a-form-region.md).
 
- **Note** The value of the child element can be expressed either as a file path to an icon file or a resource file, or as  `addin`. The file path can be expressed as a full path or a path relative to the location of the form region manifest XML file, and can involve system variables. For more information on specifying an icon using an add-in, see [How to: Use an Add-in to Specify Icons for a Form Region](../Specifying-Form-Behavior/use-an-add-in-to-specify-icons-for-a-form-region.md).
-
-[!include[Support and feedback](~/includes/feedback-boilerplate.md)]
+[!include[Support and feedback](~/includes/feedback-boilerplate.md)]

outlook/Concepts/Creating-Form-Regions/add-a-form-region-to-an-existing-page-on-a-form.md

@@ -2,7 +2,7 @@
 title: Add a Form Region to an Existing Page on a Form
 ms.prod: outlook
 ms.assetid: 3c988dac-f171-966d-cf9a-17139353d604
-ms.date: 09/08/2021
+ms.date: 09/21/2021
 ms.localizationpriority: medium
 ---
 
@@ -120,11 +120,8 @@ To create and design a form region, you will use the Forms Designer in much the
    1. Pick and click the label control to add it from the Toolbox to the form region as shown in Figure 12.
    2. Right-click the label control, click **Properties**. On the **Display** tab, type **Seat Preference:** as the **Caption**. Click **OK**.
    3. Pick and click the combo box control to add it from the Toolbox to the form region as shown in Figure 12.
-   4. Right-click the combo box control, click **Properties**. On the **Value** tab, click **Choose Field**. Point to **User-defined field in folder** in the drop-down list, and click **Seat Preference**, as in Figure 12. 
-    
-     **Figure 12. Bind the Seat Preference field to the combo box control.**
+   4. Right-click the combo box control, click **Properties**. On the **Value** tab, click **Choose Field**. Point to **User-defined field in folder** in the drop-down list, and click **Seat Preference**, as in the following figure
      ![Screenshot of the Value tab on the Properties dialog box binding the seat preference field to the combo box control.](../../../images/olPropertiesDialogSPValueTabProperty_ZA10107791.gif)
-
    5. To define values for the drop-down list, type **Aisle,Center,Window** as the **Possible Values**.
    6. Check **Set the initial value of this field to:**, and type **Aisle** in the next text box as the initial display value. Then click **OK**.