Udpating articles

Author: VesaJuvonen

docs/spfx/extensions/get-started/build-a-hello-world-extension.md

@@ -1,5 +1,5 @@
 
-# Build your first SharePoint SharePoint Extension (Hello World part 1)
+# Build your first SharePoint Framework Extension (Hello World part 1)
 
 >**Note:** The SharePoint Framework Extensions are currently in preview and is subject to change. SharePoint Framework Extensions are not currently supported for use in production environments.
 

docs/spfx/extensions/get-started/hosting-extension-from-office365-cdn.md

@@ -37,19 +37,19 @@ Open up a browser and move to a site collection where you'd like to host your CD
 
 Create a new document library on your site collection called **CDN** and add a folder called **helloworld** to it.
 
-![helloworld-extension folder in CDN library](../../../../images/cdn-helloworld-folder.png) 
+![helloworld-extension folder in CDN library](../../../../images/ext-app-cdn-folder-created.png) 
 
-Move back to your PowerShell console and add a new CDN origin. Update the provided URL below to match your own environment. 
+Move back to your PowerShell console and add a new CDN origin. Update the provided URL below to match your own environment. In this case we are setting origin as `*/cdn`, which means that any relative folder with name of **cdn** will act as CDN origin.
 ```
-Add-SPOTenantCdnOrigin -CdnType Public -OriginUrl sites/cdn/cdn
+Add-SPOTenantCdnOrigin -CdnType Public -OriginUrl */cdn
 ```
 Execute the following command to get the list of CDN origins from your tenant
 ```
 Get-SPOTenantCdnOrigins -CdnType Public
 ```
 Notice that your newly added origin is listed as a valid CDN origin. Final configuration of the origin will take a while (approximately 15 minutes), so we can continue by creating your test extension, which will be hosted from the origin, when the deployment is completed. 
 
-![List of public origins in tenant](../../../../images/cdn-public-origins.png)
+![List of public origins in tenant](../../../../images/ext-app-cdn-origins-pending.png)
 
 > When origin is listed without the *(configuration pending)* text, it is ready to be used in your tenant. This is the indication of an on-going configuration between SharePoint Online and CDN system. 
 
@@ -66,7 +66,7 @@ Update the *write-manifests.json* file (under *config* folder) as follow to poin
 https://publiccdn.sharepointonline.com/<tenant host name>/sites/site/library/folder
 ```
 
-![Updated write manifest content with path to CDN endpoint](../../../../images/cdn-write-manifest-json.png)
+![Updated write manifest content with path to CDN endpoint](../../../../images/ext-app-cdn-write-manifest.png)
 
 Save your changes.
 
@@ -87,6 +87,9 @@ This command will create a **app-extension.sppkg** package on the **sharepoint/s
 
 Upload or drag & drop the newly created client-side solution package to the app catalog in your tenant. 
 
+UPDUPAUPETPE
+![](../../../../images/ext-app-approve-cdn-address.png)
+
 Install new version of the solution to your site and ensure that it's working properly.
 
 ![Custom header and footer elements rendered in the page](../../../../images/ext-app-header-footer-visible.png)

docs/spfx/extensions/get-started/serving-your-extension-from-sharepoint.md

@@ -48,6 +48,8 @@ Create a new file inside the **sharepoint\assets** folder named as **elements.xm
 
 Copy the following xml structure into **elements.xml**. Updated the **ClientSideComponentId** property to have the unique Id of your Application Customizer available from the **HelloWorldApplicationCustomizer.manifest.json** file at **src\extensions\helloWorld** folder.
 
+We also set the **ClientSideComponentProperties** using this xml definition and bypass JSON properties for this extension instance. Notice how the JSON is escaped, so that we can set that properly using XML attribute. 
+
 Notice also that we use specific ___location called `ClientSideExtension.ApplicationCustomizer` to define that this is Application Customizer. Since by default this **element.xml** will be associated to *Web* scoped feature, this CustomAction will be automatically added to `Web.UserCustomAction` collection in the site where the solution is being installed.
 
 ```xml
@@ -57,7 +59,8 @@ Notice also that we use specific ___location called `ClientSideExtension.Applicatio
     <CustomAction 
         Title="SPFxApplicationCustomizer"
         Location="ClientSideExtension.ApplicationCustomizer"
-        ClientSideComponentId="5fc73e12-8085-4a4b-8743-f6d02ffe1240">
+        ClientSideComponentId="46606aa6-5dd8-4792-b017-1555ec0a43a4"
+        ClientSideComponentProperties="{&quot;Header&quot;:&quot;Header area of the page&quot;,&quot;Footer&quot;:&quot;Footer area in the page&quot;}">
 
     </CustomAction>