Live publish

Author: buck1ey

powerapps-docs/developer/data-platform/appendix-add-license-information-to-your-solution.md

@@ -87,6 +87,10 @@ The plan definition file must include the following columns laid out in the form
 
 **Service ID:** This is created automatically when you create a plan in the Partner Center as part of the offer creation. Copy it from partner center into the plan definition file. More information: [Create plans in Partner Center](/azure/marketplace/dynamics-365-customer-engage-plans).
 
+**Display Name:** This is a descriptive name for your plan which you can choose. It will be show to users on license check error screens so it should be easily recognizable to your customers.
+
+**More info URL:** This is a URL where you would like to direct users to get more information about your solution, in the event they run into a license check error.
+
 
 ### Plan mapping file
  
@@ -126,4 +130,4 @@ To add the license information from the CSV files (created above) to the solutio
 
 ## See also
 
-[Appendix: App certification checklist](appendix-app-certification-checklist.md)
+[Appendix: App certification checklist](appendix-app-certification-checklist.md)

powerapps-docs/developer/data-platform/create-solution-app-appsource.md

@@ -48,10 +48,11 @@ For detailed information about using the Configuration Migration tool to create
 
 You will have a solution file (example: *SampleSolution.zip*) and optionally a demo data file (example: *SampleData.zip*) for your app.
 
+**Optional licensing information:** If you wish to add licensing information to your solution, see [Appendix: Add licensing information to your solution](appendix-add-license-information-to-your-solution.md).
 
 > [!div class="nextstepaction"]
 > [Step 3: Create an AppSource package for your app](create-package-app-appsource.md) 
   
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/webapi/azure-storage-partitioning.md

@@ -6,9 +6,9 @@ ms.date: 01/27/2021
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
-author: "JimDaly" # GitHub ID
-ms.author: "pehecke" # MSFT alias of Microsoft employees only
-manager: "sunilg" # MSFT alias of manager or PM counterpart
+author: "Bluebear73" # GitHub ID
+ms.author: "munzinge" # MSFT alias of Microsoft employees only
+manager: "mayadu" # MSFT alias of manager or PM counterpart
 search.audienceType: 
   - developer
 search.app: 

powerapps-docs/developer/model-driven-apps/clientapi/reference/controls/getContentWindow.md

@@ -63,7 +63,7 @@ function setClientApiContext(xrm, formContext) {
 }
 ```
 
-Next, add the following code in the form onLoad event handler:
+Next, add the following code in the form OnLoad event handler:
 
 ```javascript
 // This should be in a script loaded on the form. 
@@ -81,5 +81,7 @@ function form_onload(executionContext) {
 }
 ```
 
+Similar initialization code should be added to a TabStateChange event handler if such initialization is necessary. Any initialization code should be idempotent if it is re-used. For performance reasons, the form may destroy and re-initialize the control during tab navigations.
 
-[!INCLUDE[footer-include](../../../../../includes/footer-banner.md)]
+
+[!INCLUDE[footer-include](../../../../../includes/footer-banner.md)]