Merge pull request SharePoint#7121 from andrewconnell/msdocsrules_misc

Update fenced code formatting to match MSDOCS supported types

Author: andrewconnell

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

@@ -28,7 +28,7 @@ ALM APIs can be used to perform exactly the same operations that are available f
 ALM APIs are supported for the tenant-scoped site collections and [site collection app catalog](../general-development/site-collection-app-catalog.md). Use the corresponding app catalog's URL to target a specific app catalog. You must first enabled a site collection app catalog before targeting it with the actions documented on this page.
 
 > [!IMPORTANT]
-> Tenant-scoped permissions which require [tenant administrative approval](https://docs.microsoft.com/sharepoint/dev/solution-guidance/how-to-provide-add-in-app-only-tenant-administrative-permissions-in-sharepoint-online) are not supported with the ALM APIs.
+> Tenant-scoped permissions which require [tenant administrative permissions](../solution-guidance/how-to-provide-add-in-app-only-tenant-administrative-permissions-in-sharepoint-online.md) are not supported with the ALM APIs.
 
 ## Options for working with ALM APIs
 
@@ -42,12 +42,12 @@ The app catalog must be included in all HTTP requests when using the REST API as
 
 For example:
 
-|      Scope      |                                            Endpoint                                            |
-| :-------------- | :--------------------------------------------------------------------------------------------- |
-| tenant          | **https://contoso.sharepoint.com/sites/AppCatalog/_api/web/tenantappcatalog/{command}**        |
-| site collection | **https://contoso.sharepoint.com/sites/Marketing/_api/web/sitecollectionappcatalog/{command}** |
+|      Scope      |                                           Endpoint                                           |
+| :-------------- | :------------------------------------------------------------------------------------------- |
+| tenant          | `https://contoso.sharepoint.com/sites/AppCatalog/_api/web/tenantappcatalog/{command}`        |
+| site collection | `https://contoso.sharepoint.com/sites/Marketing/_api/web/sitecollectionappcatalog/{command}` |
 
-- when targeting the tenant app catalog located at **https://contoso.sharepoint.com/sites/AppCatalog**, the endpoint would be **
+- when targeting the tenant app catalog located at `https://contoso.sharepoint.com/sites/AppCatalog`, the endpoint would be **
 
 Learn more here: [SharePoint REST API](../sp-add-ins/get-to-know-the-sharepoint-rest-service.md)
 
@@ -57,7 +57,7 @@ The PnP CSOM implements the ALM APIs by calling the SharePoint REST API.
 
 Before using any of the ALM APIs in PnP CSOM, you need to obtain an authenticated client context using the [Microsoft.SharePointOnline.CSOM](https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM). Then use the authenticated client context to get an instance of the PnP CSOM's **AppManager** object to call the ALM commands:
 
-```cs
+```csharp
 using Microsoft.SharePoint.Client;
 using OfficeDevPnP.Core.ALM;
 
@@ -72,7 +72,7 @@ using (var context = new ClientContext(webURL)) {
 
 In all PnP Core methods, it's assumed the request targets the tenant app catalog in the tenant you connect to using the SharePoint CSOM `ClientContext` object. you can override the scope of all commands with an optional scope argument, for example
 
-```cs
+```csharp
 appManager.Install('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx', AppCatalogScope.Site);
 ```
 
@@ -128,7 +128,7 @@ Byte array of the file
 
 # [PnP CSOM](#tab/pnpcsom)
 
-```cs
+```csharp
 // read file
 var filePath = "c:\path\to\file\sharepoint-solution-package.sppkg";
 // get an instance of the PnP CSOM's AppManager as shown above
@@ -190,7 +190,7 @@ POST /_api/web/{scope}appcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-
 
 # [PnP CSOM](#tab/pnpcsom)
 
-```cs
+```csharp
 appManager.Deploy('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')
 ```
 
@@ -237,7 +237,7 @@ POST /_api/web/{scope}appcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-
 
 # [PnP CSOM](#tab/pnpcsom)
 
-```cs
+```csharp
 // get an app package
 appManager.Retract('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')
 ```
@@ -274,7 +274,7 @@ POST /_api/web/{scope}appcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-
 
 # [PnP CSOM](#tab/pnpcsom)
 
-```cs
+```csharp
 appManager.Remove('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')
 ```
 
@@ -357,7 +357,7 @@ GET /_api/web/{scope}appcatalog/AvailableApps
 
 # [PnP CSOM](#tab/pnpcsom)
 
-```cs
+```csharp
 var allAppPackages = appManager.GetAvailable();
 ```
 
@@ -419,7 +419,7 @@ GET /_api/web/{scope}appcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-x
 
 # [PnP CSOM](#tab/pnpcsom)
 
-```cs
+```csharp
 var appPackage = appManager.GetAvailable('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx');
 ```
 
@@ -463,7 +463,7 @@ POST /_api/web/{scope}appcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-
 
 # [PnP CSOM](#tab/pnpcsom)
 
-```cs
+```csharp
 // get an app package
 appManager.Install('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')
 ```
@@ -508,7 +508,7 @@ POST /_api/web/{scope}appcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-
 
 # [PnP CSOM](#tab/pnpcsom)
 
-```cs
+```csharp
 // get an app package
 var appPackage = appManager.GetAvailable('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx');
 if (appPackage.CanUpgrade) {
@@ -559,7 +559,7 @@ POST /_api/web/{scope}appcatalog/AvailableApps/GetById('xxxxxxxx-xxxx-xxxx-xxxx-
 
 # [PnP CSOM](#tab/pnpcsom)
 
-```cs
+```csharp
 appManager.Uninstall('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')
 ```
 
@@ -603,7 +603,7 @@ POST /_api/web/{scope}appcatalog/SyncSolutionToTeams(id=xxxxx)
 
 # [PnP CSOM](#tab/pnpcsom)
 
-```cs
+```csharp
 appManager.SyncToTeams('xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx')
 ```
 

docs/apis/webhooks/get-started-webhooks.md

@@ -100,7 +100,7 @@ Each notification generated by the service is serialized into a **webhookNotific
 
 4. Add the following code to the body of the **SPWebhookNotification** class:
 
-	```cs
+	```csharp
 	public string SubscriptionId { get; set; }
 
 	public string ClientState { get; set; }
@@ -128,7 +128,7 @@ Because multiple notifications can be submitted to your webhook receiver in a si
 
 4. Add the following code to the body of the **SPWebhookContent** class:
 
-	```cs
+	```csharp
 	 public List<SPWebhookNotification> Value { get; set; }
 	```
 
@@ -162,7 +162,7 @@ A trace writer is required, so you must add a trace writer to the controller con
 
 3. Add the following line inside the **Register** method:
 
-	```cs
+	```csharp
 	config.EnableSystemDiagnosticsTracing();
 	```
 
@@ -182,7 +182,7 @@ Now build the webhook receiver controller that handles the incoming requests fro
 
 6. Replace the `using` statements with the following code:
 
-	```cs
+	```csharp
 	using Newtonsoft.Json;
 	using SPWebhooksReceiver.Models;
 	using System.Collections.Generic;
@@ -198,7 +198,7 @@ Now build the webhook receiver controller that handles the incoming requests fro
 
 7. Replace the code in the **SPWebhookController** class with the following code:
 
-	```cs
+	```csharp
 	[HttpPost]
 	public HttpResponseMessage HandleRequest()
 	{
@@ -432,7 +432,7 @@ Now that you have the required information, construct the query and the request
 
 	The trace indicates that the webhook received initially received a validation request. If you look at the code, you'll see that it returns the validation token immediately so that SharePoint can validate the request:
 
-	```cs
+	```csharp
 	if (queryStringParams.AllKeys.Contains("validationtoken"))
 	{
 		httpResponse = new HttpResponseMessage(HttpStatusCode.OK);
@@ -496,7 +496,7 @@ Now add a file to the Documents library and test if you get a notification from
 
 2. In the **SPWebhookController**, place a breakpoint on the following line of code:
 
-	```cs
+	```csharp
 	var requestContent = Request.Content.ReadAsStringAsync().Result;
 	```
 

docs/apis/webhooks/sharepoint-webhooks-using-azure-functions.md

@@ -63,7 +63,7 @@ In our case, we want this Azure Function to behave as a SharePoint webhook servi
 
 You can achieve this by replacing the default code with the following code:
 
-```cs
+```csharp
 #r "Newtonsoft.Json"
 
 using System.Net;

docs/apis/webhooks/webhooks-reference-implementation.md

@@ -61,7 +61,7 @@ After you've requested SharePoint to add your webhook, SharePoint validates that
 
 Take a look at the reference implementation, and you'll see that all webhook CRUD operations are consolidated in the [WebHookManager](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/SharePoint.WebHooks.Common/WebHookManager.cs) class of the **SharePoint.WebHooks.Common** project. Adding a webhook is done by using the **AddListWebHookAsync** method:
 
-```cs
+```csharp
 /// <summary>
 /// This method adds a webhook to a SharePoint list. Note that you need your webhook endpoint being passed into this method to be up and running and reachable from the internet
 /// </summary>
@@ -81,7 +81,7 @@ public async Task<SubscriptionModel> AddListWebHookAsync(string siteUrl, string
 
 When making a call to SharePoint, you need to provide authentication information, and in this case you're using a **Bearer** authentication header with an **access token**. To obtain the access token, intercept the token via an **ExecutingWebRequest** event handler:
 
-```cs
+```csharp
 ClientContext cc = null;
 
 // Create SharePoint ClientContext object...

docs/declarative-customization/column-formatting.md

@@ -1063,7 +1063,7 @@ An optional property that specifies the text content of the element specified by
 
 An optional property that specifies style attributes to apply to the element specified by `elmType`. This is an object with name-value pairs that correspond to CSS names and values. The values of each property in the style object can either be a string (including special strings) or an Expression object. The following style attributes are allowed.
 
-```JS
+```javascript
 'background-color'
 'fill'
 'background-image'