Fixup front matter build errors & markdown formatting

- address warnings on the MSDocs build report

Author: andrewconnell

docs/apis/onenote-migration-service.md

@@ -1,31 +1,32 @@
 ---
 title: Migrating OneNote folders
+ms.date: 12/05/2020
 ms.author: jhendr
 author: JoanneHendrickson
 manager: pamgreen
 audience: Dev
 ms.topic: article
 ms.service: sharepoint-online
 localization_priority: Priority
-ms.collection: 
+ms.collection:
 - SPMigration
 - M365-collaboration
 search.appverid: MET150
 description: "Migrating OneNote folders using the SPO OneNote converting service"
 ---
 # Migrating OneNote folders
 
-When bringing **OneNote** notebooks into SharePoint Online (SPO) from outside the service, you are required to convert the file. OneNote files need to be located within a correctly tagged NoteBook folder before the OneNote content is accessible via the modern APIs.  
+When bringing **OneNote** notebooks into SharePoint Online (SPO) from outside the service, you are required to convert the file. OneNote files need to be located within a correctly tagged NoteBook folder before the OneNote content is accessible via the modern APIs.
 
 There is now a OneNote converting service in SPO that lets you mark the **OneNote** notebooks that are being migrated to be converted.
 
 ## Example
 
-The following example shows SPMT using the SPO OneNote converting service, which is running in SPO background.  
+The following example shows SPMT using the SPO OneNote converting service, which is running in SPO background.
 
 ![OneNote migration process](../images/onenote-migration-flow.png)
 
-## Algorithm for checking whether to mark the folder as OneNote folder 
+## Algorithm for checking whether to mark the folder as OneNote folder
 
 For a normal folder, we use the following algorithm to determine whether it should be marked as **OneNote** folder or not.
 
@@ -43,11 +44,11 @@ If the folder does not contain one .onetoc2 file, it is NOT considered to be a *
 
 The CSOM will mark the `HTML_x0020_File_x0020_Type` field of the folder on SharePoint Online as `OneNote.Notebook`.
 
-The marking must be done ONLY on the top-level OneNote folder candidate in the file hierarchy. 
+The marking must be done ONLY on the top-level OneNote folder candidate in the file hierarchy.
 
 Sample code:
 
-```c#
+```csharp
 List list = context.web.Lists.GetById({listid});
 ListItem item = list.GetItemByUniqueId({itemid});
 Item[“HTML_x0020_File_x0020_Type”] = “OneNote.Notebook”;

docs/apis/sharepoint-rest-graph.md

@@ -1,8 +1,8 @@
 ---
 title: Operations using SharePoint REST v2 (Microsoft Graph) endpoints
 description: Perform basic create, read, update, and delete (CRUD) operations with the SharePoint v2 REST interface.
-ms.date: 9/10/2019
-ms.prod: sharepoint online
+ms.date: 12/05/2020
+ms.service: sharepoint-online
 localization_priority: Priority
 ---
 

docs/apis/spod-copy-move-api.md

@@ -1,6 +1,6 @@
 ---
 title: Microsoft 365 Copy and Move API (CreateCopyJobs)
-ms.date: 06/02/2020
+ms.date: 12/05/2020
 ms.author: jhendr
 author: JoanneHendrickson
 manager: pamgreen
@@ -10,7 +10,7 @@ f1.keywords:
 ms.topic: article
 ms.service: sharepoint-online
 localization_priority: Priority
-ms.collection: 
+ms.collection:
 - SPMigration
 - M365-collaboration
 search.appverid: MET150
@@ -19,27 +19,26 @@ description: "Microsoft 365 Copy and Move API (CreateCopyJobs)"
 # Microsoft 365 Copy and Move API (CreateCopyJobs)
 
 >[!IMPORTANT]
->SharePoint & OneDrive Copy and Move API replaces the CreateCopyJob API.  The CreateCopyJob API has been deprecated. 
+>SharePoint & OneDrive Copy and Move API replaces the CreateCopyJob API.  The CreateCopyJob API has been deprecated.
 
