Merge branch 'staging'

Author: VesaJuvonen

docs/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api.md

@@ -121,9 +121,9 @@ gulp serve --nobrowser
 ```
 Notice that we used the `--nobrowser` option, since there's no value for starting local workbench, since you cannot debug extensions locally currently.
 
-Once it compiles the code without errors, it will serve the resulting manifest from http://localhost:4321.
+Once it compiles the code without errors, it will serve the resulting manifest from *http://localhost:4321*.
 
-Move any SharePoint list in your SharePoin Online sites with a modern experience.
+Move any SharePoint list in your SharePoint Online sites with a modern experience.
 
 Since our ListView Command Set is hosted still in localhost and is running, we can use specific debug query parameters to execute the code in the newly created.
 

docs/spfx/extensions/get-started/building-simple-field-customizer.md

@@ -128,6 +128,7 @@ Append the following query string parameters to the URL. Notice that you will ne
 ?loadSPFX=true&debugManifestsFile=https://localhost:4321/temp/manifests.js&fieldCustomizers={"Percent":{"id":"0e3d8b71-56aa-4405-9225-f08a80fc1d71","properties":{"sampleText":"Hello!"}}}
 ```
 More detail about the URL query parameters:
+
 * **loadSPFX=true:**  ensures that the SharePoint Framework is loaded on the page. For performance reasons, the framework normally is not loaded unless at least one extension is registered.  Since no components are registered yet, we must explicitly load the framework.
 * **debugManifestsFile:**  specifies that we want to load SPFx components that are being locally served.  Normally the loader only looks for components in the App Catalog (for your deployed solution) and the SharePoint manifest server (for the system libraries).
 * **fieldCustomizers**:  Indicates which fields in your list should have their rendering controlled by the Field Customizer.  The ID parameter specifies the GUID of the extension that should be used to control the rendering of the field.  The properties parameter is an optional text string containing a JSON object that will be deserialized into `this.properties` for your extension.

docs/spfx/extensions/get-started/using-page-placeholder-with-extensions.md

@@ -99,6 +99,7 @@ export default class HelloWorldApplicationCustomizer
 ```
 
 Update the `onRender` method with the following code:
+
 * We use `this.context.placeholders.tryAttach` to get access on the placeholder
 * Extension code should not assume that the expected placeholder is available
 * Code expects a custom properties called `Header`and `Footer`. If properties exists, they will be rendered inside of the placeholder.
@@ -199,6 +200,7 @@ gulp serve --nobrowser
 Navigate to a out of the box modern list in SharePoint Online. This can be a list or a library for the initial testing. 
 
 To test your extension, append the following query string parameters to the URL:
+
 * Notice that the GUID used in this query parameter has to match on the ID attribute of your Application Customizer available from **HelloWorldApplicationCustomizer.manifest.json**.
 * We also use Header and Footer JSON properties to provide parameters or configurations to the Application Customizer. In this case we simply output these values, but you could adjust the behavior based on the properties in actual production usage.