Merge pull request SharePoint#5927 from andrewconnell/issue5926_mdCodeFencing

Update markdown fenced code language errors

Author: andrewconnell

docs/apis/alm-api-for-spfx-add-ins.md

@@ -147,7 +147,7 @@ Add-PnPApp -Path ./sharepoint-solution-package.sppkg
 
 # [Office 365 CLI](#tab/o365cli)
 
-```shell
+```console
 spo app add --filePath ./sharepoint-solution-package.sppkg
 ```
 
@@ -206,7 +206,7 @@ Publish-PnPApp -Identity xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
 
 # [Office 365 CLI](#tab/o365cli)
 
-```shell
+```console
 spo app deploy --id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
 ```
 
@@ -254,7 +254,7 @@ Unpublish-PnPApp -Identity xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
 
 # [Office 365 CLI](#tab/o365cli)
 
-```shell
+```console
 spo app retract --id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
 ```
 
@@ -290,7 +290,7 @@ Remove-PnPApp -Identity xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
 
 # [Office 365 CLI](#tab/o365cli)
 
-```shell
+```console
 spo app remove --id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
 ```
 
@@ -373,7 +373,7 @@ Get-PnPApp
 
 # [Office 365 CLI](#tab/o365cli)
 
-```shell
+```console
 spo app list
 ```
 
@@ -435,7 +435,7 @@ Get-PnPApp -Identity xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
 
 # [Office 365 CLI](#tab/o365cli)
 
-```shell
+```console
 spo app get --id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
 ```
 
@@ -480,7 +480,7 @@ Install-PnPApp -Identity xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
 
 # [Office 365 CLI](#tab/o365cli)
 
-```shell
+```console
 spo app install --id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx --siteUrl <url>
 ```
 
@@ -528,7 +528,7 @@ Update-PnPApp -Identity xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
 
 # [Office 365 CLI](#tab/o365cli)
 
-```shell
+```console
 spo app upgrade --id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx --siteUrl <url>
 ```
 
@@ -575,7 +575,7 @@ Uninstall-PnPApp -Identity xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
 
 # [Office 365 CLI](#tab/o365cli)
 
-```shell
+```console
 spo app uninstall --id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx --siteUrl <url>
 ```
 

docs/apis/export-amr-api.md

@@ -304,7 +304,7 @@ Suggestion:
 
     **Sample source code**
 
-    ```shell
+    ```console
     $site = get-spsite https://test.sharepoint.com  # get site
     $web = get-spweb https://test.sharepoint.com  # get web
     $list = $web.GetList("Shared Documents") # get the document library under this web

docs/general-development/how-to-back-up-and-restore-a-search-service-application-in-sharepoint-using.md

@@ -144,7 +144,7 @@ The following procedures are intended to help developers with creating a backup/
 1. Perform backups of the SSA databases and the index by following these steps:
 1. On the server with the SSA databases, execute the following command at a command line, where  _destination backup folder_ is the full path of the folder for the backup files, _backup log file_ is the full path and name of the backup log file, and _SSA manifest file_ is the path and file name of the SSA manifest file.
 
-    ```shell
+    ```console
     betest.exe /v /b /d "destination backup folder" /s "backup log file" /x "SSA manifest file"
     ```
 
@@ -157,7 +157,7 @@ The following procedures are intended to help developers with creating a backup/
 1. Verify that the file is created.
 1. On each server that has an index component, execute the following at a command line, where  _destination backup folder_ is the full path of the folder for the backup files, _backup log file_ is the full path and name of the backup log file, and _index manifest file_ is the path and file name of the index manifest.
 
-    ```shell
+    ```console
     betest.exe /v /b /d "destination backup folder" /s "backup log file" /x "index manifest file"
     ```
 
@@ -177,7 +177,7 @@ The following procedures are intended to help developers with creating a backup/
 
 1. On the same server, execute the following at a command line to restore the SSA databases, where  _destination backup folder_ is the full path of the folder for the backup files, _backup log file_ is the full path and name of the backup log file, and _SSA manifest file_ is the path and file name of the SSA manifest file.
 
-    ```shell
+    ```console
     betest.exe /v /r /d "destination backup folder" /s "backup log file" /x SSA_manifest_file
     ```
 
@@ -209,7 +209,7 @@ The following procedures are intended to help developers with creating a backup/
 
 1. On the same servers, execute the following at a command line, where  _index manifest file_ is the path and file name of the index manifest that you created in the backup procedure.
 