+The following API is based on the use of the SharePoint Client Side Object Model (CSOM). We recommend using [NuGet](https://www.nuget.org/) packages when you reference CSOM in your solution.
 
-The following API is based on the use of the SharePoint Client Side Object Model (CSOM). We recommend using [NuGet](https://www.nuget.org/) packages when you reference CSOM in your solution. 
-
-You can find the latest version of the SharePoint Online CSOM package from the [NuGet library](https://www.nuget.org/) using the ID *Microsoft.SharePointOnline.CSOM*. 
+You can find the latest version of the SharePoint Online CSOM package from the [NuGet library](https://www.nuget.org/) using the ID *Microsoft.SharePointOnline.CSOM*.
 
 >[!IMPORTANT]
 >Learn more about [limitations](#limitations) of this API before you begin.
 
-
 ## Method
 
 ### CreateCopyJobs
 
-This method creates a new copy or move job that lets you  copy or move a file or folder from one site in SharePoint, OneDrive, or Teams, to another site. 
+This method creates a new copy or move job that lets you  copy or move a file or folder from one site in SharePoint, OneDrive, or Teams, to another site.
 
 #### Syntax
 
-`public List<SPCopyMigrationInfo> CreateCopyJobs(Uri[] exportObjectUris, Uri destinationUri, SPCopyMigrationOptions options)`
-
+```csharp
+public List<SPCopyMigrationInfo> CreateCopyJobs(Uri[] exportObjectUris, Uri destinationUri, SPCopyMigrationOptions options)
+```
 
 #### Parameters
 
@@ -50,66 +49,76 @@ This method creates a new copy or move job that lets you  copy or move a file or
 
 ##### SPCopyMigrationOptions
 
-
-`public bool IsMoveMode { get; set; }`
+```csharp
+public bool IsMoveMode { get; set; }
+```
 
 >[!IMPORTANT]
 >By default, this is set to copy. For a move operation, set this parameter to true.
 
-
-`public bool IgnoreVersionHistory { get; set; }`
+```csharp
+public bool IgnoreVersionHistory { get; set; }
+```
 
 If not specified, the version history will be ignored and not moved to the destination.
 
-
-`public bool AllowSchemaMismatch { get; set; }`
+```csharp
+public bool AllowSchemaMismatch { get; set; }
+```
 
 This allows the item to move even if the target has a mismatched schema definition from the source list.
- 
 
-`public bool AllowSmallerVersionLimitOnDestination { get; set; }`
+```csharp
+public bool AllowSmallerVersionLimitOnDestination { get; set; }
+```
 
 This allows the move to take place if the target file has older version. By default it’s disallowed to prevent data loss.
 
-
-`public SPMigrationNameConflictBehavior NameConflictBehavior { get; set; }`
+```csharp
+public SPMigrationNameConflictBehavior NameConflictBehavior { get; set; }
+```
 
 If a name conflict occurs at the target site, the default reports a failure.
 
+```csharp
+public bool IncludeItemPermissions { get; set; }
+```
 
-`public bool IncludeItemPermissions { get; set; }`
-
-Reserved for interal use only.
-
+Reserved for internal use only.
 
-`public SPMoveAndShareFileInfo MoveAndShareFileInfo { get; set; }`
+```csharp
+public SPMoveAndShareFileInfo MoveAndShareFileInfo { get; set; }
+```
 
 Reserved for internal use only.
 
-
-`public bool BypassSharedLock { get; set; }`
+```csharp
+public bool BypassSharedLock { get; set; }
+```
 
 This indicates whether a file with a share lock can still be moved in a move job. If you want to move a file that is locked, you need to set this.
 
-
-`public string[] ClientEtags { get; set; }`
+```csharp
+public string[] ClientEtags { get; set; }
+```
 
 If set, and the source eTag doesn’t match the eTag specified, the copy and move won’t take place. If left NULL, no check will take place.
 
+```csharp
+public bool MoveButKeepSource { get; set; }
+```
 
-`public bool MoveButKeepSource { get; set; }`
-
-Once set, this move operation is similar to copy. The file will move to destination, but the source content will not be deleted. If set, this will make a copy with the version history and preserve the original metadata. No source item deletions occurs at the end. 
+Once set, this move operation is similar to copy. The file will move to destination, but the source content will not be deleted. If set, this will make a copy with the version history and preserve the original metadata. No source item deletions occurs at the end.
 
 >[!NOTE]
 >This is not like the normal copy, which only copies the most recent major version and doesn't maintain all the metadata.
 
-
-`public bool ExcludeChildren { get; set; }`
+```csharp
+public bool ExcludeChildren { get; set; }
+```
 
 For this operation, only the root level folder of the URL is copied. The sub-folders or files within the folder will not be moved or copied.
 
-
 ### Output
 
 |Output parameter|Description|
@@ -119,20 +128,18 @@ For this operation, only the root level folder of the URL is copied. The sub-fol
 |JobQueueUri|URL for accessing Azure queue used for returning notification of copy and move process|
 |EncryptionKey|	AES256CBC encryption key used to decrypt messages from job/manifest queue|
 
+```csharp
+public Uri JobQueueUri { get; set; }
+```
 
-`public Uri JobQueueUri { get; set; }`
+The reporting features are the same as they are for CreateMigrationJob. Logging tracks the status of the createCopyJobs. By default, blob queue permissions and settings are set to "all access”. It gives the job status as follows: job start, job end, and job error information.
 
-The reporting features are the same as they are for CreateMigrationJob. Logging tracks the status of the createCopyJobs. By default, blob queue permissions and settings are set to "all access”. It gives the job status as follows: job start, job end, and job error information. 
+## Limitations
 
-
-## Limitations 
 Currently, the following limitations are:
 
 |What|Limitation|
 |:-----|:-----|
 |File size|	A file must be less than 2 GB.|
 |Number of items|	No more than 30,000 items in a job.|
 |Total size of job|	Job size not to exceed 100 GB.|
-
-
-

docs/scenario-guidance/Enterprise-Content-Management.md

@@ -1,12 +1,11 @@
 ---
 title: Enterprise Content Management
-ms.date: 3/9/2015
+ms.date: 12/05/2020
 ms.audience: ITPro
 ms.topic: article
 ms.prod: sharepoint
 author: vesajuvonen
 ms.author: vesaj
-ms.topic: sharepoint
 localization_priority: Normal
 ms.assetid: 6f2336fc-0cdd-6596-fdb7-45607006b2c8
 description: "Last modified: March 09, 2015"

docs/schema/file-element.md

@@ -1,9 +1,6 @@
 ---
 title: "File element"
-ms.author: kdeding
-author: kdeding
-manager: soliver
-ms.date: 3/9/2015
+ms.date: 12/05/2020
 ms.audience: Developer
 ms.topic: reference
 ms.prod: sharepoint
@@ -13,15 +10,15 @@ api_name:
 api_type:
 - schema
 ms.assetid: db86d800-9f68-43cc-b7d5-3bd76537dfde
-description: Specifies a file to include within a module in a site definition configuration or Web template configuration. 
+description: Specifies a file to include within a module in a site definition configuration or Web template configuration.
 ---
 
 # File element
 
 **Applies to:** Lync 2013 | Lync Server 2013 | SharePoint 2016 | SharePoint Foundation 2013 | SharePoint Online | SharePoint Server 2013
-  
-Specifies a file to include within a module in a site definition configuration or Web template configuration. 
-  
+
+Specifies a file to include within a module in a site definition configuration or Web template configuration.
+
 ```XML
 <File
   DocumentTemplateForList = "Text"  DoGUIDFixUp = "TRUE" | "FALSE"
@@ -52,7 +49,7 @@ The following sections describe attributes, child elements, and parent elements.
 |**Path** <br/> | Optional **Text**. Specifies the physical path to the file relative to %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\15\TEMPLATE\SiteTemplates\ _Site_Definition_ for Onet.xml files. Specifies the physical path to the file relative to %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\15\TEMPLATE\FEATURES\  _Feature_Name_ for Feature.xml files. Can only contain the following characters:  <br/>  alphanumeric  <br/>  hyphen (**-**)  <br/>  underscore (**_**)  <br/>  period (**.**)  <br/>  space ( )  <br/> |
 |**Type** <br/> |Optional **Text**. Specifies that the file be cached in memory on the front-end server. Possible values include **Ghostable** and **GhostableInLibrary**. Both values specify that the file will be cached, but **GhostableInLibrary** specifies that the file will be cached as part of a list whose base type is **Document** **Library**.<br/><br/>For example, when changes are made to a home page through the user interface (UI), only the differences between the original page definition and the new page are stored in the database. The default.aspx is cached in memory, in addition to the schema files. The HTML page that is displayed in the browser is constructed through the combined page definition that results from the original page definition that is cached in memory and from changes that are stored in the database.  <br/> |
 |**Url** <br/> | Required **Text**. Specifies the virtual path for the file. If the **Name** attribute is specified, its value is used for the virtual path. If **Path** is not specified, the value of **Url** is used for the physical path. Cannot contain the following characters:  <br/>  \"  <br/>  #  <br/>  %  <br/>  &amp;  <br/>  \*  <br/>  :  <br/>  \<  <br/>  \>  <br/>  ?  <br/>  \\  <br/>  {  <br/>  }  <br/>  |  <br/>  ~  <br/>  \x7f  <br/> |
-   
+
 ### Child elements
 
 - [AllUsersWebPart](alluserswebpart-element-site.md)
@@ -61,18 +58,16 @@ The following sections describe attributes, child elements, and parent elements.
 - [Property](property-element-sitemodule.md)
 - [View](view-element-site.md)
 - [WebPartConnection](webpartconnection-element-site.md)
-   
+
 ### Parent elements
 
 - [Module](module-element-site.md)
-   
+
 ### Occurrences
 
 - Minimum: 0
-- Maximum: Unbounded   
-   
-### Remarks
+- Maximum: Unbounded
 
-For an example that uses the **File** element, see [Module element (Site)](module-element-site.md).  
-  
+### Remarks
 
+For an example that uses the **File** element, see [Module element (Site)](module-element-site.md).