Live publish

Author: buck1ey

powerapps-docs/developer/common-data-service/isv-app-management-appsource-checker.md

@@ -1,6 +1,6 @@
 ---
 title: Introduction to the AppSource checker | Microsoft Docs
-description: Learn how to use app source checker.
+description: Learn how to use AppSource checker
 services: ''
 suite: powerapps
 documentationcenter: na
@@ -25,39 +25,41 @@ search.app:
 
 [!INCLUDE [cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
-AppSource checker allows an ISV to check the certification criteria of their app prior to [AppSource](https://appsource.microsoft.com/) submission. The checker will let you know if your solution file has errors that need to be corrected or if AppSource certification criteria have not been met. 
+You can use the AppSource checker to verify whether your app has met certification criteria before you submit it to [AppSource](https://appsource.microsoft.com/). The checker lets you know whether your solution file has errors that need to be corrected and verifies whether AppSource certification criteria have been met. 
 
-In ISV Studio, an ISV can either upload a full [package](/powerapps/developer/common-data-service/package-deployer/create-packages-package-deployer) or solution(s) and be notified of any issues that need to be remediated. To do that:
+In ISV Studio, you can upload either a full [package](/powerapps/developer/common-data-service/package-deployer/create-packages-package-deployer) or solution(s). You'll be notified whether any issues need to be remediated.
 
-1. In ISV Studio, select **AppSource checker** tab in the left and then select **Validate your app**.
+**To run AppSource checker**
+
+1. In ISV Studio, select **AppSource checker** in the leftmost pane, and then select **Validate your app**.
 
     > [!div class="mx-imgBorder"]
-    > ![AppSource checker](media/appsource-checker.png)
+    > ![AppSource checker](media/appsource-checker.png "AppSource checker")
 
-2. Click on **Browse** to upload a solution file from your local machine and select **Run Check** to validate.
+2. Select **Browse** to upload a solution file from your local machine, and then select **Run Check**.
 
    > [!div class="mx-imgBorder"]
-   > ![AppSource checker](media/appsource-browse-solution-files.png)
+   > ![Run check command](media/appsource-browse-solution-files.png "Run check command")
  
    > [!NOTE]
-   > If a user has previously uploaded a solution for validation then you will see a history of submissions instead of the screenshot above.
+   > If you've previously uploaded a solution for validation, you'll see a history of submissions instead of the screenshot above.
 
-3. Once the solution checker completes validating, a summary of results will be displayed along with the number of issues present (if any). Double-click on the solution file to see the issues in detail.
+3. After the validation check is complete, a summary of results is displayed with the number of issues found (if any). Double-click to select the solution file to see the issues in detail.
 
    > [!div class="mx-imgBorder"]
-   > ![AppSource checker](media/appsource-results-page.png)
+   > ![Summary of AppSource checker results](media/appsource-results-page.png "Summary of AppSource checker results")
 
-4. If the submission has no errors, you will see the following message:
+4. If the submission has no errors, you'll see the following message:
 
    > [!div class="mx-imgBorder"]
-   > ![AppSource checker](media/appsource-no-error-page.png)
+   > ![AppSource checker success message](media/appsource-no-error-page.png "AppSource checker success message")
    
-5. An ISV can download the validation report for their app and include it with their AppSource submission. 
+Now you can download the validation report for your app and include it with your AppSource submission. 
 
-## See Also
+### See also
 
 [Home page](isv-app-management-homepage.md)<br/>
 [App page](isv-app-management-apppage.md)<br/>
 [Tenant page](isv-app-management-tenantpage.md)<br/>
-[Connector Certification](isv-app-management-certification.md)
+[Connector certification](isv-app-management-certification.md)
 

powerapps-docs/developer/common-data-service/isv-app-management-certification.md

@@ -1,6 +1,6 @@
 ---
 title: Connector certification from ISV Studio | Microsoft Docs
-description: Learn how to submit a custom connector for certification using ISV Studio.
+description: Learn how to submit a custom connector for certification by using ISV Studio.
 services: ''
 suite: powerapps
 documentationcenter: na
@@ -21,40 +21,42 @@ search.app:
   - D365CE
 ---
 
-# Connector Certification
+# Connector certification
 
-If you own a service, API, or built a custom connector that you want to connect to Power Apps, Power Automate, Azure Logic Apps, or Power Query, you need to submit your connector to Microsoft for certification. 
+If you own a service or API—or you've built a custom connector that you want to connect to Power Apps, Power Automate, Azure Logic Apps, or Power Query—you need to submit your connector to Microsoft for certification. 
 
-Connector Certification is now in ISV Studio allowing the users to manage and track their connector certification submission. More information: [Get your connector certified](https://docs.microsoft.com/connectors/custom-connectors/submit-certification).
+Connector certification is now included in ISV Studio, so you can use it to manage and track your connector certification submission. More information: [Submit your connector for Microsoft certification](https://docs.microsoft.com/connectors/custom-connectors/submit-certification)
+<!--Suggest making the next paragraph a note, to emphasize the point. -->
+> ![NOTE]
+> Before you start submitting your connector for certification, see [Instructions on submitting your connector](https://docs.microsoft.com/connectors/custom-connectors/certification-submission) for submission requirements.
 
-Before you start submitting your connector for certification, see the [Instructions on submitting your connector](https://docs.microsoft.com/connectors/custom-connectors/certification-submission) article for submission requirements.
+**To certify your custom connector through ISV Studio**
 
-To certify your custom connector through ISV Studio:
+1. In ISV Studio, select **Connector certification** in the leftmost pane.
 
-1. In ISV Studio, select **Connector certification** tab in the left pane.
-2. Select the type of connector to certify and click on **Submit**.
+2. Select the type of connector to certify, and then select **Submit**.
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification](media/connector-certification-submit.png)
+   > ![Connector certification](media/connector-certification-submit.png "Connector certification")
 
-3. In the **Connector submission** page, read the agreement details and check the **Accept terms** and click on **Next**.
+3. On the **Connector submission** page, read the agreement details, select the **Accept terms** check box, and then select **Next**.
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification Consent form](media/connector-certification-consent-form.png)
+   > ![Consent form](media/connector-certification-consent-form.png "Consent form")
 
 4. Select **Choose a file** to upload the custom connector from your local machine. 
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification choose file](media/connector-certification-choose-file.png)
+   > ![Choose file](media/connector-certification-choose-file.png "Choose file")
 
-5. Enter the required details and click on **Submit for review**. 
+5. Enter the required details, and then select **Submit for review**. 
 
    > [!div class="mx-imgBorder"]
-   > ![Connector certification choose file](media/connector-certification-submit-for-review.png)
+   > ![Submit for review](media/connector-certification-submit-for-review.png "Submit for review")
 
-6. After you submit your connector for review, you'll receive an email from Microsoft.
+After you submit your connector for review, you'll receive an email from Microsoft.
 
-## See Also
+### See also
 
 [Home page](isv-app-management-homepage.md)<br/>
 [App page](isv-app-management-apppage.md)<br/>

powerapps-docs/developer/component-framework/faq.md

@@ -59,6 +59,10 @@ This is not supported natively by the framework. You can use one of many third-p
 
 Currently, font resources (files with a .ttf file extension) are not supported by the framework.
 
+### Can I use img resource for canvas apps?
+
+Currently, [img](manifest-schema-reference/img.md) resources are not supported in canvas apps.
+
 ## Related topics
 
 [Power Apps component framework API reference](reference/index.md)<br/>

powerapps-docs/developer/component-framework/reference/mode/setfullscreen.md

@@ -22,7 +22,7 @@ ms.assetid: 1faf3e79-969e-4c1e-ac01-8e2155c609fa
 
 ## Syntax
 
-`context.mode.setControlState(mode);`
+`context.mode.setFullScreen(value);`
 
 ## Available for 
 
@@ -39,4 +39,4 @@ Model-driven apps
 
 [Mode](../mode.md)<br/>
 [Power Apps component framework API reference](../../reference/index.md)<br/>
-[Power Apps component framework overview](../../overview.md)
+[Power Apps component framework overview](../../overview.md)

powerapps-docs/developer/model-driven-apps/actions-dashboards.md

@@ -51,6 +51,7 @@ You can perform actions such as create, retrieve, update, or delete, on organiza
   For a list of supported messages on the user-owned dashboard entity, see [UserForm Entity](../common-data-service/reference/entities/userform.md).  
 
 ### See also  
+
  [Dashboards for Microsoft Dynamics 365](analyze-data-with-dashboards.md)   
  [Using FormXML for Dashboards](understand-dashboards-dashboard-components-formxml.md)   
  [Create a Dashboard](create-dashboard.md)   

powerapps-docs/developer/model-driven-apps/actions-visualizations-charts.md

@@ -23,8 +23,9 @@ search.app:
 
 Using the Common Data Service Web Services, you can perform the following actions on the visualization entities.  
 
-## Actions on organization-owned visualizations  
- To perform actions on an organization-owned visualization (`SavedQueryVisualization`), you must have the System Administrator or the System Customizer role. You can perform the following actions on an organization-owned visualization:  
+## Actions on organization-owned visualizations 
+
+To perform actions on an organization-owned visualization (`SavedQueryVisualization`), you must have the System Administrator or the System Customizer role. You can perform the following actions on an organization-owned visualization:  
 
 - Create, retrieve, update, and delete an organization-owned visualization. More information: [Create a Visualization](create-visualization-chart.md)  
 

powerapps-docs/developer/model-driven-apps/client-scripting.md

@@ -28,17 +28,18 @@ However, if your business requirement can't be achieved using a business rule, y
 
 ## Use client scripting in model-driven apps
 
-Forms in Model-driven apps help display data to the user. A form in Model-driven apps can contain items such as fields, a quick form, or a grid. An [event](clientapi/events-forms-grids.md) occurs in Model-driven apps forms whenever:
+Forms in model-driven apps help display data to the user. A form in model-driven apps can contain items such as fields, a quick form, or a grid. An [event](clientapi/events-forms-grids.md) occurs in model-driven apps forms whenever:
+
 - A form loads
 - Data is changed in a field or an item within the form
 - Data is saved in a form
 
-You can attach your JavaScript code to "react" to these events so that your code gets executed when the event occurs on the form. You attach your JavaScript code (scripts) to these events by using a [Script web resource](script-jscript-web-resources.md) in Model-driven apps. 
+You can attach your JavaScript code to "react" to these events so that your code gets executed when the event occurs on the form. You attach your JavaScript code (scripts) to these events by using a [Script web resource](script-jscript-web-resources.md) in model-driven apps. 
 
 Model-driven apps provides you a rich set of **client APIs** to interact with form objects and events to control what and when to display on a form.
 
 > [!NOTE]
-> Some client APIs are deprecated in the current release of model-driven apps. Ensure that you are aware of these APIs as you write your client-side code for Model-driven apps. More information: [Deprecated client APIs](/dynamics365/get-started/whats-new/customer-engagement/important-changes-coming#some-client-apis-are-deprecated)
+> Some client APIs are deprecated in the current release of model-driven apps. Ensure that you are aware of these APIs as you write your client-side code for model-driven apps. More information: [Deprecated client APIs](/dynamics365/get-started/whats-new/customer-engagement/important-changes-coming#some-client-apis-are-deprecated)
 
 ## Get started here
 
@@ -53,7 +54,7 @@ Model-driven apps provides you a rich set of **client APIs** to interact with fo
 
 ### Related topics
 
-[Web resources for Model-driven apps](web-resources.md)<br/>
+[Web resources for model-driven apps](web-resources.md)<br/>
 [Customize commands and the ribbon](customize-commands-ribbon.md)<br/>
 
 

powerapps-docs/developer/model-driven-apps/command-bar-ribbon-presentation.md

@@ -100,6 +100,6 @@ Data defining commands in Common Data Service can be presented in several differ
 
 ### See also  
  [Customize commands and the ribbon](customize-commands-ribbon.md)   
- [Ribbons Available](/dynamics365/customer-engagement/developer/customize-dev/ribbons-available-microsoft-dynamics-365)   
- [Export Ribbon Definitions](export-ribbon-definitions.md)   
+ [Ribbons available](/dynamics365/customer-engagement/developer/customize-dev/ribbons-available-microsoft-dynamics-365)   
+ [Export Ribbon definitions](export-ribbon-definitions.md)   
  [Troubleshoot ribbon issues](https://support.microsoft.com/help/4552163)

powerapps-docs/developer/model-driven-apps/configure-form-accept-custom-querystring-parameters.md

@@ -23,16 +23,16 @@ search.app:
 
 The ability to pass values to a Web page by using query strings represents a concern for security. Model-driven Apps applies the best practice of always comparing any parameter passed as a query string against a list of expected parameter names and data types.  
 
- By default, Model-driven Apps allows a specified set of query string parameters to be passed to a form. You use these parameters to set default values when you create a new record in the application. Each parameter must use a standard naming convention that includes a reference to the attribute logical name. For more information, see [Set field values using parameters passed to a form](set-field-values-using-parameters-passed-form.md).  
+ By default, model-driven Apps allows a specified set of query string parameters to be passed to a form. You use these parameters to set default values when you create a new record in the application. Each parameter must use a standard naming convention that includes a reference to the attribute logical name. For more information, see [Set field values using parameters passed to a form](set-field-values-using-parameters-passed-form.md).  
 
  In your applications, you may want to pass custom query string parameters to an entity form. This topic provides information about how you can define a set of specific parameter names and data types that can be accepted for a specific entity form.  
 
 ## Define allowed query string parameters  
  There are two ways to specify which query string parameters will be accepted by the form:  
 
--   Edit form properties  
+- Edit form properties  
 
--   Edit form XML  
+- Edit form XML  
 
 ### Edit form properties  
  When you edit an entity form, on the **Home** tab in the **Form** group, click **Form Properties**. In the **Form Properties** dialog box, select the **Parameters** tab.