-    ```shell
+    ```console
     betest.exe /v /r /d "destination backup folder" /s "backup log file" /x "index manifest file"
     ```
 

docs/general-development/site-collection-app-catalog.md

@@ -83,7 +83,7 @@ Add-PnPSiteCollectionAppCatalog -site https://contoso.sharepoint.com/sites/marke
 
 Alternatively, use the `spo site appcatalog add` command if you are using the Office 365 CLI:
 
-```shell
+```console
 spo site appcatalog add --url https://contoso.sharepoint.com/sites/marketing
 ```
 
@@ -111,7 +111,7 @@ Remove-PnPSiteCollectionAppCatalog -site https://contoso.sharepoint.com/sites/ma
 
 Alternatively, use the `spo site appcatalog remove` command if you are using the Office 365 CLI
 
-```shell
+```console
 spo site appcatalog remove --url https://contoso.sharepoint.com/sites/marketing
 ```
 

docs/general-development/social-feed-rest-api-reference-for-sharepoint.md

@@ -3048,7 +3048,7 @@ The following response example represents the unlocked thread. The **Attributes*
 > [!NOTE]
 > The values of thread and post **Id** properties are too long to send in a URL, so you have to send them in the request body. As a result, even read-only operations that are logically **GET** requests must be sent as **POST** requests. For example, to get a thread, you have to send a **POST** request and pass the thread **Id** as an entity in the request body.
 
-```js
+```javascript
 var endpoint = siteUrl + '/_api/social.feed/post';
 var postId = '1.655c70c348374d48839daabc24a360f0.82baa3bdfa2f481a8185802eb9c6c6cd.5d227a6fa3894f0c9dde26876b71d619.0c37852b34d0418e91c62ac25af4be5b.4316bdaa94bf4984be5dfea1ba96954e.26.26.S-1-5-21-2127521184-1604012920-1887927527-66602';
 
@@ -3083,7 +3083,7 @@ $.ajax({
 
 
 
-```js
+```javascript
 var endpoint = <site url> + '/_api/social.feed/my/feed/post';
 var postContent = 'Posted with REST.';
 

docs/solution-guidance/Localize-UI-elements-sample-app-for-SharePoint.md

@@ -119,7 +119,7 @@ The following figure shows the start page for Scenario 1.
 
 The **AddJSLink** method is part of the JavaScriptExtensions.cs file in **OfficeDevPnP.Core**. **AddJSLink** requires that you supply a string representing the identifier to assign to the custom action, and a string containing a semicolon delimited list of URLs to the JavaScript files that you want to add to the host web. Note that this code sample adds a reference to Scripts\scenario1.js, which adds a status bar message to the host web.
 
-```js
+```javascript
 protected void btnSubmit_Click(object sender, EventArgs e)
         {
             var spContext = SharePointContextProvider.Current.GetSharePointContext(Context);
@@ -135,7 +135,7 @@ protected void btnSubmit_Click(object sender, EventArgs e)
 > [!NOTE] 
 > SharePoint uses Minimal Download Strategy to reduce the amount of data the browser downloads when users navigate between pages on a SharePoint site. In scenario1.js, the following code ensures that whether Minimal Download Strategy is used on your SharePoint site, the **RemoteManager_Inject** method is always called to run the JavaScript code to add the status bar message to the host web. For more information, see [Minimal Download Strategy overview](../general-development/minimal-download-strategy-overview.md).
 > 
-> ```js
+> ```javascript
     if ("undefined" != typeof g_MinimalDownload && g_MinimalDownload && (window.___location.pathname.toLowerCase()).endsWith("/_layouts/15/start.aspx") && "undefined" != typeof asyncDeltaManager) {
         // Register script for MDS if possible.
         RegisterModuleInit("scenario1.js", RemoteManager_Inject); //MDS registration
@@ -150,7 +150,7 @@ protected void btnSubmit_Click(object sender, EventArgs e)
 > [!NOTE] 
 > Some JavaScript files may depend on other JavaScript files to be loaded first before they can run and complete successfully. The following code construct from **RemoteManager_Inject** uses the **loadScript** function in scenario1.js to first load jQuery, and then continue running the remaining JavaScript code.
 >
-> ```js
+> ```javascript
     var jQuery = "https://ajax.aspnetcdn.com/ajax/jQuery/jquery-2.0.2.min.js";
         // Load jQuery first, and then continue running the rest of the code.
         loadScript(jQuery, function () {
@@ -195,7 +195,7 @@ Similar to Scenario 1, **btnSubmit\_Click** in scenario2.aspx.cs calls **AddJsLi
     
 - Replaces **my quicklaunch entry** with the value of the **quickLauch\_Scenario2** variable read from the JavaScript resource file.
 
-```js
+```javascript
 function RemoteManager_Inject() {
 
     var jQuery = "https://ajax.aspnetcdn.com/ajax/jQuery/jquery-2.0.2.min.js";

docs/solution-guidance/create-ux-controls-by-using-sharepoint-provider-hosted-add-ins.md

@@ -51,7 +51,7 @@ The Scripts folder of the Core.PeoplePickerWeb project contains app.js and peopl
 
 The app.js file then creates and configures a people picker control.
 
-```js
+```javascript
 //Make a people picker control.
 //1. context = SharePoint Client Context object
 //2. $('#spanAdministrators') = SPAN that will 'host' the people picker control
@@ -70,7 +70,7 @@ peoplePicker.Initialize();
 
 The people picker control queries the **ClientPeoplePickerWebServiceInterface** object in the JSOM library to initiate searches for users whose names match the character strings entered.
 
-```js
+```javascript
 if (searchText.length >= parent.GetMinimalCharactersBeforeSearching()) {
                             resultDisplay = 'Searching...';
                             if (typeof resultsSearching != 'undefined') {
@@ -122,7 +122,7 @@ When you choose the **Setup term store** button, the add-in:
     
 The following code in the **TaxonomyHelper** class verifies that the required languages are enabled, and if they're not, it enables them.
 
-```js
+```javascript
 var languages = new int[] { 1031, 1033, 1036, 1053 };
             Array.ForEach(languages, l => { 
                 if (!termStore.Languages.Contains(l)) 
@@ -142,7 +142,7 @@ termGroup = termStore.CreateGroup("Taxonomy Navigation", groupId);
 
 Finally, the following code in the same **TaxonomyHelper** class creates each new term, along with labels for the German, French, and Swedish languages. It also sets a value for the **\_Sys\_Nav\_SimpleLinkUrl** property, which is equivalent to the **Simple Link or Header** property in the Term Store Management Tool. In this case, the URL for each term points back to the root site.
 
-```js
+```javascript
 var term = termSet.CreateTerm(termName, 1033, Guid.NewGuid());
 term.CreateLabel(termNameGerman, 1031, false);
 term.CreateLabel(termNameFrench, 1036, false);
@@ -156,7 +156,7 @@ Next, the add-in inserts the topnav.js file into the root folder of the host sit
 
 The following code in the topnav.js file uses JSOM to check for the user's preferred language.
 
-```js
+```javascript
 var targetUser = "i:0#.f|membership|" + _spPageContextInfo.userLoginName;
         context = new SP.ClientContext.get_current();
 var peopleManager = new SP.UserProfiles.PeopleManager(context);
@@ -167,7 +167,7 @@ var userProperty = peopleManager.getUserProfilePropertyFor(targetUser, "SPS-MUIL
 
 The add-in then determines whether the user's language preference matches one of the enabled languages. If it finds a match, the following code gets the terms and the associated labels for the user's preferred language.
 
-```js
+```javascript
 while (termEnumerator.moveNext()) {
     var currentTerm = termEnumerator.get_current();
     var label = currentTerm.getDefaultLabel(lcid);
@@ -181,7 +181,7 @@ while (termEnumerator.moveNext()) {
 
 Finally, the following code in the topnav.js file inserts links that contain the terms into the top navigational element of the host site.
 
-```js
+```javascript
 html += "<ul style='margin-top: 0px; margin-bottom: 0px;'>"
         for (var i in termItems) {
             var term = termItems[i];
@@ -230,7 +230,7 @@ The Scripts folder of the Core.TaxonomyPicker project contains app.js and taxono
 
 The app.js file then creates and configures a taxonomy picker control.
 
-```js
+```javascript
 // Load scripts for calling taxonomy APIs.
                     $.getScript(layoutsRoot + 'init.js',
                         function () {
@@ -247,7 +247,7 @@ The app.js file then creates and configures a taxonomy picker control.
 
 The taxonomy picker control uses the following code to open a **TaxonomySession** instance in the JSOM to load all the terms from the term store.
 
-```js
+```javascript
 // Get the taxonomy session by using CSOM.
             var taxSession = SP.Taxonomy.TaxonomySession.getTaxonomySession(spContext);
             //Use the default term store...this could be extended here to support additional term stores.