Fixed some markup errors.

Author: DennisLee-DennisLee

docs/vsto/custom-xml-parts-overview.md

@@ -70,7 +70,7 @@ ms.workload:
 ### Modify XML parts without starting the Office application  
  You can add or modify a custom XML part without starting Excel, PowerPoint, or Word. This is useful if you want to work with XML data in a document on a computer that does not have Microsoft Office applications installed, such as a server.  
 
- To add a custom XML part without starting Microsoft Office, use classes in the Open XML SDK. These classes are designed to provide access to Open XML content that is specific to Office documents. For example, to add a custom XML part to an Excel workbook, you use the <xref:DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.AddNewPart%2A?displayProperty=fullName> method of a <xref:DocumentFormat.OpenXml.Packaging.WorkbookPart> object. For more information, see [Open XML SDK](/office/open-xml/open-xml-sdk).  
+ To add a custom XML part without starting Microsoft Office, use classes in the Open XML SDK. These classes are designed to provide access to Open XML content that is specific to Office documents. For example, to add a custom XML part to an Excel workbook, you use the <xref:DocumentFormat.OpenXml.Packaging.OpenXmlPartContainer.AddNewPart%2A> method of a <xref:DocumentFormat.OpenXml.Packaging.WorkbookPart> object. For more information, see [Open XML SDK](/office/open-xml/open-xml-sdk).  
 
 ## Bind custom XML parts to Word content controls  
  You can bind content controls in a Word solution to elements in a custom XML part. When a content control is bound to a custom XML part, the data in the custom XML part is displayed in the user interface (UI) of the content control. If a user edits text in the control, the corresponding XML element is automatically updated. Similarly, if element values in the custom XML parts are changed, the content controls that are bound to the XML elements display the new data. For more information, see [Content controls](../vsto/content-controls.md).  

docs/vsto/how-autosave-impacts-office-solutions.md

@@ -20,7 +20,7 @@ ms.workload:
 
 AutoSave is a feature for Excel, PowerPoint, and Word that automatically and continuously saves your edits. If the feature is turned off, you must save files manually to keep your changes. You may need to adjust your Office solution so that it works smoothly even while AutoSave is on. For details, see [How AutoSave impacts add-ins and macros](/office/vba/library-reference/concepts/how-autosave-impacts-addins-and-macros). For more information about AutoSave in general, see [What is AutoSave?](https://support.office.com/en-US/article/What-is-AutoSave-6d6bd723-ebfd-4e40-b5f6-ae6e8088f7a5).
 
-> ![NOTE]
+> [!NOTE]
 > AutoSave for Windows Desktop Word, Excel, and PowerPoint was introduced in 2017 and is currently available for Office365 subscribers. If you bought a perpetual license to Office 2016 or earlier, you don't currently have access to the coauthoring feature. (Excel Online, Excel for Android, Excel for iOS, and Excel Mobile in the Windows Store do support this feature, though.)
 
 ## See also

docs/vsto/writing-code-in-office-solutions.md

@@ -56,7 +56,7 @@ ms.workload:
  The Office PIAs are not required on end-user computers to run Office solutions that target the [!INCLUDE[net_v40_short](../sharepoint/includes/net-v40-short-md.md)] or later. For more information, see [Design and create Office solutions](../vsto/designing-and-creating-office-solutions.md).  
 
 ### Use types in primary interop assemblies  
- The Office PIAs contain a combination of types that expose the object model of the Office applications and additional infrastructure types that are not intended to be used directly in your code. For an overview of the types in the Office PIAs, see [Overview of classes and interfaces in the Office primary interop assemblies](/previous-versions/office/office-12//ms247299(v=office.12)).  
+ The Office PIAs contain a combination of types that expose the object model of the Office applications and additional infrastructure types that are not intended to be used directly in your code. For an overview of the types in the Office PIAs, see [Overview of classes and interfaces in the Office primary interop assemblies](/previous-versions/office/office-12/ms247299\(v\=office.12\)).  
 
  Because the types in the Office PIAs correspond to types in the COM-based object models, the way you use these types is often different from other managed types. For example, the way you call methods that have optional parameters in an Office primary interop assembly depends on the programming language you are using in your project. For more information, see the following topics: