Merge pull request SharePoint#8927 from andrewconnell/content-update/markdownfixup

🧼 cleanup markdown numbered list

Author: andrewconnell

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

@@ -133,14 +133,14 @@ The following diagram describes the complete end-to-end webhook flow.
 ![Webhooks reference implementation end-to-end flow](../../images/webhook-sample-end-to-end-flow.png)
 
 1. Your application creates a webhook subscription. When it does, it gets the current **changeToken** from the list it created the webhook for.
-2. Your application persists the **changeToken** in a persistent storage, such as SQL Azure in this case.
-3. A change in SharePoint occurs, and SharePoint calls your service endpoint.
-4. Your service endpoint serializes the notification request and stores it in a storage queue.
-5. Your web job sees the message in the queue and starts your message processing logic.
-6. Your message processing logic retrieves the last used change token from the persistent storage.
-7. Your message processing logic uses the `GetChanges()`API to determine what changed.
-8. The returned changes are processed and now your application performs what it needs to do based on the changes.
-9. Finally, the application persists the last retrieved **changeToken** so that next time it does not receive changes that were already processed.
+1. Your application persists the **changeToken** in a persistent storage, such as SQL Azure in this case.
+1. A change in SharePoint occurs, and SharePoint calls your service endpoint.
+1. Your service endpoint serializes the notification request and stores it in a storage queue.
+1. Your web job sees the message in the queue and starts your message processing logic.
+1. Your message processing logic retrieves the last used change token from the persistent storage.
+1. Your message processing logic uses the `GetChanges()`API to determine what changed.
+1. The returned changes are processed and now your application performs what it needs to do based on the changes.
+1. Finally, the application persists the last retrieved **changeToken** so that next time it does not receive changes that were already processed.
 
 ## Work with webhook renewal
 
@@ -157,7 +157,7 @@ Create a web job that on a weekly basis reads all the subscription IDs from the
 > [!NOTE]
 > This web job is not part of this reference implementation.
 
-The actual renewal of a SharePoint list webhook can be done by using a [`PATCH /_api/web/lists('list-id')/subscriptions(‘subscriptionID’)`](./lists/update-subscription.md) REST call.
+The actual renewal of a SharePoint list webhook can be done by using a `[PATCH /_api/web/lists('list-id')/subscriptions(‘subscriptionID’)](./lists/update-subscription.md)` REST call.
 
 In the reference implementation, updating of webhooks is implemented 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.
 

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

@@ -123,13 +123,13 @@ Now that you've added a site script and site template, you can use it to create
 1. Go to the home page of the SharePoint site that you are using for development.
 1. Choose **Create site**.
 1. Choose the type of site you need to use. SharePoint will create a team site using the Microsoft **Team collaboration template** or a communication site using the Microsoft **Topic** template unless another custom site template is set as default.
-2. Choose **Next**.
-4. In **Site name**, enter a name for the new site **Customer order tracking**.
-7. Choose **Finish**.
-5. Next, go to **Settings** and select **Apply a site template**.
-5. Select the site template you just created.
-8. Once applied, your new template will display under the tab in the template viewer titled **From your organization.**
-9. When the new template has been applied, you will see the custom list on the page.
+1. Choose **Next**.
+1. In **Site name**, enter a name for the new site **Customer order tracking**.
+1. Choose **Finish**.
+1. Next, go to **Settings** and select **Apply a site template**.
+1. Select the site template you just created.
+1. Once applied, your new template will display under the tab in the template viewer titled **From your organization.**
+1. When the new template has been applied, you will see the custom list on the page.
 
 ### Apply to an existing site
 
@@ -142,9 +142,9 @@ You can apply templates to existing site collections in bulk by using the [Invok
 1. Group-connected team sites
 1. Team sites that not connected to a Microsoft 365 group
 1. Communication sites
-2. Channel sites
-3. Classic team sites
-4. Classic publishing sites
+1. Channel sites
+1. Classic team sites
+1. Classic publishing sites
 
 The REST API to apply a site template to an existing site collection is **ApplySiteDesign**.
 

docs/declarative-customization/get-started-create-site-design.md

@@ -16,10 +16,8 @@ Use the CLI for Microsoft 365 to create, retrieve, update, and remove site desig
 To run the CLI for Microsoft 365 commands, you'll need to do the following:
 
 1. Download and install [NodeJS LTS version](https://nodejs.org/en/)
-
-2. Follow the instructions at [Installing the CLI](https://pnp.github.io/cli-microsoft365/user-guide/installing-cli/) to install the CLI for Microsoft 365 on your machine
-
-3. Follow the instructions at [Logging in to Office 365](https://pnp.github.io/cli-microsoft365/user-guide/connecting-office-365/) to connect to your SharePoint tenant.
+1. Follow the instructions at [Installing the CLI](https://pnp.github.io/cli-microsoft365/user-guide/installing-cli/) to install the CLI for Microsoft 365 on your machine
+1. Follow the instructions at [Logging in to Office 365](https://pnp.github.io/cli-microsoft365/user-guide/connecting-office-365/) to connect to your SharePoint tenant.
 
 To verify your setup and connection, try using the [sitedesign list](https://pnp.github.io/cli-microsoft365/cmd/spo/sitedesign/sitedesign-list) command to read the current list of site designs. If the cmdlet runs and returns with no errors, you're ready to proceed.
 

docs/declarative-customization/site-design-o365cli.md

@@ -32,23 +32,21 @@ Site templates can be used each time a new site is created to apply a consistent
 You create site templates and register them in SharePoint to one of the modern template sites: the Team site or the Communication site. You can see how this works in the following steps.
 
 1. Go to the SharePoint start page on your developer tenant.
-
-2. Choose **Create site**.
+1. Choose **Create site**.
 
    You'll see the two modern template sites: **Team site** and **Communication site**.
 
-3. Choose the type of site needed.
+1. Choose the type of site needed.
 
-- SharePoint will automatically create a communication site using the **Topic** site template.
-- Had you chosen the default Team site, SharePoint will create a new site using the **Team collaboration** template.
+    - SharePoint will automatically create a communication site using the **Topic** site template.
+    - Had you chosen the default Team site, SharePoint will create a new site using the **Team collaboration** template.
 
-For more information about how you can change the default site templates, see [Customize a default site template](customize-default-site-design.md).
+    For more information about how you can change the default site templates, see [Customize a default site template](customize-default-site-design.md).
 
-4. Navigate to the **Settings** icon, and select **Apply site template** to review Microsoft-provided site templates based on the type of site you chose in step three.
+1. Navigate to the **Settings** icon, and select **Apply site template** to review Microsoft-provided site templates based on the type of site you chose in step three.
 
 When a site template is selected, SharePoint creates the new site, and runs site scripts for the site template. The site scripts provide the details for the template such as creating new lists or applying a theme. These script actions are run in the background. When the scripts are complete the page will refresh to display the site script details.
 
-
 > [!NOTE]
 > Site templates can now be applied to previously created modern site collections. For more information, see the [REST API](site-design-rest-api.md) and [PowerShell](site-design-powershell.md) articles.
 
@@ -109,8 +107,6 @@ The following example is a script that has two top-level actions. First, it appl
 }
 ```
 
-<br/>
-
 Each action in a site script is specified by a **verb** value in the JSON. In the previous script, the first action is specified by the **applyTheme** verb. Next, the **createSPList** verb creates the list. Notice that the **createSPList** verb contains its own set of verbs that run additional actions on only the list.
 
 **Available actions include:**
@@ -130,6 +126,7 @@ Each action in a site script is specified by a **verb** value in the JSON. In th
 For a complete list of available actions and their parameters, see the [JSON schema](site-design-json-schema.md).
 
 > [!NOTE]
+>
 > - Actions marked with ** are automatically blocked for [channel sites](/sharepoint/teams-connected-sites).
 > - For libraries and lists, use the PowerShell command [Get-SPOSiteScriptFromList](/powershell/module/sharepoint-online/Get-SPOSiteScriptFromList) to create the site script syntax from an existing SharePoint list.
 
@@ -166,109 +163,36 @@ C:\> Add-SPOSiteDesign `
   -Description "Creates customer list and applies standard theme"
 ```
 
-<!--
-```javascript
-var site_script = {
-  "$schema": "schema.json",
-  "actions": [
-    {
-      "verb": "applyTheme",
-      "themeName": "Contoso Explorers"
-    },
-    {
-      "verb": "createSPList",
-      "listName": "Customer Tracking",
-      "templateType": 100,
-      "subactions": [
-        {
-          "verb": "SetDescription",
-          "description": "List of Customers and Orders"
-        },
-        {
-          "verb": "addSPField",
-          "fieldType": "Text",
-          "displayName": "Customer Name",
-          "isRequired": false,
-          "addToDefaultView": true
-        },
-        {
-          "verb": "addSPField",
-          "fieldType": "Number",
-          "displayName": "Requisition Total",
-          "addToDefaultView": true,
-          "isRequired": true
-        },
-        {
-          "verb": "addSPField",
-          "fieldType": "User",
-          "displayName": "Contact",
-          "addToDefaultView": true,
-          "isRequired": true
-        },
-        {
-          "verb": "addSPField",
-          "fieldType": "Note",
-          "displayName": "Meeting Notes",
-          "isRequired": false
-        }
-      ]
-    }
-  ],
-  "bindata": { },
-  "version": 1
-};
-
-RestRequest("/_api/Microsoft.SharePoint.Utilities.WebTemplateExtensions.SiteScriptUtility.CreateSiteScript(Title=@title,Description=@desc)?@title='Contoso theme and list'&@desc='this script creates a list named customer tracking and sets the contoso explorers company theme'", site_script);
-
-RestRequest("/_api/Microsoft.SharePoint.Utilities.WebTemplateExtensions.SiteScriptUtility.CreateSiteDesign",{
-  info:{
-    Title:"Contoso customer tracking", Description:"Creates customer list and applies standard theme",  SiteScriptIds:["607aed52-6d61-490a-b692-c0f58a6981a1"],  WebTemplate:"64"
-   }
-  });
-```
-
--->
-
-<br/>
-
 In the previous example, the **Add-SPOSiteScript** cmdlet or **CreateSiteScript** REST API returns a site script ID. This is used for the **SiteScripts** parameter in the subsequent call to the **Add-SPOSiteDesign** cmdlet or **CreateSiteDesign** REST API.
 
-
 | Parameter            | Value                | Site template type  |
 | :------------------- | :------------------- |:----------------|
 | WebTemplate  | 64 | Team site template |
 | WebTemplate 1 | 1 | Team site (with group creation disabled) |
 | WebTemplate    | 68 | Communication site template |
 | WebTemplate    | 69 | Channel site template |
 
-
-
 For step-by-step information about creating a site template, see [Get started creating site templates.](get-started-create-site-design.md)
 
 > [!NOTE]
+>
 > - A site template can run multiple scripts. The script IDs are passed in an array, and they run in the order listed.
 > - The former term for site templates may still appear in certain cmdlet and script labels as "site design."
 
-
 ## PnP provisioning and customization using Power Automate
 
 One action provided by site scripts is the ability to trigger a Power Automate flow. This allows you to specify any custom action that you need beyond the actions provided natively in site scripts.
 
 If you use the PnP provisioning engine to automate site creation, you can use a Power Automate flow to integrate with site templates. You can maintain all your existing provisioning scripts as well as create new custom provisioning scripts by using this technique.
 
-<br/>
-
 ![Process of triggering a Microsoft Flow](images/process-for-triggering-a-custom-flow.png)
 
 The process works as follows:
 
 1. The script instantiates your Power Automate flow using a URL with additional details.
-
-2. The flow sends a message to an Azure storage queue that you have configured.
-
-3. The message triggers a call to an Azure function that you have configured.
-
-4. The Azure function runs your custom script, such as the PnP provisioning engine, to apply your custom configurations.
+1. The flow sends a message to an Azure storage queue that you have configured.
+1. The message triggers a call to an Azure function that you have configured.
+1. The Azure function runs your custom script, such as the PnP provisioning engine, to apply your custom configurations.
 
 For a step-by-step tutorial about how to configure your own Power Automate flow with PnP provisioning, see [Build a complete site template using the PnP provisioning engine](site-design-pnp-provisioning.md).
 
@@ -287,12 +211,6 @@ Grant-SPOSiteDesignRights `
   -Rights View
 ```
 
-<!--
-```javascript
-RestRequest("/_api/Microsoft.SharePoint.Utilities.WebTemplateExtensions.SiteScriptUtility.GrantSiteDesignRights", {id:"44252d09-62c4-4913-9eb0-a2a8b8d7f863", principalNames:["[email protected]”], grantedRights:1});
-```
--->
-
 For more information about working with scopes, see [Scoping access to site templates](site-design-scoping.md).
 
 ## See also

docs/declarative-customization/site-design-overview.md

@@ -17,15 +17,15 @@ To run the PnP PowerShell cmdlets, you'll need to do the following:
 
 1. Download and install the PnP PowerShell Module by running:
 
-```PowerShell
-Install-Module PnP.PowerShell
-```
+    ```PowerShell
+    Install-Module PnP.PowerShell
+    ```
 
-2. Connect to the SharePoint Online Admin Center of your tenant:
+1. Connect to the SharePoint Online Admin Center of your tenant:
 
-```PowerShell
-Connect-PnPOnline -Url https://tenant-admin.sharepoint.com -Interactive
-```
+    ```PowerShell
+    Connect-PnPOnline -Url https://tenant-admin.sharepoint.com -Interactive
+    ```
 
 To verify your setup and connection, try using the `Get-PnPSiteScript` cmdlet to read the current list of site scripts. If the cmdlet runs and returns with no errors, you're ready to proceed.
 

docs/declarative-customization/site-design-pnppowershell.md

@@ -14,8 +14,7 @@ Use PowerShell cmdlets to create, retrieve, update, and remove site designs and
 To run the PowerShell cmdlets, you'll need to do the following:
 
 1. Download and install the [SharePoint Online Management Shell](https://www.microsoft.com/download/details.aspx?id=35588). If you already have a previous version of the shell installed, uninstall it first and then install the latest version.
-
-2. Follow the instructions at [Connect to SharePoint Online PowerShell](https://technet.microsoft.com/library/fp161372.aspx) to connect to your SharePoint tenant.
+1. Follow the instructions at [Connect to SharePoint Online PowerShell](https://technet.microsoft.com/library/fp161372.aspx) to connect to your SharePoint tenant.
 
 To verify your setup, try using the [Get-SPOSiteScript](/powershell/module/sharepoint-online/Get-SPOSiteScript) cmdlet to read the current list of site scripts. If the cmdlet runs and returns with no errors, you're ready to proceed.