doc updates for September release

Author: jansenbe

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

@@ -1,7 +1,7 @@
 ---
 title: Page Transformation Functions and Selectors
 description: Page Transformation Functions and Selectors
-ms.date: 06/24/2019
+ms.date: 09/03/2019
 ms.prod: sharepoint
 localization_priority: Normal
 ---
@@ -124,7 +124,7 @@ Name|Description
 
 **Description:** Returns an the (static) string provided as input
 
-**Example:** `EmptyString('static string')`
+**Example:** `StaticString('static string')`
 
 #### Input parameters
 
@@ -500,7 +500,7 @@ Name|Description
 
 **Description:** Returns an the (static) string provided as input
 
-**Example:** `EmptyString('static string')`
+**Example:** `StaticString('static string')`
 
 #### Input parameters
 
@@ -592,6 +592,22 @@ Name|Description
 Name|Description
 :-----|:----------
 {return value}|A formatted preview image url
+### ToAuthors
+
+**Description:** Looksup user information for passed user id
+
+**Example:** `ToAuthors({PublishingContact})`
+
+#### Input parameters
+
+Name|Description
+:-----|:----------
+{userId}|The id (int) of a user
+#### Output parameters
+
+Name|Description
+:-----|:----------
+{return value}|A formatted json blob describing the user's details
 ## Selectors
 ### TextSelector
 

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

@@ -116,7 +116,7 @@ ConvertTo-PnPClientSidePage -Identity "page1.aspx" -PublishingPage -TargetConnec
 ```
 
 > [!NOTE]
-> - This feature is still in preview in the June 2019 release...it should support SharePoint 2013, 2016 and 2019
+> - This feature supports SharePoint 2010, 2013, 2016 and 2019 as a source environment. Target environment is SharePoint Online
 > - It's important to use the SharePoint Online PnP PowerShell version, the machine running the PowerShell script needs to be able to connect to both the on-premises SharePoint server as the SharePoint Online environment
 > - There (currently) is no user mapping feature, hence item level permissions are not copied over from the on-premises publishing page to the SharePoint Online modern page
 > - This approach can also be used for page transformation across tenants (whenever that would make sense)

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: 04/04/2019
+ms.date: 03/09/2019
 ms.prod: sharepoint
 localization_priority: Priority
 ---
@@ -13,7 +13,7 @@ Classic SharePoint sites typically have classic pages being wiki pages or web pa
 The SharePoint PnP Modernization framework ([Nuget](https://www.nuget.org/packages/SharePointPnPModernizationOnline), [source code](https://github.com/SharePoint/sp-dev-modernization/tree/master/Tools/SharePoint.Modernization/SharePointPnP.Modernization.Framework)) does bring page transformation capabilities which will be explained in the upcoming chapters.
 
 > [!IMPORTANT]
-> - Page transformation today works for wiki, web part pages and publishing pages. The publishing page transformation is currently in preview.
+> - Page transformation today works for wiki, web part pages and publishing pages.
 > - 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).
 
 Page transformation can be used in one or more models and these models can used together: