Doc updates

Author: jansenbe

docs/transform/modernize-userinterface-site-pages-webparts.md

@@ -15,6 +15,8 @@ When a page is transformed from a classic page into a modern client side page th
 
 ## Web part transformation list (updated for Feb 2018 release)
 
+The page transformation uses a default web part mapping when it transforms classic pages to modern pages. The used mapping in this default modern is described here, but do know that you can update the mapping to for example add your own custom 3rd party web parts as a transformation target. How to extend the web part mapping model is described in the [Page transformation model](modernize-userinterface-site-pages-model.md) article.
+
 Classic web part | Modern web part | Comments
 -----------------|-----------------|--------------------------------------
 Microsoft.SharePoint.WebPartPages.XsltListViewWebPart (viewing list data) | [List](https://support.office.com/en-us/article/use-the-list-and-other-web-parts-on-classic-pages-03044488-c0e4-4226-a8fb-4cd8364424fa), [Library](https://support.office.com/en-us/article/use-the-document-library-web-part-a9dfecc3-2050-4528-9f00-2c5afc5731b0) or [Events](https://support.office.com/en-us/article/use-the-events-web-part-5fe4da93-5fa9-4695-b1ee-b0ae4c981909) web part | See next chapter for more details

docs/transform/modernize-userinterface-site-pages.md

@@ -1,7 +1,7 @@
 ---
 title: Transform classic pages to modern client-side pages
 description: Explains how to transform classic wiki and web part pages into modern client side pages
-ms.date: 01/30/2019
+ms.date: 02/19/2019
 ms.prod: sharepoint
 localization_priority: Priority
 ---
@@ -16,10 +16,18 @@ The SharePoint PnP Modernization framework ([Nuget](https://www.nuget.org/packag
 > - Page transformation today works for wiki and web part pages. Publishing pages is something we're evaluating for a future release.
 > - The SharePoint PnP Modernization framework is continuously evolving, checkout [the release notes](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/Modernization%20Framework%20release%20notes.md) to stay up to date on the latest changes. If you encounter problems please file an issue in the [sp-dev-modernization GitHub issue list](https://github.com/SharePoint/sp-dev-modernization/issues).
 
-To use page transformation for your environment you can use one or more of below described approaches:
+Page transformation can be used in one ore more approaches:
 
-Approach | Audience | Description
----------|----------|------------
+Technique | DevOps/Developer/ISV | End user | Keep/Discard option | Comments
+--------- |----------------------|----------|---------------------|---------
+[SharePoint Page Transformation UI](modernize-userinterface-site-pages-ui.md) | | X | Mandatory | If you want your end users to have the ability to self-service modernize pages
+[PowerShell](modernize-userinterface-site-pages-powershell.md) | X | | Optional | Typically used when you want to modernize pages for multiple site collections. Optionally you can configure the page accept banner to be shown which then enables your end users to keep or discard the pages you've created using PowerShell
+[.Net](modernize-userinterface-site-pages-dotnet.md) | X | | Optional | Typically used when you integrate page transformation into existing services or tools. Optionally you can configure the page accept banner to be shown which then enables your end users to keep or discard the pages you've created using .Net
+
+To use page transformation for your environment you can use one or more of below described techniques:
+
+Technique | Audience | Description
+----------|----------|------------
 [SharePoint Page Transformation UI](modernize-userinterface-site-pages-ui.md) | Any SharePoint user | This approach will make it possible for end users to simply click a button to request a modern version of a page. The returned page is a preview and the end user will have the option to keep or discard the generated page.
 [PowerShell](modernize-userinterface-site-pages-powershell.md) | DevOps | Use the PowerShell approach to automate the generation of modern pages for a site. Pages generated using this approach can also optionally be generated as preview, allowing the actual site page users to decide on whether they want to keep or discard the pages.
 [.Net](modernize-userinterface-site-pages-dotnet.md) | Developer / ISV | The core of page transformation is the .Net based SharePoint PnP Modernization framework. Using .Net you can fully tailor the transformation process, this approach is recommended whenever you want full control on the transformation process or when you want to integrate page transformation into another solution/product.