Refresh of the Azure CDN web part tutorial

VesaJuvonen · VesaJuvonen · commit 745f1f0fc784 · 2018-08-22T10:37:52.000+03:00
diff --git a/docs/images/tutorial-feature-solution-app-details.png b/docs/images/tutorial-feature-solution-app-details.png
diff --git a/docs/spfx/web-parts/get-started/deploy-web-part-to-cdn.md b/docs/spfx/web-parts/get-started/deploy-web-part-to-cdn.md
@@ -1,7 +1,7 @@
 ---
 title: Deploy your SharePoint client-side web part to Azure CDN
 description: Create a new sample web part and deploy its assets to an Azure CDN instead of using the default Office 365 CDN as the hosting solution.
-ms.date: 01/08/2018
+ms.date: 08/20/2018
 ms.prod: sharepoint
 ---
 
@@ -17,6 +17,9 @@ Create a new sample web part and deploy its assets to an Azure Content Delivery
 
 To configure an Azure storage account and integrate it with the CDN, follow the instructions at [Integrate an Azure storage account with Azure CDN](https://docs.microsoft.com/en-us/azure/cdn/cdn-create-a-storage-account-with-cdn), along with the detailed steps in this article. 
 
+> [!NOTE]
+> As Azure UIs are evolving fast, some of the pictures and steps might be out of date, but high level process is still valid.
+
 ### Storage account name
 
 This is the name you used to create your storage account, as described in [Step 1: Create a storage account](https://docs.microsoft.com/en-us/azure/cdn/cdn-create-a-storage-account-with-cdn#step-1-create-a-storage-account).
@@ -105,13 +108,7 @@ Note, however, that you have not yet deployed the files.
 
   At this point, Yeoman scaffolds the solution files and installs the required dependencies. This might take a few minutes. Yeoman scaffolds the project to include your custom web part as well.
 
-6. After the scaffolding completes, lock down the version of the project dependencies by running the following command:
-
-  ```sh
-  npm shrinkwrap
-  ```
-
-7. Enter the following to open the web part project in Visual Studio Code:
+6. Enter the following to open the web part project in Visual Studio Code:
 
   ```
   code .
@@ -123,11 +120,11 @@ Note, however, that you have not yet deployed the files.
 
   This is where we control the solution packaging.
 
-2. Update `includeClientSideAssets` value as **false** so that client-side assets are NOT packaged inside of the sppkg file, which is the default behavior. Because we are hosting assets from an external CDN, we do not want them to be included in the solution package. Your configuration should look somewhat like the following.
+2. Update `includeClientSideAssets` value as **false** so that client-side assets are NOT packaged inside of the sppkg file, which is the default behavior. As we are hosting assets from an external CDN, we do not want them to be included in the solution package. Your configuration should look somewhat like the following.
 
   ``` json
   {
-    "$schema": "https://dev.office.com/json-schemas/spfx-build/package-solution.schema.json",
+    "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/package-solution.schema.json",
     "solution": {
       "name": "azurehosted-webpart-client-side-solution",
       "id": "a4e95ed1-d096-4573-8a57-d0cc3b52da6a",
@@ -290,7 +287,7 @@ gulp bundle --ship
 As long as you are updating the **cdnBasePath** accordingly, your files are being properly loaded.
 
 > [!NOTE]
-> If you find an issue in the documentation or in the SharePoint Framework, report that to SharePoint engineering by using the [issue list at the sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input in advance.
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering by using the [issue list at the sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues) or by adding a comment to this article. Thanks for your input in advance.
 
 ## See also
 
diff --git a/docs/spfx/web-parts/get-started/provision-sp-assets-from-package.md b/docs/spfx/web-parts/get-started/provision-sp-assets-from-package.md
@@ -1,7 +1,7 @@
 ---
 title: Provision SharePoint assets from your SharePoint client-side web part
 description: SharePoint assets can be provisioned as part of the SharePoint Framework solution, and are deployed to SharePoint sites when the solution is installed on it. 
-ms.date: 01/08/2018
+ms.date: 08/20/2018
 ms.prod: sharepoint
 ---
 
@@ -61,13 +61,7 @@ You can also follow these steps by watching this video on the SharePoint PnP You
 
   At this point, Yeoman installs the required dependencies and scaffolds the solution files. This might take a few minutes. Yeoman scaffolds the project to include your **AssetDeployment** web part as well.
 
-6. After the scaffolding completes, lock down the version of the project dependencies by running the following command:
-
-  ```sh
-  npm shrinkwrap
-  ```
-
-7. Next, enter the following to open the web part project in Visual Studio Code:
+6. Next, enter the following to open the web part project in Visual Studio Code:
 
   ```
   code .
@@ -159,7 +153,7 @@ In the following steps, we define the needed structure to be provisioned.
   * Definitions use standard Feature Framework schema, which is well known to SharePoint developers.
   * Custom fields are being referenced in the introduced content type.
   * We use the **CustomSchema** attribute in the **ListInstance** element to define a provisioning time schema.xml file for the list. This way the list is still based on the out-of-the-box list template (normal custom list '100' in this case), but we can define an alternative provisioning definition during initial provisioning.
-  * When provisioning list instances using Features you must provide the ID of the Feature associated with the particular list definition. Using the FeatureId attribute you are supposed to provide the ID of the Feature which contains the List Definition. As an example: if you’re provisioning an instance of a custom list the FeatureId attribute should be set to {00bfea71-de22-43b2-a848-c05709900100}.
+  * When provisioning list instances using Features you must provide the ID of the Feature associated with the particular list definition. Using the FeatureId attribute you are supposed to provide the ID of the Feature which contains the List Definition. As an example: if you’re provisioning an instance of a custom list the FeatureId attribute should be set to `{00bfea71-de22-43b2-a848-c05709900100}`.
 
   More details about the used schema structures can be found at [Using Features in SharePoint Foundation](https://msdn.microsoft.com/en-us/library/office/ms460318(v=office.14).aspx) on MSDN.
 
@@ -221,7 +215,7 @@ Now we have created the needed structures for provisioning SharePoint assets aut
 
   ```json
   {
-    "$schema": "https://dev.office.com/json-schemas/spfx-build/package-solution.schema.json",
+    "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/package-solution.schema.json",
     "solution": {
       "name": "asset-deployment-webpart-client-side-solution",
       "id": "6690f11b-012f-4268-bc33-3086eb2dd287",
@@ -390,7 +384,7 @@ Next we need to update both the solution version and the feature version respons
 
   ```json
   {
-    "$schema": "https://dev.office.com/json-schemas/spfx-build/package-solution.schema.json",
+    "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/package-solution.schema.json",
     "solution": {
       "name": "asset-deployment-webpart-client-side-solution",
       "id": "6690f11b-012f-4268-bc33-3086eb2dd287",
@@ -476,7 +470,7 @@ Now that the package has been updated in the app catalog, we can move to the act
   ![App status updated to updating in the site contents page](../../../images/tutorial-feature-solution-updating-app-classic.png)
 
   > [!NOTE]
-  > Because the SharePoint Framework uses the same app infrastructure as SharePoint Add-ins, the status for the upgrade indicates that the update can happen for an add-in or an app. 
+  > Because the SharePoint Framework uses the same app infrastructure as SharePoint Add-ins, the status for the upgrade indicates that the update can happen for an add-in or an app.
 
   The update can take a while, but when the solution status changes to normal again, you can select **F5** to refresh the site contents page to confirm that a new list called *New List* has been successfully provisioned as part of the update process.
 
@@ -485,7 +479,7 @@ Now that the package has been updated in the app catalog, we can move to the act
   Now we have successfully upgraded this instance to the latest version. This Feature Framework option for SharePoint asset provisioning is pretty much the same as it is for the SharePoint Add-in model. The key difference is that the assets are being provisioned directly to a normal SharePoint site, because there's no concept called app or add-in web with SharePoint Framework solutions.
 
 > [!NOTE]
-> If you find an issue in the documentation or in the SharePoint Framework, report that to SharePoint engineering by using the [issue list at the sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues). Thanks for your input in advance.
+> If you find an issue in the documentation or in the SharePoint Framework, please report that to SharePoint engineering by using the [issue list at the sp-dev-docs repository](https://github.com/SharePoint/sp-dev-docs/issues) or by adding a comment to this article. Thanks for your input in advance.
 
 ## See also
 
