Updating notes on SPFx usage with SP2016 around the includeClientSideAssets attribute

Author: VesaJuvonen

docs/spfx/sharepoint-2016-support.md

@@ -1,6 +1,6 @@
 ---
 title: SharePoint Framework development with SharePoint 2016 Feature Pack 2
-ms.date: 09/25/2017
+ms.date: 1/2/2018
 ---
 
 # SharePoint Framework development with SharePoint 2016 Feature Pack 2
@@ -21,6 +21,9 @@ If you are planning to use the same client-side web parts in both SharePoint 201
 
 Starting from version 1.3, the SharePoint Framework Yeoman generator supports scaffolding solutions both that use the latest version of the SharePoint Framework meant for use with SharePoint Online, and solutions that can be used also with SharePoint on-premises based on the v1.1.0 of the SharePoint Framework. You don't need to install a separate version of the SharePoint Framework Yeoman generator to scaffold solutions meant for use with SharePoint on-premises.
 
+> [!IMPORTANT]
+> Starting from version 1.4, the SharePoint Framework Yeoman generator supports new attribute of `includeClientSideAssets`, which can be used to indicate that assets should be included in the *sppkg* package. This capability is however only currently supported in SharePoint Online. When solution is targeted to  on-premises, this attribute in `package-solution.json` should be updated as `false`.
+
 ## Hosting your SharePoint Framework solution for on-premises deployment
 
 Getting SharePoint Framework client-side web parts deployed to on-premises requires two distinct actions:

docs/spfx/web-parts/get-started/hosting-webpart-from-office-365-cdn.md

@@ -1,6 +1,6 @@
 ---
 title: Hosting client-side web part from Office 365 CDN
-ms.date: 12/11/2017
+ms.date: 1/2/2018
 ms.prod: sharepoint
 ---
 
@@ -12,6 +12,9 @@ This article describes how to host your client-side web part from Office 365 CDN
 > [!NOTE]
 > There are multiple different hosting options for your web part assets. This tutorial concentrates on showing the Office 365 CDN option, but you could also use the [Azure CDN](./deploy-web-part-to-cdn.md) or simply host your assets from SharePoint library from your tenant. In the latter case, you would not benefit from the CDN performance improvements, but that would also work from the functionality perspective. Any ___location which end users can access using HTTP(S) would be technically suitable for hosting the assets for end users.
 
+> [!IMPORTANT]
+> This article uses `includeClientSideAssets` attribute, which was introduced in the SPFx v1.4. This version is not supported with **SharePoint 2016 Feature Pack 2**. If you are using on-premises setup, you need to decide the CDN hosting ___location separately. You can also simply host the JavaScript files from centralized library in your on-premises SharePoint which your users have access. Please see additional considerations from the [SharePoint 2016 specific guidance](../../sharepoint-2016-support.md).
+
 ## Prerequisites
 
 Make sure that you have completed the following tasks before you begin: